POK-313: Add MiMo Code, Oh My Pi, Mistral Vibe from AgentPeek gap analysis

[saheljalal]

Closes POK-313

Summary

Adds the three AI coding agents that AgentPeek tracks but aikit was missing,
each wired end-to-end (install / update / version-check / uninstall /
auth-discovery) following the existing registry pattern. Bumps aikit
1.15.5 → 1.16.0 (MINOR, additive) and the AGENTS count 31 → 34.

The fourth AgentPeek-tracked agent we were missing, ZCode, has no public
CLI installer (Z.ai ships it only as a signed desktop app) and is intentionally
not added — documented as a known gap in docs/aikit.md so searches land
somewhere instead of silence.

New agents

Key	Agent	Install	Version source	Auth discovery
mimo	🧬 MiMo Code (Xiaomi)	curl … mimo.xiaomi.com/install / PowerShell install.ps1	npm @mimo-ai/cli (derives npm uninstall)	~/.local/share/mimocode/auth.json (Linux) / ~/Library/Application Support/mimocode/auth.json (macOS)
omp	🥧 Oh My Pi (can1357)	curl … omp.sh/install / PowerShell install.ps1	npm @oh-my-pi/pi-coding-agent (derives npm uninstall)	~/.omp/agent/auth.json (Pi-compatible layout)
vibe	🌊 Mistral Vibe (Mistral AI)	curl … mistral.ai/vibe/install.sh / pip install mistral-vibe	PyPI mistral-vibe (explicit pip_agent_uninstall_cmd)	~/.vibe/ config dir + MISTRAL_API_KEY env var

Each new entry has: per-platform install, real version_check, working
update_cmd or update_via_install, uninstall (derived or explicit),
auth_env_vars + auth_note, path_markers, requires, tags, and a
per-agent discover_auth branch.

Gateway coverage

The three new agents land in GATEWAY_COVERAGE as pending (each with a
reason naming the gap a future renderer or env wire would close). This keeps
them visibly tracked instead of silently defaulting to unclassified.

Bucket counts: renderer 12, env 7, pending 4 → 7, unsupported 8
(total 31 → 34; unclassified stays 0).

Tests

• Updated test_aikit_new_agent_registry_entries: len(AGENTS) == 34.
• Extended test_aikit_npm_agent_uninstall_derived_from_version_check with
  mimo and omp (the npm-backed pair).
• Extended test_aikit_pip_agent_uninstall_cmds with vibe.
• Updated bucket-count assertions in test_aikit_gateway_coverage.py and
  test_aikit_gateway_passthrough.py.

Verification

$ venv/bin/python -m pytest
430 passed, 1 skipped in 7.55s

$ ./aikit list
🤖 aikit v1.16.0 — AI Coding Agent CLI Installer & Manager
… 34 rows: #9 🧬 MiMo Code, #13 🌊 Mistral Vibe, #18 🥧 Oh My Pi render correctly …

$ ./aikit doctor
  • 9/34 installed, 9 authenticated
  • Not installed: … MiMo Code, … Mistral Vibe, … Oh My Pi …

$ ./aikit gateway coverage
  ℹ️  12 renderer · 7 env · 7 pending · 8 unsupported  (9 detected)

$ ./aikit auth mimo  # / omp / vibe — same shape
  ❌ 🧬 MiMo Code is not installed. Run 'aikit install mimo' first.  (exit 1)

Files

• aikit — 3 new AGENTS entries, 3 new discover_auth branches, 3 new
  GATEWAY_COVERAGE rows, version bump in docstring + __version__, agent
  count 31 → 34 in module header + registry comment.
• tests/test_tools_characterization.py, tests/test_aikit_gateway_coverage.py,
  tests/test_aikit_gateway_passthrough.py — count + bucket assertions updated.
• docs/aikit.md — new rows 32–34 + a "Not managed" section for ZCode;
  31 → 34 everywhere the count appears.
• docs/aikit-gateway.md, README.md — count updates.
• CHANGELOG.md — new ### 1.16.0 — 2026-07-19 section.

[saheljalal]

Review — POK-313 (aikit 1.16.0: +mimo, +omp, +vibe)

Solid, well-scoped PR. The three new entries follow the existing registry pattern faithfully, version-bump discipline is clean (1.15.5 → 1.16.0 MINOR, all four sync points updated: docstring, __version__, docs H1, CHANGELOG), tests are surgical with annotated assertion deltas, and the GATEWAY_COVERAGE classification choice (pending with concrete reason strings) is exactly the right call — visibly tracked rather than silently defaulted. All 430 tests pass + 1 pre-existing skip, confirmed locally.

Verdict: Request changes — one Should-fix to verify/complete the omp + mimo uninstall path before merge, plus a few minor nits. vibe is clean.

🟡 Should-fix

• aikit:468 / aikit:685 (omp & mimo uninstall is half-wired). Both entries install via curl | sh but rely on version_check: {type: npm} to derive npm uninstall -g @oh-my-pi/pi-coding-agent / npm uninstall -g @mimo-ai/cli. If the curl installer doesn't install via npm under the hood (Pi forks like omp typically ship a compiled single binary, not an npm-wrapped one), then aikit uninstall omp will print a command that's a no-op against the actual install aikit itself performed — and the user is left with a fully-working omp/mimo binary plus a ~/.omp/ / ~/.local/share/mimocode/ data dir that the same PR's discover_auth and path_markers point at. I smoke-tested resolve_uninstall_cmd() for both: neither touches the vendor dir. This contradicts the PR's stated "no half-wired fields" contract. Two options:
  1. Confirm the curl installers ultimately run npm i -g and reply with that evidence (in which case the derived uninstall removes the package but still leaves the data dir — consider binary_uninstall_cmd(..., vendor_dirs=[...]) like grok/kimi/claude use, to clean ~/.omp and ~/.local/share/mimocode too).
  2. Add an explicit uninstall_cmd (e.g. binary_uninstall_cmd("omp", vendor_dirs=["$HOME/.omp"])) and drop omp/mimo from test_aikit_npm_agent_uninstall_derived_from_version_check.
     vibe is fine — pip_agent_uninstall_cmd already does the rm -f $HOME/.local/bin/vibe binary cleanup.
     Note: qwen has the same latent gap (systemic), but since this PR's whole premise is "works end to end / no half-wired entries," it's worth getting omp/mimo right here and filing a separate issue for qwen + the rest of the curl-install-with-npm-version_check family.

⚪ Nits (mimo entry polish — bundle as you see fit)

• aikit:465 — Windows install uses powershell -ep Bypass -c "irm … | iex", but no other agent in the registry uses -ep Bypass. irm | iex streams the script (it isn't a local .ps1), so ExecutionPolicy doesn't apply — -ep Bypass looks cargo-culted. Drop it for consistency with the other 33 entries, unless MiMo's installer genuinely requires it (in which case a one-line comment helps).
• aikit:470 — path_markers includes /.mimocode/ but neither the auth_note nor discover_auth reference that path (they use ~/.config/mimocode/ and ~/.local/share/mimocode/). Either align the marker to a path the install actually writes, or drop it.
• aikit:2767 — discover_auth comment claims MIMOCODE_HOME relocates both, but the branch only checks the two hardcoded paths and never reads MIMOCODE_HOME. Either honor the env override or drop the claim — as-is the comment promises behavior the code doesn't implement.

✅ Praise

• aikit:4158-4163 — classifying the three new agents as pending with reason strings that name the exact config path / env var a future renderer or env wire would touch is the right call. It keeps the agents visibly tracked and the gap actionable, instead of letting them fall into the silent unclassified default. This is the anti-silent-omission guarantee applied well.
• Discover-auth branches correctly guard on if data: and handle JSONDecodeError/OSError consistently with the surrounding code — good defensive mirror of the existing pi/hermes/kilo branches.
• Test updates are annotated with # POK-313: comments at every assertion delta — easy to audit.

Once omp/mimo uninstall is verified or wired with an explicit cmd, this is an approve.

[saheljalal]

🟡 Should-fix: derived npm uninstall won't reliably clean up a curl-installed omp.

omp installs via curl -fsSL https://omp.sh/install | sh, but with no explicit uninstall_cmd the npm version_check derives npm uninstall -g @oh-my-pi/pi-coding-agent. If omp.sh/install ships a compiled single binary (typical for can1357's Pi fork — it's a bun-compiled binary, not an npm-wrapped CLI), that npm uninstall is a no-op against the actual install aikit itself performed, and ~/.omp/ (which this same PR's discover_auth reads and path_markers advertises) survives.

I smoke-tested resolve_uninstall_cmd(AGENTS["omp"]) → npm uninstall -g @oh-my-pi/pi-coding-agent --prefix $HOME/.local — no rm of ~/.omp or the binary.

Two options:

1. Confirm omp.sh/install ultimately runs npm i -g and reply with that evidence; or
2. Add an explicit uninstall, e.g. binary_uninstall_cmd("omp", vendor_dirs=["$HOME/.omp"]) (the grok/kimi/claude pattern), and move omp out of test_aikit_npm_agent_uninstall_derived_from_version_check.

Same concern applies to mimo (aikit:468) — its path_markers even include /.mimocode/, implying files land there that npm uninstall won't touch. vibe is fine — pip_agent_uninstall_cmd already does binary cleanup.

This contradicts the PR's stated "no half-wired fields" contract for the uninstall axis.

[saheljalal]

⚪ Nit: -ep Bypass is unique to mimo — no other entry in the registry uses it. irm | iex streams the script over HTTP (it isn't a local .ps1), so Windows ExecutionPolicy doesn't apply to it — the flag looks cargo-culted. Drop it to match the other 33 entries (powershell -c "irm … | iex"), unless MiMo's installer genuinely requires it.

Two more mimo-entry polish items while I'm here:

• path_markers (line 470) includes /.mimocode/, but neither the auth_note nor discover_auth references that path — they use ~/.config/mimocode/ and ~/.local/share/mimocode/. Align or drop.
• The discover_auth comment (aikit:2767) says MIMOCODE_HOME relocates both, but the branch only checks the two hardcoded paths and never reads MIMOCODE_HOME. Either honor the env override or drop the claim.

[saheljalal]

✅ Praise: classifying the three new agents as pending with concrete reason strings is exactly right.

The reasons name the precise config path or env var a future renderer or env wire would touch (~/.config/mimocode/mimocode.json, ~/.omp/agent/models.yml, OPENAI_BASE_URL/MISTRAL_BASE_URL), so the gap stays actionable rather than becoming a mystery. This is the anti-silent-omission guarantee (test_coverage_classifies_every_agent + assert "unclassified" not in counts) applied the way it was designed — keep these visibly tracked rather than letting them default into unclassified.

[saheljalal]

Re-review — POK-313 (aikit 1.16.0: +mimo, +omp, +vibe) ✅ Approved

All four prior findings addressed correctly; no new issues introduced. Full suite re-run locally: 431 passed, 1 skipped (matches the author's claim, +1 from the new test_aikit_curl_installed_npm_version_check_agents_have_explicit_uninstall test). CI green.

Prior findings — resolved

• 🟡 Should-fix: omp + mimo uninstall half-wired ✅ resolved.

  • mimo_uninstall_cmd() correctly removes the binary at its real curl-install path (~/.mimocode/bin/mimo{,.bak}) plus all the XDG config/data dirs (~/.mimocode, ~/.config/mimocode, ~/.local/share/mimocode, ~/Library/Application Support/mimocode, ~/.cache/mimocode). Covers every dir discover_auth reads.
  • omp_uninstall_cmd() (Grok pattern) removes ~/.local/bin/omp + ~/.omp/.
  • Both uninstall_removes_vendor_data = True, so the confirmation prompt fires on uninstall (same shape as kimi/grok/claude).
  • New test test_aikit_curl_installed_npm_version_check_agents_have_explicit_uninstall pins the contract on four axes — most importantly that the derived npm uninstall -g … is NOT what runs. Good design: this is now a reusable invariant for any future curl-install + npm-version_check agent.

• ⚪ Nit 1: mimo Windows -ep Bypass ✅ dropped — now plain powershell -c "irm … | iex", matching omp/codex/grok/pi.

• ⚪ Nit 2: mimo path_markers alignment ✅ aligned — now ["/.mimocode/", "/.config/mimocode", "@mimo-ai/cli"] (matches install + discover paths). Bonus: added install_paths: ["~/.mimocode/bin/mimo"] (matches kimi) so resolve_agent_bin finds the binary off-PATH, and flipped requires from ["node", "npm"] to ["curl"] — a real correctness improvement since the curl installer the entry points at doesn't need node locally.

• ⚪ Nit 3: discover_auth MIMOCODE_HOME claim ✅ corrected — comment now honestly says "we don't honor it here" and points at the default XDG paths the code actually checks.

✅ Praise

• Verification of the curl install mechanism (omp.sh/install → bun install -g; mimo.xiaomi.com/install → self-contained binary at ~/.mimocode/bin/) is exactly the kind of evidence that should accompany a fix like this. Turned an assertion into a confirmed fact.
• The new test doesn't just assert the fix — it asserts the contract for the whole class of curl-installed-but-npm-version-checked agents. The next agent added with this shape gets the invariant for free.

Approved — ready for human merge. Out-of-scope qwen systemic-uninstall audit the author flagged is a good candidate for a separate follow-up issue.