What is Blink?
Blink is a menu bar app that lists every dev server currently listening on your Mac — with its port, framework and project — plus the booted iOS simulators and the app running inside each one. From that list you can stop or restart a server in one click, open its localhost address in a browser, and relaunch an app in a simulator without opening Xcode. When a restart fails to come back, the row explains why and puts the full output one click from your clipboard. It works by polling the system rather than by wrapping your commands: it reads listening ports, inspects each process's arguments and working directory, and reads the project manifest to name the framework. The developer states that Blink runs no background daemon, requests no elevated privileges and does not talk to the network at all — it does not even check for updates. Requires macOS 14 (Sonoma) or later, and is MIT licensed.
Verified product facts
- Type
- developer utilityEditorially reviewed
- Platform
- macOS
- Pricing
- Open sourceDeveloper-stated
- Open source
- Yes
- Relationship to Nuanyue
- Third-party product — not published by NuanyueEditorially reviewed
- Licence
- MIT
- Current version
- 1.2Developer-stated
- Official website
- github.com/megootronic/Blink
Last updated , last reviewed . Facts marked developer-stated come from the developer and are not independently confirmed; editorially reviewed marks a Nuanyue judgement.
Key features
What Blink does at a glance.
Live server monitoring
Every dev server running on your machine, with port, framework and project name
Restart without leaving the menu bar
Stop and relaunch a dev server in one click, no terminal, no rebuild
Failures explained in place
When a restart doesn't come back, the row shows why, with the full output one click from your clipboard
Framework detection
Next.js, Vite, Nuxt, Remix, Astro, Django, Flask, Rails and more, each with its own colour
Simulator tracking
Booted simulators with device name, runtime, and the app running inside
Relaunch an app in the simulator
Terminate and launch without going back to Xcode
What you can use Blink for
- Restarting a dev server after a config change without finding the terminal tab it was started in
- Watching which port each project ended up on when several are running at once
- Reading why a server failed to come back up, and copying its output into a bug report
- Relaunching an app in a booted simulator during a build-debug loop
- Opening a project's localhost address without remembering the port
Who is Blink for?
- Developers who keep several dev servers running across different projects
- iOS developers who bounce between a simulator and the terminal all day
- Anyone who would rather not install a daemon or grant an app elevated rights for this
Who is Blink not for?
- People on macOS 13 or earlier — the developer states macOS 14 Sonoma as the minimum
- Teams that need a managed or centrally configured dev environment; there is no shared config
- Anyone who wants the app to update itself in the background
Limitations
- Requires macOS 14 (Sonoma) or later, per the developer
- The developer states that Blink does not check for updates, so new versions are a manual download
- Restarting reconstructs a command from the running process rather than replaying the original shell invocation; the developer documents specific handling for frameworks such as Next.js and npm that overwrite their arguments
- It observes servers that are already listening; a process that failed before binding a port is outside what a port scan can see
- A minimum macOS version is stated, but no compatibility statement for individual frameworks beyond the detection list
Strengths and trade-offs
What Blink does well, and what to weigh before choosing it. Points marked developer-stated come from the developer’s own material and have not been independently confirmed.
Strengths
- The developer describes it as a menu bar robot that watches running dev servers and iOS simulators and restarts them, so the restart happens where you already are rather than in the terminal that started the process.Developer-stated
- Server rows carry port, framework and project name, and framework detection covers Next.js, Vite, Nuxt, Remix, Astro, Django, Flask and Rails.Developer-stated
- A failed restart is reported in the row with the reason, and the full output is one click from the clipboard — which is the part that usually costs a trip back to a terminal scrollback.Developer-stated
- The developer states that Blink runs no background daemon, asks for no privilege escalation and makes no network requests, including update checks.Developer-stated
- MIT licensed, with the source and the release build both published in the same repository.
Trade-offs
- macOS 14 Sonoma is the stated minimum, which excludes machines held back a release.Developer-stated
- Because it does not check for updates and does not talk to the network, there is no in-app upgrade path; staying current means noticing a release yourself.Derived
- The developer documents that Next.js and npm overwrite process arguments, with argv[0] often reduced to a bare node — so relaunching is a reconstruction from kernel state and the parent chain, bounded to the server's own project directory, rather than a replay of the exact command you typed.Developer-stated
- Discovery works from listening ports, so a server that died before binding one does not appear in the list.Derived
Overview
The terminal tab that started a dev server is easy to lose. Ten minutes later the server needs a restart, and the choice is to hunt for the tab, or to start a second copy and find out which port it grabbed.
Blink takes the other route: it lists what is already running. The menu bar panel shows every dev server on the machine with its port, framework and project name, plus the booted iOS simulators and the app inside each one. Stop, restart, open in a browser, relaunch the simulator app — all from that list.
How It Finds Things
It does not wrap your commands, which is why it works on servers it never saw
start. It polls the system for listening ports, then reads each process’s
arguments and working directory, and reads the project manifest to name the
framework. Simulators come from xcrun simctl.
The consequence is worth stating plainly: discovery is a scan, so it sees what is currently bound to a port. A process that crashed before listening is not in the list.
The Restart Problem
Restarting sounds trivial and is not. The developer documents why: Next.js and
npm overwrite their own process arguments, and argv[0] is often just node,
so the command line you typed is no longer readable from the process table.
Blink reads the real arguments from the kernel and the resolved binary, walks
up the parent chain to find a process it can relaunch, and stops at the
project’s own directory boundary rather than climbing further.
That is a reconstruction, not a replay. It is also the reason the feature can exist at all without hooking into your shell.
What It Deliberately Doesn’t Do
No background daemon, no privilege escalation, no network access — including no update check. The developer states all three, and the last one has a visible cost: staying current is a manual download.
For a tool that reads your process table, that is a reasonable trade. It also means the app cannot quietly change behaviour between releases.
Who It Suits
Developers running several servers across several projects, and iOS developers who move between a simulator and a terminal all day. The one-click copy of a failed server’s output is the small feature that earns the install.
It is a poor fit below macOS 14, and a poor fit for anyone who needs the app to maintain itself.
Questions about Blink
Does Blink run a background service or need admin rights?
No. The developer states there is no background daemon and no privilege escalation — Blink reads what the system already exposes about running processes and presents it in a menu bar panel.Editorially reviewed
Does it send anything over the network?
The developer states it does not talk to the network at all, and explicitly that it does not check for updates. Everything it reports is read locally.Editorially reviewed
How does it know which framework a server is using?
By inspecting the process: its arguments, its working directory, and the project manifest in that directory. The developer lists Next.js, Vite, Nuxt, Remix, Astro, Django, Flask and Rails among the detected frameworks.Editorially reviewed
Can it restart a server that was started from a terminal?
That is the case it is built for, but the mechanism matters. The developer documents that some frameworks and package managers overwrite their own arguments, so Blink reads the real arguments from the kernel and walks up the parent process chain to find a process it can relaunch, without stepping outside the server's project directory.Editorially reviewed
What macOS version does it need?
macOS 14 (Sonoma) or later, per the developer.Editorially reviewed
Is it free?
Yes. The repository is MIT licensed and the release build is published there.Editorially reviewed
Works well with
Not a replacement — apps commonly used alongside this one.
Control Room
Control the Xcode Simulator's appearance, status bar, location and notifications.
Both work on a booted simulator from outside Xcode: Blink relaunches the app inside it, Control Room changes the status bar, appearance, location and notifications it shows.
AXe
CLI for automating iOS Simulators via accessibility APIs and HID input.
AXe drives a simulator from the command line for scripted runs; Blink is the menu bar view for restarting the app and the dev server by hand between those runs.
Ghostty
Native, GPU-accelerated terminal emulator built on a shared Zig core.
Blink exists so you do not have to find the terminal tab that started a server — but that tab is still where the server was started, and Ghostty is one of the terminals it can be started from.
Links
Sources
Facts on this page are checked against the sources below. Last updated , last reviewed .
- Blink — official websiteGrade B
- Blink — source repositoryGrade D





