Concepts
Privacy
Where your recordings live, what's in them, and the only ways they leave your machine.
Wisdom keeps exact recordings, which is what makes them useful, and also why they need care. This page covers where they live and how to keep them private.
Everything stays local
Section titled “Everything stays local”Recordings live in the project’s .wisdom/ folder. The background service and the dashboard
listen only on 127.0.0.1, and every request needs a token stored in .wisdom/daemon.json.
By default, nothing is uploaded and no model reads your sessions. The two exceptions below,
commit guides and team mode, are both ones you turn on.
What’s in .wisdom/
Section titled “What’s in .wisdom/”Your sessions exactly as they happened: prompts, tool output, diffs, transcripts. If a key
appeared in a command’s output, it’s in there. In a tracked project, .wisdom/ also holds each
agent’s login.
The only ways out
Section titled “The only ways out”A recording leaves your machine only when you run one of these:
| Command | Writes | Secret check |
|---|---|---|
wisdom share |
One file for a teammate, with no logins | Yes |
wisdom export |
A Markdown document | Yes |
git push, in team mode |
Sessions and commit records, to your own git remote | Yes, redacted without asking |
The check lists each value that looks like a key, token, password or email address. With
share and export you choose to redact it, keep it, or cancel; a team-mode push redacts all
of them, since nobody is there to answer. Redaction changes only what leaves, never your
recording. See Share a session.
Commit records are kept in your own .git and a normal git push never sends them, outside
team mode or in it. git push --mirror sends every ref, so it sends them too.
Commit guides
Section titled “Commit guides”A model writes a commit guide only when you ask:
wisdom guide <commit>, wisdom guide on, or team mode, where it’s on unless you run
wisdom guide off. The default writer reads the commit’s sessions through your own Claude
Code login, so that text goes to the model’s provider, as in any Claude Code session. A team
that sets its own guides.command sends it wherever that command does. The plain guide uses
no model.
Your global settings
Section titled “Your global settings”Wisdom never edits ~/.claude, ~/.codex or ~/.pi/agent. wisdom connect writes only to
the project’s own settings, kept out of git, and wisdom disconnect removes exactly that. The
one exception is yours to choose: deleting a connected session with Also delete the
harness’s own copy ticked.