You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Servers panel lists the Claude CLI's own port when a mod registers a tool #36173
Start a Claude thread in T3 Code and send any message.
Open the thread details panel.
Expected behavior
The Servers section lists only servers that the thread's agent or terminals started.
Actual behavior
The Servers section lists the Claude CLI itself, for example localhost:62403 · Agent · 2.1.323 (the CLI's version is the process name). The page at that port returns 404 not found. The row shows in every Claude thread.
Cause: Claude Code holds a loopback port when a plugin registers a tool with $.tool.register. ClaudeAdapterV2 launches the CLI with T3CODE_THREAD_ID in its own environment. PortScanner attributes every listener whose process carries that variable to the thread, so the CLI's own port reads as a server it started.
Without such a mod the CLI holds no port. An empty mod, a skills-only plugin, or a mod that adds its tool through a tool.list hook (mcp: false) does not trigger it.
Impact
Cosmetic issue
Version or commit
T3 Code Nightly 0.1.10-nightly.20261113.4630. Reproduced on main at 2d8a843 with vp run dev.
Environment
macOS 27.0.1, Claude Code 2.1.323. The Linux path reads the same environment variable, so it should behave the same. I did not check Linux.
Another reproduction of this. Claude Code 2.1.325 in a Claude thread (T3 Code, macOS) shows localhost:64192 · Agent · 2.1.325 in the Servers section of the thread details panel.
I checked the port: lsof shows it is held by the session's own claude --output-format stream-json … process, not by anything the agent or a terminal started. A mod in this session registers a tool through $.tool.register, which matches the cause described above.
Suggested fix: when PortScanner attributes listeners to a thread, skip the thread's own agent process (for example by PID, or by checking the process is the adapter's CLI) and only list descendants it spawned.
Fixed by #38916, now on main: With a Claude mod registering a tool, the Servers panel now excludes the Claude CLI's own loopback listener while retaining servers its commands start.
Activity
jsc2304 commentedon Nov 15, 2026
Another reproduction of this. Claude Code 2.1.325 in a Claude thread (T3 Code, macOS) shows
localhost:64192 · Agent · 2.1.325in the Servers section of the thread details panel.I checked the port:
lsofshows it is held by the session's ownclaude --output-format stream-json …process, not by anything the agent or a terminal started. A mod in this session registers a tool through$.tool.register, which matches the cause described above.Suggested fix: when
PortScannerattributes listeners to a thread, skip the thread's own agent process (for example by PID, or by checking the process is the adapter's CLI) and only list descendants it spawned.juliusmarminge commentedon Nov 19, 2026
Fixed by #38916, now on main: With a Claude mod registering a tool, the Servers panel now excludes the Claude CLI's own loopback listener while retaining servers its commands start.