Manage local dev servers

Download for macOSFree 3-day trial · Apple silicon
Watches
Ports 3000 to 9999
Recognizes
7 frameworks and 7 runtimes
Each row
Port, project, uptime
Actions
Open, copy, stop

Framework and port details

AgentPeek recognizes common frameworks (Next.js, Vite, Astro, Wrangler, Storybook, Playwright, and static-site servers) and language runtimes (Node, Bun, Deno, Python, Ruby, Rust, or Go); anything else shows its process name. Each row carries the port, the project folder taken from the server's working directory, and how long it's been up.

Server actions

  • One click opens the localhost URL in your browser.
  • One click copies the URL, ready to paste anywhere.
  • One click asks the process to shut down after AgentPeek verifies the target; save your work before stopping anything.

That last one matters when a coding agent spins up a server on its own: it shows up on the next scan, a few seconds after it starts listening, and you can shut it down without hunting for the PID.

Servers beside sessions

The server list lives in the same panel as your live sessions, so when Claude Code says "the dev server is running", the proof is one glance up. It sits alongside Quick Routes and Fast Actions, the two panels you open for the same kind of errand.

Questions

AgentPeek watches ports 3000 to 9999 and lists the dev servers listening on those ports with port, framework or runtime, project folder, and uptime, live in the Mac notch. No lsof, no terminal commands.
Yes: each server row has a one-click stop that verifies the target process and requests a graceful shutdown. As with any process stop, unsaved state in that server is lost.
Next.js, Vite, Astro, Wrangler, Storybook, Playwright, and static-site servers, plus the Node, Bun, Deno, Python, Ruby, Rust, and Go runtimes. Anything it does not recognize shows its process name instead.

Keep reading

Keep your agents in view

Download for macOSFree 3-day trial · Apple silicon