What gets forgotten
When a session ends, the reasons go with it: what was tried, what was decided, what was left undone. Notes files help, but they sit on one machine and somebody has to keep them current. CodeKasten's Claude Code plugin keeps this in a workspace, as records your team can read and correct.
Every session starts with a briefing
The project's facts, its open gaps, the features being built, what you have told the agent about how you work, and the skills your team approved reach each new session at its start.
| What | Who sees it | Holds |
|---|---|---|
| Project profile | the workspace | The repository's stack and commands |
| Skill | the workspace | Instructions for a kind of task, reviewed through a merge |
| Fact | the workspace | A convention, a decision and why, how a thing works |
| Gap | the workspace | Something missing or wrong that nobody is fixing now |
| Memory | you alone | How you work, and what you asked the agent to do or not do |
What an agent writes is a proposal
A fact reaches every session of everybody in the workspace, so one wrong note would spread. What an agent writes to facts and gaps stays out of the briefing until a person accepts it, and an agent never accepts its own. A fact can name the files it is about: when those files change, the next briefing marks it check.
Sessions you can look back through
A session keeps what you asked, what the agent answered and did, and a summary of what came of it. Later sessions search it instead of starting from nothing, you can read any of them in the app, and a kept session can be resumed on another machine.
- A session is yours alone. Nobody else in the workspace sees it or its transcript, whatever their role.
- Secrets are redacted by the plugin before anything leaves your machine.
- You can write to a running session from the app, while it listens.
Works with what you already use
It works with Claude Code, through the plugin that ships with CodeKasten. Sessions and memory are kept by the CodeKasten app, which a workspace installs from the Marketplace. Records the agent changes go through the MCP server, on a branch of the session's own.
We use this every day to build CodeKasten: how we work with agents.