Repository navigation
Client templates: stop MCP Inspector opening a browser when an agent runs it (mcp-inspector --version popups) - #275
Merged
seathatflowsinourveins merged 1 commit intoSep 25, 2026
Conversation
… commands MCP Inspector 2.7.0 has no version flag: `mcp-inspector --version` starts the web UI with `--version` as a stdio server command and, unless MCP_AUTO_OPEN_ENABLED=false (resolveAutoOpen in clients/web/build), opens a browser tab. On WSL that is the user's Windows browser, which then shows `spawn --version ENOENT`. Agents probing tool versions kept triggering it (latest 2026-09-25 18:58Z). Both client templates now set the variable to false for agent shells, and the recipe row says why. A bounded probe with the variable set printed no "Opening browser" line and opened nothing. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
seathatflowsinourveins
deleted the
claude/inspector-no-autoopen-20260925
branch
September 25, 2026 19:27
This was referenced Sep 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
MCP_AUTO_OPEN_ENABLED=falseto the Claude settings templateenvand to the Codex template[shell_environment_policy.set], and extends themcp-inspectorrecipe row to explain why.dcd6f0cflane:foundationadoption/templates/claude.settings.template.json,adoption/templates/codex.config.template.toml,recipes/README.md, and their registrations inmanifests/evidence.json.Why. The user kept seeing an MCP Inspector browser tab fail with
spawn --version ENOENT. MCP Inspector 2.7.0 has no version flag.mcp-inspector --versionstarts the web UI with--versionas an ad-hoc stdio server, and its web mode opens a browser unlessMCP_AUTO_OPEN_ENABLED=false(resolveAutoOpen()inclients/web/build/index.js). On WSL that is the Windows browser. Today's session transcripts show agents running it as a routine version probe: unbounded at 05:56Z and 18:58Z, and in bounded #251 probes at 06:19Z and 06:21Z.Evidence-class table
falsesource_reviewclients/web/build/index.js:1724-1729(resolveAutoOpen)MCP_AUTO_OPEN_ENABLED=false,mcp-inspector --versionstill starts the web server but prints no "Opening browser" line; the timeout ends it and no 627x listener remainslocal_integrationMCP_AUTO_OPEN_ENABLED=false setsid timeout -k 2 8 mcp-inspector --version </dev/null, thenss -ltnandpgrepsyntheticHost evidence
This workstation's
~/.claude/settings.jsonenvand~/.codex/config.toml[shell_environment_policy.set]got the same key, each with a backup. The key takes effect for sessions started after the change.Checklist
🤖 Generated with Claude Code