With an agent
An agent connected to Kessho is an AI assistant (Claude Code, Codex, Gemini CLI… see Connect the agent) that talks to your memory through Kessho's MCP server. It reads what you have already decided, writes what the session brings, and you find it on screen: the application and the agent look at the same folder of notes (see Choosing your memory).
Why
An assistant has no memory from one session to the next, nor from one tool to another. With Kessho, what matters is written into your memory, a folder of Markdown notes that is yours: the next session, in the same assistant or another one, starts from there without you having to say it all again.
The cycle: resume, work, archive
- Resume. You say "let's pick up project X"; the agent loads that project's context. See Resume a project.
- Work. During the session, the agent can search, note a decision, tidy up. See Search the memory and Write to the memory.
- Archive. At the end of the session, the agent writes a dated archive and updates the project's context. See Archive a session.
Who does what
| What it does | Where you see it | |
|---|---|---|
| The application (Kessho) | Declares its server in your assistants, drops the procedures that tell them when to call it, displays the memory, syncs it in one click. | The screens of the application guide. |
| The agent | Calls the MCP tools (the mem_* ones): read, search, write, tidy up. Each tool is described in the MCP reference. | The freshness indicator lights up when it writes (see Zones). |
Every page of this section starts from what you say to the agent, then explains what the agent does (the tools it calls, what changes in the memory), then what the application shows.
The seven journeys
- Connect the agent: connect your assistant, and check that it sees Kessho.
- Resume a project: find where you left off, without re-explaining anything.
- Archive a session: keep a trace of a session, and undo it if needed.
- Search the memory: find a decision, a file, a note.
- Write to the memory: note a fact, a principle, a goal, a person, a document.
- Maintain the memory: check the folder's health, rename, move, remove.
- Sync the memory: keep the memory up to date across your machines, with git.
The complete list of tools, with their parameters, is in the MCP reference.
An agent does not do everything on its own
Some tools only run under a condition, which each journey recalls: a dry run before applying (apply, confirm), a justified confirmation to remove a note. These safeguards are the server's, not the agent's good manners.
Another kind of instruction is not checked by the server: for mem_git_commit and mem_git_resolve, it is the tool's description that tells the agent to obtain the user's agreement; the server does not verify it.