Shared memory for AI coding agents in a team
One developer fixes the Docker timeout on Monday. A teammate's agent runs into the same wall on Thursday, because the first agent's session ended and nothing carried over.
How do you share memory between AI coding agents in a team?
Give the team one place that all agents read from and write to. With cachly that place is a Brain (a store of lessons on a server in Germany). Each lesson is a short record of a fix, a decision or a dead end. Agents store lessons after a fix, and they look them up before a task.
Sharing then needs no meeting and no wiki page. The Brain is the shared state, and each agent asks it.
What exactly is shared?
- Lessons: topic, what worked, what failed, context, files and commands. Each one carries the name of whoever learned it, and
team_recallshows who knows what. - Confirmations: a reviewer can confirm a lesson with
team_confirm. Confirmed lessons rank higher in recall and carry a badge. - Not shared: your source code. It reaches the Brain only if someone runs
index_project, and then as a short excerpt per file. - Not shared: your editor setup. Rule files such as
CLAUDE.mdtravel through git, like any other file.
How does a team set it up?
- Create an organization in the dashboard under Team. An organization itself costs nothing.
- Invite teammates by email. Open the Brains page and press Share on a Brain, or run
npx @cachly-dev/mcp-server@latest invite [email protected]in the project. If the Brain has no organization yet, cachly creates one for it. Org admins can also invite from the Team page and pick the role, admin or member. Members can read and teach the Brain. Deleting it, billing and inviting more people stay with the owner or an org admin. - Teammates accept and connect. The invitation email holds a link and the command
npx @cachly-dev/mcp-server@latest join <token>. The command accepts the invitation and writes the Brain's instance ID into the configs it finds for Claude Code, Cursor, Windsurf and VS Code. If someone accepts in the browser instead, the page showsnpx @cachly-dev/mcp-server@latest join --brain <id>for each Brain. The Brain also appears under “Shared with you” on their Brains page. The invitation works for 7 days. - Let agents write with a name.
team_learnstores a lesson with its author.team_recalllists the lessons and who learned them.
Per-editor steps are in the setup guide. The same Brain across several tools is the topic of one memory for Claude Code, Cursor and Copilot.
Who may write, review and read?
A shared Brain knows four roles. They are enforced once an admin has been assigned. Before that, the team is open and every tool works for everyone.
- admin
- Assigns roles, deletes lessons, and can do everything a reviewer or contributor can.
- reviewer
- Confirms lessons with senior weight, and can do everything a contributor can.
- contributor
- Stores lessons, confirms them with peer weight, and recalls.
- viewer
- Recalls only. Cannot store or review lessons.
team_assign_role sets a role, team_whoami shows yours, team_roster lists the team, and team_audit shows an admin the trail of role changes and confirmations.
Can a team review lessons before they go live?
Yes. An org owner or admin can switch on lesson review for the organization. New team lessons then land as pending proposals. They do not appear in smart_recall or team_recall until an owner or admin approves them in the dashboard, under Team, Review. Without the switch, lessons are written directly.
What stays private?
- Private lessons. A lesson stored with visibility
privateis returned only through an exactrecall_best_solutioncall, not through broad search. - Groups. A lesson stored with a
group, such as backend or security, surfaces only for members of that group and for admins.team_grant_scopeadds or removes members. - Where data lives. What leaves each machine and where it lands is listed in GDPR and EU-hosted AI memory.
What does a team plan cost?
Team costs €49 a month for up to 5 people. Business costs €199 a month for up to 20 people and includes SSO. Free and Solo are for one person. Current prices are on the pricing page. To try the team flow, start with the free sign-up.
Frequently asked questions
Do all team members need the same editor?
No. Each person connects Claude Code, Cursor, Windsurf, VS Code with Copilot or another MCP client to the same Brain. The lessons live in the Brain, not in the editor.
Can a teammate see my private lessons?
Not if you store the lesson with visibility private. It then comes back only through an exact recall_best_solution call. A lesson stored with a group is visible to that group and to admins only.
Does the team Brain contain our source code?
No. A lesson holds a topic, what worked, what failed, context, files and commands. Source code is stored only if someone calls index_project, and then as a short excerpt per file.
Can we check lessons before the team sees them?
Yes. An org owner or admin can turn on review. New team lessons then wait as proposals, and they do not appear in recall until an owner or admin approves them in the dashboard under Team, Review.
Sources
Every statement above comes from the code of the cachly API and the open-source MCP server:
- cachly-mcp README (team tools, roles, what a Brain stores)
- cachly for teams (the product page)
Checked against the code on .
More: Team Brain: shared AI memory · Agent keeps making the same mistake · All docs