What problem does it solve? Developers modifying the MiniMax Code CLI need to understand its layered architecture—command registration, interactive TUI, headless exec, and ACP adapters—before making changes, or they risk fixing one adapter while breaking others. ## Core Features & Use Cases - Architecture Map: Documents entry points from packages/tui/src/index.ts through command registration, TUI, headless exec, ACP protocol adapters, and the in-process CliService runtime boundary. - Change Guidance: Directs where to inspect parsing, dispatch, rendering, output settlement, and protocol handling depending on whether you modify commands, interactive behavior, exec, or ACP. - Verification Workflow: Prescribes building the standalone artifact and checking real --help output, plus smoke/BYOK tests with temporary data directories. - Use Case: When adding a new CLI flag, follow the guide to update cli/program.ts and cli/contract.ts together, then verify with node dist/cli.js --help after pnpm build. ## Quick Start Ask the agent to add a new flag to the exec command and verify it appears in the built CLI help output.