Skip to content

The intent behind every change your coding agent makes

Wisdom records Claude Code, Codex and Pi sessions on your machine and links every file change to the request and the commands behind it. You read them in a dashboard; your agents read them through a skill.
Install and connect
npm install -g @oqura/wisdom
cd your-project
wisdom connect
claude # or codex, or pi: use it as usual

Then read what happened: the session at a glance, then any turn in full, or start from the commit it made. Below is an example session, written to show the format.

~/invoice-api
❯ wisdom glance latest
session 3f9c2a71-8d4e-4b1a-9c55-2e7f0b6d1a90 · claude-code 2.1.319 · closed (idle) · version 412
resume with: wisdom resume 3f9c2a71-8d4e-4b1a-9c55-2e7f0b6d1a90
workspace /home/maya/invoice-api
started 2026-11-11 09:12Z · ended 2026-11-11 09:41Z
3 turns · 14 tool calls · 1 failed · 3 changes · 0 subagents · 412,906 tokens · $1.8420 reported
t1 in totals are off by a cent on some invoices, find out why
out Each line item is rounded before the sum, so cents drift on long invoices.
6 tool calls · no changes
t2 in fix it and add a test
out Totals now round once, after the sum. A new test covers a 40-line invoice.
7 tool calls · 1 failed · changed src/totals.ts, test/totals.test.ts
t3 in commit it
out Committed as a4c91e2 "fix: round invoice totals once".
1 tool call · no changes
complete · 17 lines
  • Prompts, replies, tool calls and file diffs, recorded as they happened. Nothing is summarized, and gaps in the recording are marked where they occur.
  • One way to read Claude Code, Codex and Pi sessions: for you in the terminal or the dashboard, for your agents through a skill.
  • From any commit back to the steps that made it, with wisdom glance --commit (new in 0.6.0).
  • Hooks that never block your agent. If the background service is down, events wait on disk.
  • Everything stays in the project’s .wisdom/ folder until you choose to share it.

Start with the quick start, or read how it works.