For teams of 3–20 developers on Claude Code
Shared team memory for Claude Code
Every teammate's Claude Code sessions know what the others are changing, what was decided and what was assumed, before they touch the code. The rest of your company follows the work from a link. One plugin, one token, and your code never leaves your machine.
Free during early access. Then free for one person, $9 per developer a month for teams.
What it fixes
“My teammates' Claude Code sessions don't know what each other are doing.”
The first time a session reads or edits a part of the code, it's told what's changing there right now (with the plan), the decisions that apply, and what was tried and dropped.
How it works“Agents keep breaking team decisions, and CLAUDE.md doesn't help.”
Decisions are recorded as they're made, with their reasons, and given to every session that touches that area. The newest call stands, and clashing decisions are caught the moment they happen.
How it works“I'm the human router. Sessions stop to ask, and the questions wait for me.”
Sessions state their assumptions and keep going. Each assumption goes to whoever should confirm it, high-stakes ones first, and the answer reaches the agent at its next turn.
How it works“Review is the bottleneck. I can't tell why an agent did that.”
Every change gets its reasons, written as the agent works: what it's for, what was decided, what was assumed. The link goes in the pull request.
How it works“Half-finished work loses its context when it changes hands.”
When a session stops, a handoff is written from it: what's done, what's left, the next step and what to watch out for.
How it works“The rest of the company finds out what we built last.”
Founders, product, sales and support follow the work from a link, in plain words, and answer the questions that are theirs. They're free.
How it worksSet up in two minutes
- Sign in and create a token, then paste the two install lines into a terminal.
- Start a Claude Code session. It opens with your team's brief.
- Invite one teammate. From then on, each of your sessions knows what the other's are doing.
Running Claude Code in the cloud? /connect has the steps for that too. It also works with Claude, Codex and any MCP client.
Questions
How is this different from CLAUDE.md?
CLAUDE.md is the same file for every session and changes when someone edits it. Campfyrr is live: what teammates are changing right now, decided this morning, or assumed last night, given to the session working in that part of the code.
Doesn't Claude Code already share memory?
Claude Code's projects, auto memory and cross-session messaging work across one person's sessions. Campfyrr shares across everyone on the team, and with the people around them.
Do git worktrees solve this?
Worktrees keep sessions out of each other's files. They don't tell one session what another is about to change or what the team decided. Use both.
Does it store our code?
No. Hooks send file paths and what happened in the session, never file contents or diffs. /trust says exactly what's kept.