Mistral Vibe sessions, Direct Chat, and usage in the notch

Run vibe in a terminal and AgentPeek projects the session into the notch with its project, state, visible conversation, model, tool activity, tokens, and nested agents. Mistral's separate vibe-acp executable provides the native Agent Client Protocol transport used by Direct Chat.

Ambient monitoring is observation-only. AgentPeek installs no Mistral Vibe hook and does not mutate hooks.toml. It reads each ~/.vibe/logs/session/session_... directory's meta.json and messages.jsonl, then groups child sessions found under the parent's agents directory. Set VIBE_HOME and AgentPeek follows that root instead of ~/.vibe. Private reasoning and tool output are not presented as assistant chat.

The session composer launches vibe-acp, loads the persisted session ID, sends the next prompt, streams replies and completed tool activity, and cancels work in flight. Native ACP permission options can be answered in the notch while AgentPeek owns that Direct Chat turn. Ambient terminal approvals remain in Vibe.

AgentPeek reads stats.session_prompt_tokens plus stats.session_completion_tokens from each main and nested-agent session record. Vibe stores one cumulative snapshot per session, not per-call timestamps, so calendar-month and daily views attribute that snapshot to its latest saved end_time. Vibe stores no cache counters. This local store exposes no provider quota percentage, reset window, or exact cost, so AgentPeek does not invent one.

Quick Routes opens Vibe's agents, skills, tools, config, hooks, sessions, logs, and root. Every route follows VIBE_HOME when it is set.