chore(mcp): bump agent-mcp-manager to 0.0.3 and hide Claude Desktop#1393
Merged
Dani Akash (DaniAkash) merged 6 commits intoJun 26, 2026
Merged
Conversation
agent-mcp-manager 0.0.3 marks Codex as http-capable, so the Connect flow now writes Codex's config.toml with a direct url= entry instead of routing through npx mcp-remote. Claude Desktop is dropped from the Integrations panel and the manual-setup tabs because its only supported config shape needs Node on the user's machine, which is not a viable default.
Contributor
✅ Tests passed — 1429/1433
|
Contributor
Greptile SummaryThis PR updates the MCP integration behavior for Codex and Claude Desktop. The main changes are:
Confidence Score: 4/5This is close, but I would fix the legacy disconnect path before merging.
packages/browseros-agent/apps/server/src/lib/mcp-manager/service.ts Important Files Changed
Prompt To Fix All With AIFix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 1
packages/browseros-agent/apps/server/src/lib/mcp-manager/service.ts:114
**Legacy links disappear**
This check only treats `browseros` and `browseros-stdio` as BrowserOS links. Legacy per-profile installs link agents under the profile slug, so an existing Claude Desktop profile created through that path can still have an active BrowserOS-managed link while being removed from `linkedSet` here. `listAgents()` then filters out `claude-desktop`, and the Integrations UI cannot show the Disconnect row needed to remove the stale config entry.
Reviews (3): Last reviewed commit: "feat(claw-app): retire Claude Desktop fr..." | Re-trigger Greptile |
Hiding Claude Desktop unconditionally left users who had linked it via a previous release stranded with an orphan entry and no UI to Disconnect. listAgents now keeps a hidden agent in the result whenever it still has an active BrowserOS link, and removes it from the next refresh after the user clicks Disconnect. Restored the Claude Desktop presentation row and brand mark so the legacy tile renders with the right label until that point.
Contributor
Author
claw-server's specFor maintained a hardcoded STDIO_ONLY={'codex'} set so Codex installs still wrote a 'npx mcp-remote' spec even after the 0.0.3 bump that flipped Codex to http-capable. specFor now reads supportedTransports from resolveAgentSurface, matching the apps/server planFor approach, so future upstream transport changes propagate without editing a parallel allow-list. The Claude Desktop harness install test now asserts the stdio shape its config parser actually accepts.
Mirrors the apps/server HIDDEN_AGENTS rationale: Claude Desktop's config parser only accepts stdio entries and the recommended npx mcp-remote bridge needs Node on the user's machine, so a fresh user picking it has no reliable install path. SELECTABLE_HARNESSES (the picker source) drops it, while the full HARNESSES set and the data-layer schema still accept it so existing profiles parse, render with the right icon, and can be uninstalled. Codex HTTP routing is already handled server-side by specFor's resolveAgentSurface refactor in aa76455.
Contributor
Author
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.
agent-mcp-manager 0.0.3 (release notes) marks Codex as http-capable. The Connect flow now writes Codex's
~/.codex/config.tomlwith a directurl = "<browseros-url>"entry instead of wrapping it innpx mcp-remote, so Codex users without Node on their machine still get a working integration.Claude Desktop is hidden from the Integrations panel and the manual-setup tabs.
claude_desktop_config.jsonaccepts stdio entries only, and the recommendednpx mcp-remotebridge requires Node — which silently breaks the Connect flow for non-developer users. Bringing Claude Desktop back is tracked separately as a bundled-runtime extension; until then, hiding it is the honest default.