# Reading the undocumented session logs of Claude Code, Codex and Mistral Vibe

Description and use

<p>Oct 16, 2026 · <a class="mentioned-user" href="https://dev.to/arthur">@arthur</a></p> <h2> Why read the logs at all </h2> <p>Claude Code, Codex and Mistral Vibe all write everything they do to disk, as they do it, and none of them documents the format. If you run a few sessions that spawn sub-agents, those files are the only place that knows which agent is still working, which one is waiting on another, and which session is sitting on a prompt for you.</p> <p>I build <a href="https://github.com/Atoll92/agent-standup" rel="noopener noreferrer">Agent Standup</a>, an open-source tool that read

Problem

<p>Oct 16, 2026 · <a class="mentioned-user" href="https://dev.to/arthur">@arthur</a></p> <h2> Why read the logs at all </h2> <p>Claude Code, Codex and Mistral Vibe all write everything they do to disk, as they do it, and none of them documents the format. If you run a few sessions that spawn sub-agents, those files are the only place that knows which agent is still working, which one is waiting on another, and which session is sitting on a prompt for you.</p> <p>I build <a href="https://github.com/Atoll92/agent-standup" rel="noopener noreferrer">Agent Standup</a>, an open-source tool that read

Outcome

<p>Oct 16, 2026 · <a class="mentioned-user" href="https://dev.to/arthur">@arthur</a></p> <h2> Why read the logs at all </h2> <p>Claude Code, Codex and Mistral Vibe all write everything they do to disk, as they do it, and none of them documents the format. If you run a few sessions that spawn sub-agents, those files are the only place that knows which agent is still working, which one is waiting on another, and which session is sitting on a prompt for you.</p> <p>I build <a href="https://github.com/Atoll92/agent-standup" rel="noopener noreferrer">Agent Standup</a>, an open-source tool that read

Evidence

Reading the undocumented session logs of Claude Code, Codex and Mistral Vibe

Source