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
`moshcode install kimi`, `/agents kimi`, `/start kimi`, headless `ai()`, and
the skill fan-out. Aliases: kimi-cli, kimi-code, moonshot.
Verified against the real binary (Kimi Code 0.32.0) rather than the kimi-cli
reference docs, which describe the deprecated Python CLI and differ in ways
that matter:
- install: the kimi-code installer directly. The code.kimi.com/install.sh
wrapper those docs name now installs the deprecated kimi-cli, and it prompts
— Enter or a 30s timeout redirects to kimi-code anyway. `moshcode install`
cannot drive an installer that blocks on a human.
- agents: `--yolo` (auto-approve tool calls). No agentsView — Kimi Code has no
agent list to land on, so /agents kimi is the autonomous session.
- upgrade: `kimi upgrade`, its own native updater.
- ai(): `-p <prompt>`. There is no `--quiet`/`--final-message-only` here.
- skills: clones into $KIMI_CODE_HOME/skills (default ~/.kimi-code/skills).
- mcp: skipped with a reason. Kimi Code runs MCP servers but dropped the
`mcp add` subcommand — they live in ~/.kimi-code/mcp.json or the in-session
/mcp-config picker, and moshcode drives engines' CLIs, not their config.
Two supporting changes:
- engines gain `binDirs`, as tools already have. Kimi's installer writes to
~/.kimi-code/bin and only appends it to your shell rc, so PATH alone reports
it missing in the session that just installed it.
- the /mcp list column now reads "no mcp add command" instead of "no MCP
support". It reports what moshcode can drive; "no MCP support" would be a
false claim about kimi and send the reader looking for another engine.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
0 commit comments