Skip to content

feat(web): scope browser empty-state servers to the current worktree - #40

Merged
connorch merged 1 commit into
mainfrom
connorch/worktree-scoped-local-servers
Oct 1, 2026
Merged

connorch merged 1 commit into
mainfrom
connorch/worktree-scoped-local-servers

Conversation

@connorch

@connorch connorch commented Oct 1, 2026

Copy link
Copy Markdown
Owner

The empty browser tab lists every local server in the environment. With several worktrees running dev servers at once, it is hard to tell which one belongs to the code in the current thread.

The list now defaults to servers started from terminals of any thread in the active worktree. A "This worktree / All" toggle shows everything else. It appears only when it would hide something. Threads without a worktree share the project root. The scanner already tags each server with the thread terminal that started it, so this is client-only.

Rows now show the address a click actually opens, for example the tailnet host when connected remotely, and the title of the thread that started the server. Before, rows showed the process name ("node") and localhost:PORT.

No screenshots: the browser panel needs the desktop app, and QA in the web dev build was cut short. Unit tests cover the worktree filtering.

Made with Claude Opus 5.5 in Claude Code, running inside T3 Code.

🤖 Generated with Claude Code

The empty browser tab listed every local server in the environment, which
made it hard to find the dev server for the code being worked on when many
worktrees run servers at once. It now defaults to servers started from
terminals of threads in the active worktree, with a toggle to show all.

Rows now show the address a click opens and the thread that started the
server.
@connorch
connorch merged commit eeb097e into main Oct 1, 2026
5 of 14 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-01T20:37:17.160050Z 9c38404 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@github-actions github-actions Bot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:M labels Oct 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M vouch:trusted PR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant