feat(engines): add kimi (Kimi Code) - #286
Merged
Merged
Conversation
`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>
ThreatCrush Security Scan88 finding(s) HIGH/CRITICAL: 50 | MEDIUM: 38
…and 38 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
ralyodio
marked this pull request as ready for review
August 4, 2026 13:14
ralyodio
added a commit
that referenced
this pull request
Aug 4, 2026
`/install qwen` and `/install deepseek` now resolve, alongside the kimi entry added in #286. qwen is a Gemini CLI fork, so it reuses gemini's `--approval-mode=yolo` for agent mode — `--yolo`/`-y` names the same mode, and passing both is a hard error, so only one form is wired. deepseek has no first-party CLI; `@serjm/deepseek-code` is the live community one. The two names that get suggested alongside it are dead ends: `deepseek-tui` is now a stub whose own description says it was renamed to `codewhale`, and `deepseek-cli` has not shipped since January 2025. Its package installs `dsc` and `deepseek-code`; we launch the long name, because `dsc` collides with Microsoft's Desired State Configuration binary and the short name would silently start the wrong program on a machine that has both. The agents/start test loop now writes its stub under the engine's *bin* rather than its key. Those were the same string for every engine until now; deepseek is the first where they differ, and a stub named after the key would leave nothing on PATH to find. MCP and skills fan-out stay opt-in per engine, so both new engines report "no support" there until their native `mcp add` surfaces are wired. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Merged
ralyodio
added a commit
that referenced
this pull request
Aug 4, 2026
Three more coding engines you can install and drive: Kimi Code, Qwen Code, and DeepSeek Code (#286, #287). `moshcode install kimi | qwen | deepseek` now resolve, each with reviewed autonomous-mode flags behind `agents` and a headless mode behind moshscript's ai(). Two of those entries route around a bad name. kimi installs the kimi-code script directly, because the older code.kimi.com wrapper now installs the deprecated Python kimi-cli and blocks on a prompt for 30 seconds. deepseek launches `deepseek-code` rather than the `dsc` alias its package also installs, because `dsc` is Microsoft's Desired State Configuration binary on a machine that has both. `template list` grew a --json form for automation (#284). Also fixes a DoH config that dropped its default guards when only one of them was overridden (#285). Minor, not patch: three new engines and a new output format. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Adds
kimito moshcode's engines, somoshcode install kimi,/agents kimi,/start kimi, headlessai(), and the skill fan-out all work.Aliases:
kimi-cli,kimi-code,moonshot.Verified against the binary, not the docs
The kimi-cli reference documents the deprecated Python kimi-cli. The maintained product is Kimi Code, and it differs in ways that would have shipped broken:
code.kimi.com/install.shcode.kimi.com/kimi-code/install.shuv tool upgrade kimi-clikimi upgrade--quiet -p-p(no--quiet)kimi mcp add …~/.kimi/skills~/.kimi-code/skillsThe
install.shthe docs name now prompts and, on Enter or a 30s timeout, silently redirects to the kimi-code installer.moshcode installcan't drive an installer that blocks on a human, so it calls the real one directly.Details
--yolo(auto-approves tool calls, agent may still ask). NoagentsView— Kimi Code has no agent list to land on, so/agents kimiis the autonomous session. (--autoalso suppresses questions; that's a step past what/agentsmeans for the other engines.)mcp add— they live in~/.kimi-code/mcp.jsonor the in-session/mcp-configpicker, and moshcode drives engines' CLIs rather than writing their config files.Two supporting changes
binDirs, which tools already had. Kimi's installer writes to~/.kimi-code/binand only appends it to your shell rc, so PATH alone reports it missing in the session that just installed it./mcp listnow reads "no mcp add command" rather than "no MCP support". The column reports what moshcode can drive; "no MCP support" would be a false claim about kimi and send the reader hunting for an engine they already have.Testing
Full suite green (1242 tests, 0 fail). End-to-end against a real Kimi Code 0.32.0 install:
moshcode enginesshows it installed, andmoshcode start kimi --versionpasses through and prints0.32.0.🤖 Generated with Claude Code