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
mcp: register with qwen too, and stop calling a re-install a failure (#427)
`mcp install` already fanned out to Claude Code, but a re-run reported it
as `claude ✗ failed (code 1)` — Claude Code exits 1 with "already exists in
user config" — while opencode printed a green box for the same no-op. Read
from a box where the server was already registered, that summary says
moshcode cannot register with Claude Code, which is the wrong conclusion.
- qwen joins MCP_ENGINES. Qwen Code is a Gemini CLI fork and kept the whole
`mcp add` surface (-s/-t/-e/-H, "URL or command" positional), verified
against its own --help, so it shares gemini's argv builder rather than
getting a copy. Checked and left alone: kimi still has no `mcp`
subcommand, openagents exposes an MCP server rather than registering one,
deepseek-code exits silently, aider has none.
- An engine that says the server is already there now reports `already
registered` in grey instead of a red failure, and no longer makes the
command exit 1. runCmd grew an opt-in `capture` that tees the child's
output instead of inheriting it, so the classification reads the engine's
own words; every other caller is untouched.
- An unknown flag after a remote URL was swallowed: it landed in `args`,
which every remote builder discards. `mcp install <url> --dry-run` — a
flag mcp does not have — therefore wrote to five engines' configs and
said nothing. It is now an error, before anything runs.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
0 commit comments