Agent Architecture

MiMoCode

MiMoCode is a terminal-native Xiaomi MiMo coding assistant with agents, persistent SQLite FTS5 memory, checkpoint reconstruction, task tracking, subagents, goal judging, compose mode, voice input, and JSON/JSONC config files.

Source reviewed #10Checked 2026-07-06

Setup guide Source

Run type

CLI

Adapter

ts-plugin

Source

OSS · XiaomiMiMo/MiMo-Code

Stars

★ 13k

Archive Context

This page is one host entry inside the full architecture archive and keeps multi-surface products visible instead of collapsing them into a single run type.

42 host archive

Host page

mimo-code

Run cohort

CLI: 30

Archive route

/agents

Host Surface Perspectives

The host is the primary architecture boundary. Each runnable surface below separates what the host owns from what agent-connector can safely install for MiMoCode.

1 surface entry

CLI

cli

Host entry: A terminal command owns the process, current working directory, stdin/stdout, shell environment, and project file discovery.
Host owns: The CLI host owns agent loop timing, approval prompts, tool execution, session files, and how hook or MCP subprocesses are launched.
Connector role: agent-connector can only write the host's documented CLI config, prompt, memory, hook, MCP, or package files and point them at the home binary. Current wired connector surfaces: MCP server, Hooks, Commands, Skills, Subagents, Memory.
Implementation consequence: A CLI surface is byte-addressable and smoke-testable from a temporary HOME, but terminal UI behavior still belongs to the host process. No visible host-native gap is currently tracked for this surface.

Verified Architecture

Source-checked on 2026-07-06. These notes are intentionally separate from the generated surface matrix below.

Sequence #10

Source pass

Current source review findings are kept as the first architecture section so readers can separate external evidence from the generated local coverage model.

MiMoCode is documented as a terminal-native AI coding assistant that reads and writes code, runs commands, manages Git, and keeps persistent memory.
The repository exposes first-party project and user config paths under `.mimocode` and user config directories, matching a CLI-local architecture.
Multiple agents, persistent memory, checkpoints, task progress, and goal judging are host-native primitives that should remain visible in the archive page.

Runtime boundary

The adapter target is the terminal-native `mimo` CLI. MiMoCode owns the TUI, command execution, Git operations, provider selection, memory injection, subagent scheduling, checkpointing, and voice input.

The repository describes MiMoCode as terminal-native and able to read/write code, run commands, and manage Git.
Install paths include curl, npm, and Windows PowerShell.

MCP registration

MiMoCode is tracked as a TypeScript-plugin style host in the connector matrix, but the public README emphasizes memory, agents, provider setup, and workflow modes more than MCP. MCP claims should stay adapter-backed.

Configuration files live under `.mimocode` for projects and `~/.config/mimocode` globally.
Provider setup supports MiMo Auto, Xiaomi MiMo Platform, Claude Code import, and custom OpenAI-compatible APIs.

Hook bridge

MiMoCode's runtime has rich lifecycle concepts, but connector hook support should be described through the TypeScript/plugin adapter. Subagent lifecycle tracking, checkpointing, and goal judging are host behavior unless exposed as plugin events.

The `/goal` command uses an independent judge model to prevent premature stops.
Subagents can run in parallel with lifecycle tracking, cancellation, and background execution.

Content surfaces

MiMoCode content surfaces are explicit: `MEMORY.md`, `checkpoint.md`, `notes.md`, per-task progress logs, compose-mode skills, task trees, and config files. This row should be a reference for memory architecture.

Memory is powered by SQLite FTS5 and injected on resume.
`/dream` extracts persistent knowledge and `/distill` packages repeated workflows into skills, subagents, or commands.

Marketplace and host-only affordances

The host-only affordance is a self-improving terminal workflow with persistent memory, dream/distill loops, voice, task hierarchy, and compose mode. Those features should be visible beside connector chips.

MiMo models also work in other agents such as Cursor, Cline, and Zed.
Voice and ASR features are host capabilities, not generic connector features.

Host-specific shape

MiMoCode follows the OpenCode fork architecture: ts-plugin bridge plus MCP, commands, skills, subagents, and memory until a verified product divergence appears.

Form factor: CLI.
Native surfaces: MCP server, Hooks, Commands, Skills, Subagents, Memory.
Wired surfaces: MCP server, Hooks, Commands, Skills, Subagents, Memory.
Visible gaps: none.

Hooks

Hooks enter through a generated plugin module that the host loads in its own runtime.

MCP

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory

Managed memory text is written into the rules or memory file this host actually reads, with ownership markers for reversible uninstall.

Marketplace and affordances

The plugin bridge is generated directly, but there is no separate drivable marketplace path in the current driver registry.

Runtime handlers: none.
User-visible affordances: Users see managed commands + skills + subagents + memory surfaces after install; runtime-only surfaces stay behind the host boundary..

Known Limits

Do not equate MiMo model provider support in other tools with MiMoCode host support.
MCP and hook specifics should stay adapter-tested.
Memory semantics are MiMoCode-owned and richer than generic connector memory.

Evidence checked

MiMo-Code repository MiMo website

Architecture Diagram

Host-specific flow for the CLI surface.

ts-plugin

1
Entry point: CLI
Terminal agent process reads user/project config and invokes the connector home binary for runtime callbacks.
2
Connector package
defineConnector package declares server, hooks, content, memory, and actions.
3
Adapter module: mimo-code
ts-plugin renderer at src/adapters/mimo-code/index.ts.
4
Native host artifacts
Adapter writes MCP config + plugin module + content files + memory/rules through this host's native file, package, or marketplace surface.
5
Runtime boundary
host loads generated TypeScript plugin bridge
6
User-visible surface
Users see managed commands + skills + subagents + memory surfaces after install; runtime-only surfaces stay behind the host boundary.
7
Coverage ceiling
6/6 native surfaces wired. No visible host-native gap in the current coverage matrix.

Component Diagram

Static parts of the MiMoCode integration and which side owns each one.

MiMoCode host
CLI surface owns the model loop, UI shell, config discovery, and native lifecycle for this integration.
agent-connector package
Normalizes connector declarations into MCP, hook, memory, content, and action payloads before delegating to a host adapter.
mimo-code adapter
Implements the ts-plugin translation layer in src/adapters/mimo-code/index.ts.
Native artifacts
Adapter writes MCP config + plugin module + content files + memory/rules through this host's native file, package, or marketplace surface.
Runtime bridge
host loads generated TypeScript plugin bridge
User-visible surface
Users see managed commands + skills + subagents + memory surfaces after install; runtime-only surfaces stay behind the host boundary.

Runtime Sequence Flow

Message order from install to runtime for the CLI surface.

1 · User / project
Choose host adapter
Install or update starts against MiMoCode; the selected surface is CLI.
2 · agent-connector
Resolve connector declaration
The package reads connector metadata and routes it to the mimo-code adapter instead of exposing a generic host contract.
3 · mimo-code adapter
Render host-native shape
Adapter writes MCP config + plugin module + content files + memory/rules through this host's native file, package, or marketplace surface.
4 · MiMoCode
Host loads artifacts
host loads generated TypeScript plugin bridge
5 · Agent runtime
Run through host boundary
Users see managed commands + skills + subagents + memory surfaces after install; runtime-only surfaces stay behind the host boundary.
6 · Coverage matrix
Expose remaining ceiling
6/6 native surfaces wired. No visible host-native gap in the current coverage matrix.

Architecture Archive

The same five study axes are rendered for every host: runtime shape, hooks, MCP, memory, and host-only affordances.

Host-specific shape

MiMoCode follows the OpenCode fork architecture: ts-plugin bridge plus MCP, commands, skills, subagents, and memory until a verified product divergence appears.

Form factor: CLI.
Native surfaces: MCP server, Hooks, Commands, Skills, Subagents, Memory.
Wired surfaces: MCP server, Hooks, Commands, Skills, Subagents, Memory.
Visible gaps: none.

Hooks

Hooks enter through a generated plugin module that the host loads in its own runtime.

MCP

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory

Managed memory text is written into the rules or memory file this host actually reads, with ownership markers for reversible uninstall.

Marketplace and affordances

The plugin bridge is generated directly, but there is no separate drivable marketplace path in the current driver registry.

Runtime handlers: none.
User-visible affordances: Users see managed commands + skills + subagents + memory surfaces after install; runtime-only surfaces stay behind the host boundary..

Special Feature Inventory

Host-specific capabilities separated from the generic surface matrix: lifecycle hooks, MCP registration, memory/rules, marketplace delivery, and UI or content affordances owned by the host.

Lifecycle hooks

Wired

Hooks enter through a generated plugin module that the host loads in its own runtime.

MCP registration

Wired

The adapter writes this host's native MCP registration dialect, including its root key, scope, transport fields, and environment syntax.

Memory and rules

Wired

Managed memory text is written into the rules or memory file this host actually reads, with ownership markers for reversible uninstall.

Marketplace delivery

Direct plugin

The plugin bridge is generated directly, but there is no separate drivable marketplace path in the current driver registry.

Host-only affordances

3/3 wired

Wired host affordances: Commands, Skills, Subagents. Host-native gaps: none. Not confirmed: Statusline handler, Action affordances.

Source Review Notes

Latest source pass for host-specific architecture details. This is separate from generated adapter coverage and local drift guards.

Checked 2026-07-06Open review source

XiaomiMiMo/MiMo-Code repository

MiMoCode is documented as a terminal-native AI coding assistant that reads and writes code, runs commands, manages Git, and keeps persistent memory.
The repository exposes first-party project and user config paths under `.mimocode` and user config directories, matching a CLI-local architecture.
Multiple agents, persistent memory, checkpoints, task progress, and goal judging are host-native primitives that should remain visible in the archive page.

Evidence Map

Each host page ties public source evidence to the local adapter and drift guards that keep the rendered archive aligned with code.

Public source: XiaomiMiMo/MiMo-Code

Primary public repository or product source used for current host status and source links.

external

Open source

Local adapter implementation

Defines the install/uninstall behavior, native config rendering, capability flags, and any runtime parse/format bridge for this host.

local

src/adapters/mimo-code/index.ts

Platform metadata and host-native matrix

Records the form factor, public source target, ranking source, native host surfaces, and current agent-connector coverage cells.

local

site/src/platform-data.ts

Architecture drift guard

Asserts that every registered host has a page, diagram, host-specific brief, source link, form-factor band, and adapter-aligned surface data.

local

tests/docs/platform-drift.test.ts

Runtime Shape

The host loads a generated TypeScript plugin module that bridges in-process host events to the connector runtime.

MCP registration: Wired through this adapter
Hook bridge: Wired

Connector Surfaces

Static content

MCP server, Hooks, Commands, Skills, Subagents, Memory

Runtime handlers

No runtime handler surfaces wired

Surface Matrix

Wired means agent-connector installs it now. Host native marks support we know about but have not wired yet.

SurfaceStatus

MCP server

Static content