CLAUDE.md alone vs CLAUDE.md plus team memory
By Soumen Sarkar · October 2026
Comparison. If your team's calls are standing rules that change every few weeks, CLAUDE.md alone is enough: keep it short and reviewed like code. If decisions arrive daily and replace each other, keep the rules in CLAUDE.md and put the decisions in shared team memory like Campfyrr, where the newest one reaches every session before it edits. Most teams of three or more need both.
What are you trying to fix?
If your problem is "every session should follow the same rules", CLAUDE.md alone fixes it. If your problem is "a call we made this morning didn't reach the session that started at eleven", the file can't fix it, and shared team memory can. Most teams have both problems, so the useful question is what goes where.
Anthropic's own advice draws the line well. CLAUDE.md is "the place you write down what you'd otherwise re-explain", and it should hold "facts Claude should hold in every session: build commands, conventions, project layout, 'always do X' rules". It is loaded at the start of every session, and Claude treats it "as context, not enforced configuration".
What belongs in the file:
- Build, test and run commands.
- Conventions that differ from tool defaults, and pitfalls with their reasons.
- How to work in this repository: where things are recorded, what never gets committed.
- Architectural choices that stand for months.
What doesn't:
- Calls that change week to week, like a product behaviour the PM settled today.
- Anything that only matters for one part of the code. The docs say to move it to a path-scoped rule or a skill.
- Old calls next to new ones. If two instructions contradict each other, "Claude may pick one arbitrarily".
- So much that the file passes the suggested 200 lines, where it consumes "more context" and can "reduce adherence".
The rest of this page is about what changes when that second list has somewhere else to live.
The same day, with each
Here's a scene, not a customer. Priya, Sam and Lee are developers on an invoicing product, with Jo as PM. The CLAUDE.md says "Store and show all times in UTC."
With CLAUDE.md alone. At ten, Priya's session settles with Jo that invoice due dates show in the customer's own time zone. Priya adds a line to CLAUDE.md on her branch. At eleven, Sam's session starts on the reminder emails from the main branch, where the file still says UTC. His emails show UTC dates. In the afternoon Priya's branch merges, and now the file holds both lines. The next session may follow either one. Lee spots the mismatch in review, and an hour goes to rework and to a conversation about which line wins.
With CLAUDE.md plus Campfyrr. The file still says "store all times in UTC", because that rule stands. At ten, Priya's session records Jo's call as a decision, with Jo's name and the reason, tied to the invoice code. At eleven, the first time Sam's session opens that code, the hook adds an area brief: the due-date decision, and Priya's work in progress there. His emails show local dates. Nobody edits the file, merges anything or relays the call by hand.
By evening, the file in both versions says the same thing. The difference is that with Campfyrr the day's decision reached Sam before he built on the old one. See what a session gets.
When CLAUDE.md alone is the better choice
- One person, or one person per repository. Nothing has to cross between people the same hour.
- Your calls are rules, not decisions. If they change every few weeks, a reviewed file is the right home, and a pull request is the right way to change it.
- You need a hard line. Neither the file nor Campfyrr blocks anything. For an action that must never happen, the docs point to a PreToolUse hook.
- You want one file every tool reads. CLAUDE.md can import an AGENTS.md so other coding agents share it.
What it costs
CLAUDE.md costs nothing. Campfyrr Team is $9 per developer a month, minimum three ($7 billed yearly), and business teammates who read and answer are free. For 5 developers and 3 business teammates, that's 5 times $9, which is $45 a month, or $35 billed yearly. Everything is free during early access (pricing).
The cost that matters more is the daily work. With the file alone, someone has to notice each call that matters, edit the file, get it merged and delete the line it replaces. With both, the file changes only when a rule does.
Here is our own repository as the record shows it. Its CLAUDE.md was written on 8 October 2026 and is 21 lines today. In those two weeks it changed six more times, and every change was about how to work: one rename from ask_team to state_assumption, then lines for publishing plans and for searching team memory before asking. None of those changes holds a product decision. Those live in the record, where one replaced another after four days without anyone touching the file (that example).
What Campfyrr doesn't do: it doesn't block a change, choose between two calls for you, or replace CI. It never stores your code (trust).
Verdict
Choose CLAUDE.md alone if you work alone, or your team's calls are standing rules that change rarely. Keep it under 200 lines and audit it.
Choose CLAUDE.md plus Campfyrr if decisions arrive daily from sessions, meetings and reviews, and a call made in one session has to reach another the same day.
Use both, always, if you add Campfyrr: it doesn't replace the file. Keep the rules in CLAUDE.md, the decisions in the record, and one line in the file saying where the decisions are. For why files grow, see why CLAUDE.md keeps growing; for the whole problem, agents breaking team decisions; for auto memory and Projects too, Claude Code memory vs team memory; and for the field, our research.
The problem this answers: Agents ignore team decisions: "Agents break team decisions, and CLAUDE.md doesn't help."
The principle behind this: Decide by doing: Our decisions live in what we do, not in what we say.
Move as one at agent speed. Nobody waits. Add Campfyrr to Claude: it briefs every agent before it touches the code, keeps assumptions and handoffs where the team can see them, and never takes your code (what it keeps).