type: decision
status: active
timestamp: 2026-07-02
tags: [fleet, agents, cc, drops]

Fleet cut to Claude Code only (2026-07-02)

Drop ZCode, OpenCode, Kilo Code, Antigravity, MiMoCode from installed fleet. Claude Code + Bedrock chain is the sole agent.

Fleet cut to Claude Code only

Fleet = 1. Claude Code + Bedrock chain. Everything else dropped.

What dropped

AgentDrop reason
ZCodeGUI IDE. Manual install, GUI-only MCP config (no .mcp.json sync). Second surface to maintain, no CLI parity. Corp laptop already has Claude Code; personal doesn’t need a heavyweight IDE.
OpenCodePersonal-only CLI. Format-transformed MCP config (.opencode/opencode.jsonc) = sync-script complexity. Failover-only role; never used as primary this quarter. Cost of transform > value of failover.
Kilo CodeVS Code extension. Extension surface changes per VS Code release; MCP schema drifts. Dual-machine but never picked over Claude Code on corp.
AntigravityStandalone Google IDE. Personal-only, manual install, no headless mode. Standalone binary + separate MCP config = third surface for zero unique capability.
MiMoCode (mimo)Xiaomi CLI. PATH caveat on Windows (Git Bash only), install script writes to ~/.bashrc, invisible in PowerShell. Small ecosystem, unproven daily-driver. Sync/PATH tax > differentiating value (same pattern as gocode/Codeep/Claurst/Coddy drop on 2026-07-01).

What kept

Claude Code + Bedrock chain. Corp-paid Bedrock via Hr proxy (localhost:8787 → hai :6655 → Bedrock). Single agent, single chain, single config. Reads .mcp.json natively — no sync script needed.

Personal laptop consequence: no Claude Code available (no free tier + no-card-on-file rule blocks personal install). Personal machine is agent-less until a free-tier CLI passes the parity bar.

AGENTS.md stays canonical family-wide

AGENTS.md remains the workspace source of truth. Other CLIs, human readers, and future agents still read it. Only the fleet installation drops — the rules, decisions, and knowledge tree are agent-agnostic.

Submodule-level configs (90-day cooldown)

Files stay but stop being synced:

Flag for deletion after 2026-10-02 (90 days). Rationale for cooldown: preserves diff history in case a dropped agent gets reintroduced with valid rebuttal.

If reintroduction happens before cooldown expires: config already exists, sync resumes, minimal churn.

If cooldown expires with no reintroduction: git rm the files per knowledge-deletion-not-supersession. Do NOT flag with status: deprecated — hard-delete.

Reintroduction bar

Reintroducing any dropped agent requires:

  1. Cite this decision by path in the reintroduction PR body.
  2. Rebut the specific drop reason in the table above. Generic “it’s popular now” or “I want to try it” does not clear the bar.
  3. Grill-me session per no-global-config-without-grilling — same rigor as any new agent.
  4. Update fleet parity rule in the same commit (three-place update per agents-md-three-place-update).

Impact on rules

Three rules need edits in the same session as this decision commits:

Impact on AGENTS.md

Sections to edit:

Anti-patterns

Cross-refs


Edit on GitHub · Back to index