AgentPeek
Download

MiMo Code sessions, approvals, and exact usage in the notch

MiMo sessions and resumable prompts, without invented limits.

Download for macOSFree 3-day trial · Apple silicon
AgentPeek monitoring a MiMo Code session, conversation, tools, and local token usage on a Mac

01

Native session, message, tool, and permission events

AgentPeek installs one managed module at ~/.config/mimocode/plugins/agentpeek.js. MiMo Code discovers that plugin from its config directory and emits session status, visible user and assistant messages, tool starts and completions, questions, errors, and deletes. AgentPeek never rewrites mimocode.json or its unknown user keys.

MiMo Code's current permission.ask plugin hook exposes one mutable status. AgentPeek can allow or deny that request once, without feedback or persistent allow.

02

Exact local conversations, tools, tokens, and recorded cost

AgentPeek reads MiMo Code's native session, message, and part rows from mimocode.db. Visible text parts build the conversation; private or ignored parts stay out. Persisted assistant-message counters supply input, output, reasoning, cache, request, and recorded USD cost totals for the current calendar month and by-day history.

This database exposes usage already recorded by the selected models. It does not expose a provider plan percentage or billing reset window, so AgentPeek does not invent one.

03

Direct Chat through mimo acp

The session composer launches mimo acp, loads the exact persisted session ID, sends the next prompt, streams assistant text and completed tools, and cancels work in flight. Native ACP permission options can be answered in the notch while AgentPeek owns that Direct Chat turn. Sessions already hosted by another ACP client remain view-only in AgentPeek.

04

Quick Routes follow MiMo Code's real roots

Quick Routes opens MiMo Code's plugins, configuration, logs, SQLite database, and data root. On macOS the defaults are ~/.config/mimocode for config and ~/Library/Application Support/mimocode for data. An absolute MIMOCODE_HOME moves them to config and data children; MIMOCODE_DB can select another database path.

Questions

Yes. AgentPeek monitors the mimo CLI through its native plugin events, reads visible conversations and exact usage from mimocode.db, and supports resumable Direct Chat through mimo acp.
Yes, for the current one-shot permission.ask status contract: allow or deny. The plugin ABI exposes neither deny feedback nor persistent allow. MiMo Code ACP also exposes native approval choices during AgentPeek-owned Direct Chat.
It sums exact persisted assistant-message token fields and recorded cost from mimocode.db for calendar-month totals and daily history. It does not infer a plan quota, percentage, or provider reset window.
No. AgentPeek writes and owns only plugins/agentpeek.js under MiMo Code's config root. Existing plugin declarations and every unknown mimocode.json key remain untouched.
Configuration defaults to ~/.config/mimocode, while mimocode.db and logs default to ~/Library/Application Support/mimocode. An absolute MIMOCODE_HOME replaces both with config and data subdirectories.

More of AgentPeek

Keep your agents in view

Download for macOSFree 3-day trial · Apple silicon