Guides
Let agents read sessions
The skill every connected agent gets, what to ask it, and the optional MCP tool.
Your agents read sessions the way you do: glance, then open. Any agent can read any
session, so Codex can read what Claude Code did, and the other way round.
The skill
Section titled “The skill”wisdom connect and wisdom init give each agent a skill that teaches it to run these in its
shell:
wisdom glance # recorded sessions, newest firstwisdom glance latest # one session: its shape and every turnwisdom open t3 --capture latest # turn 3, wholeRunning connect or init again updates the skill to match your Wisdom version.
wisdom doctor tells you if it’s missing or old.
What to ask
Section titled “What to ask”Ask in plain words. The agent finds the session and the turn on its own.
- Which session changed
src/totals.ts, and was that on purpose? - Read the last Wisdom session. Did the tests pass before it said they did?
- What did the Claude Code session try before it settled on this fix?
- Which session wrote the last commit, and did it do what I asked?
For the last one, the skill uses wisdom glance --commit. It also tells
your agents not to run wisdom guide unless you ask, since that calls a model on your account.
Here an agent checks a change against the request behind it:
t3 in Add a one-line docstring to main() in jev_router/tool.py.
c4 Edit src/optim_jev/tools/jev_router/tool.py · ok · → p1reply I added a one-line docstring to main().
p1 src/optim_jev/tools/jev_router/tool.py · modify · +2 −1 · observed during c4 def main() -> None: - mode = sys.argv[1] if len(sys.argv) > 1 else "" + """Dispatch a JSON request from stdin to the handler named by argv[1].""" + mode =sys.argv[1] if len(sys.argv) > 1 else ""The request and the reply both say “docstring”, but the diff shows the line below changed too. The agent sees the change, the request behind it, and where they differ.

The MCP tool (optional)
Section titled “The MCP tool (optional)”Most agents don’t need it. It’s for an agent without a shell, or if you’d rather give a tool
than a command. One read-only tool, ledger, returns the same text as the CLI. It can’t start
an agent or edit code. wisdom track already passes it to Claude Code and Codex.
To add it to another agent:
{ "mcpServers": { "wisdom": { "command": "wisdom", "args": ["mcp", "--data", "/path/to/your-project/.wisdom"] } }}{ "mcpServers": { "wisdom": { "command": "cmd", "args": ["/c", "wisdom", "mcp", "--data", "C:/path/to/your-project/.wisdom"] } }}