CLI and interactive TUI sessions
Run cline, cline -i, or cline --tui. AgentPeek keeps the session labeled by project in the notch, with its runtime state, prompts, assistant messages, tool activity, files, commands, diffs, and terminal close at hand.
A global Cline CLI runtime plugin
AgentPeek installs ~/.cline/plugins/agentpeek.ts, a normal plugin that Cline CLI discovers globally. Other Cline hosts can emit the same feed when they enable the shared plugin runtime. Its onEvent stream reports run-started, user message-added, assistant-message, run-finished, and run-failed with Cline's session, parent-agent, conversation, run, status, and usage fields. The beforeTool and afterTool hooks carry tool calls and results without replacing Cline's runtime.
Mutating tools hold for a per-call answer
Cline's built-in run_commands, editor, and apply_patch calls pause in beforeTool until you approve or deny them. Deny with feedback sends your note back as the reason, and Open Terminal remains available. The gate is deliberately per call: Cline's plugin contract exposes no persistent Always Allow channel, and every other tool, extension tools included, stays observation-only.
Conversations and exact usage from modern local storage
Cline keeps its current session index at ~/.cline/data/db/sessions.db, with each session's manifest and ordered messages under <id>/<id>.json and <id>/<id>.messages.json inside ~/.cline/data/sessions. AgentPeek reads those files locally for conversation history and shows the calendar month's persisted input-plus-output tokens and exact recorded cost, with input, output, cache read, and cache write fields in the daily breakdown. Cline's input total already includes cache portions, so they are never added twice. No quota percentage, limit, or reset window is invented. Set CLINE_DATA_DIR and AgentPeek follows that root's db and sessions folders; CLINE_DB_DATA_DIR and CLINE_SESSION_DATA_DIR move each one on its own, and CLINE_DIR moves the whole Cline root.
Native ACP exists, but monitored sessions stay view-only
cline --acp starts native ACP for a fresh editor client. AgentPeek could not verify a session-loading path through ACP in the current Cline build, and --id resume is wired only through the interactive TUI. AgentPeek therefore does not claim Direct Chat or programmatic resume for monitored Cline sessions. Hosts using Cline's shared plugin runtime can emit the same feed, but those host sessions remain view-only in AgentPeek.
Cline folders in Quick Routes
Quick Routes opens Cline's plugins, hooks, agents, skills, rules, workflows, settings, CLI MCP, IDE MCP, sessions, the session database, and the ~/.cline root. Cline can also discover project .cline/plugins and .cline/hooks, plus the legacy editor plugin mirror under ~/Documents/Cline/Plugins; AgentPeek's managed integration stays in the global ~/.cline/plugins location.