[Feature]: Tracking running server URLs per worktree

[zyrain]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

Not sure

Problem or use case

When switched between several worktrees, sometimes they're running local dev instances, but it's tough to tell if they are and even tougher to know which ports they are running on.

Using portless only addresses the conflict issue, not the "is it running" issue.

Proposed solution

Ideally, we'd have a field and action button showing the currently active URL for the worktree and a status on if it's running (greyed-out if it's not running). If it's not, one button can launch the dev server and also trigger the browser. An embedded browser might be a nice optional feature here.

Why this matters

This allows for rapid switching between worktrees and, especially in the embedded browser case, where the window switches along with the thread switch, we can see if the LLM has implemented or is implementing correctly any changes in real time (hot reload).

Smallest useful scope

A first pass:

1. Track if the LLM has a hosting instance running on a background thread
2. When the user clicks "Preview" if it's NOT running a local dev server, then run one.
3. Then open that URL in the browser.

Alternatives considered

https://github.com/broskees/worktree-mcp
https://pm2.keymetrics.io/
https://github.com/raskrebs/sonar
https://www.49agents.com/
https://github.com/vercel-labs/portless

Risks or tradeoffs

• Testing running processes might be tricky, especially when the browser might not be showing the right thing
• The LLM might ignore any system prompt info on using this tool call / MCP and spin up additional ones anyhow.

Examples or references

No response

Contribution

• I would be open to helping implement this.