| name | ai-provider |
| description | Reference for where Claude and Codex provider data is stored on disk — session logs, raw output, thinking/reasoning availability, and format differences between the two providers. Use whenever investigating provider output, debugging missing thinking blocks, reading session history, or asking "where does X get stored for Claude vs Codex?" |
AI Provider Storage Reference
Claude
Session logs
~/.claude/projects/<path-based-id>/<session-id>.jsonl
The path-based ID is derived from the working directory (e.g., -Users-bill-Developer-personal-AIDevTools). Each line is a structured JSONL event covering tool calls, text output, thinking, and metrics.
App-level logs
~/Library/Logs/AIDevTools/aidevtools.log
Structured JSON log used by the Mac app and CLI. Filter with jq by label field.
Eval artifacts (raw provider output)
~/Desktop/ai-dev-tools/services/evals/AIDevTools/artifacts/raw/claude/<suite>.<case-id>.stdout
Only written during eval runs, not during chat sessions.
Thinking blocks
Claude thinking blocks are present in the exec stream as plain text events and are fully parseable. The ClaudeStreamFormatter.formatStructured() emits .thinking(text) events which the Mac app renders as purple collapsible blocks.
Codex
Native session logs
~/.codex/sessions/YYYY/MM/DD/rollout-<timestamp>-<uuid>.jsonl
Codex writes a session file for every invocation — both from the native TUI (originator: "codex-tui") and from codex exec (originator: "codex_exec"). Each line is a rich event object.
Key event types in the native format:
