Skip to content

Guides

Keep it healthy

Check, repair, run the background service, and clean up old sessions.

Wisdom mostly runs on its own. When a session isn’t recorded, or after you move Wisdom or change Node versions, start here.

Terminal
wisdom doctor

Checks the background service, the dashboard, each agent’s hooks and version, Codex hook trust, and events waiting to be recorded. It changes nothing and prints the fix for each problem.

Level Meaning
ok Working.
note Worth knowing: the service is stopped (it starts by itself), or an agent is newer than the last tested version.
problem Recording or reading is affected until you run the fix.

The same checks run at the top of every dashboard page.

Hooks store the full path of the installed Wisdom. They break when that path changes: you moved the install, or switched Node versions with nvm. Your agent keeps working either way; only live recording stops.

Terminal
wisdom connect # a connected project
wisdom init # a tracked project

Both are safe to run again. In the dashboard, Repair… does the same and backs up every file it changes first, so you can restore it. Codex asks you to approve changed hooks again in /hooks.

It starts by itself when a hook or command needs it, and keeps running after your agent exits.

Terminal
wisdom daemon status
wisdom daemon stop # the next hook starts it again
wisdom daemon start

It listens on 127.0.0.1:7434, and the dashboard on the next port. If another project already uses them, it takes the next free pair. Each project has its own service.

The dashboard’s overview shows how much space each session takes. Clean up… lists sessions not active for 30 days (change the number), and each session page has Delete.

Nothing is deleted until you’ve read what goes and confirmed: the session’s record, its evidence, and its files in the project’s agent home. For a connected session, a checkbox (off by default) also deletes the agent’s own copy in your home folder; then the agent can no longer resume it.

Each commit’s record and guide are made by a background job after the commit. It writes one line to .wisdom/jobs.log when it ends:

.wisdom/jobs.log
2026-11-11T09:41:02.118Z a4c91e2b7f30 job · record kept · guide by claude-haiku-5-5 via Claude Code, reading the sessions' windows, check passed, writer 38.4 s, $0.0031 · 40 s

A job that died is started again, up to three times; after that your next git push or wisdom guide <commit> finishes it. When that’s more than two minutes after the commit, the record says record kept later.

You see What to do
guide · none: no guide writer: Claude Code is not installed and wisdom-team.json names no guides.command Install and log in to Claude Code, or use wisdom guide off for the plain guide.
guide · none: the guide writer failed: … The writer’s own error follows. wisdom guide <commit> tries again.
No guide written: the guide must read session …, which is no longer recorded here That session was deleted, so a model guide can’t be written. Outside team mode, glance --commit still shows the plain guide.

Stop the service first (wisdom daemon stop), then move or copy the whole folder. Recording carries on in the new place. For a backup, copy all of .wisdom/, and treat the copy like a password: it holds your sessions unredacted, and in a tracked project, your agents’ logins.