Do Claude Code's projects, auto memory and agent teams work across a whole team?
By Soumen Sarkar · October 2026
Short answer: Not yet: they work across one person's sessions. Projects belong to one user, auto memory stays on one machine, cross-session messaging reaches only your own sessions, and an agent team lives inside one session. A team needs a shared layer on top that every teammate's sessions read and write.
What does each feature do?
Claude Code has several ways for work to carry over, and each is good at its job:
- CLAUDE.md files hold instructions at organisation, project and personal level. The project file is shared with the team through git. Anthropic's docs describe these instructions as context, not enforced configuration.
- Auto memory lets Claude keep notes for itself between sessions. Anthropic's docs say it is machine-local and not shared across machines.
- Projects let parallel cloud threads share repositories, instructions and a memory file of requirements, decisions and pitfalls. Anthropic's docs say a project belongs to one user and can't be shared with another.
- Cross-session messaging lets Claude pass findings between your sessions, including warning one session when a change in another breaks what it's building on. It covers your own sessions.
- Agent teams let one lead session start teammates that share a task list and a mailbox. It's one team per session, run by one person.
Where do they stop?
At the edge of one person's account. Between teammates, the things that cause rework never cross over:
- Your session can't see that a colleague's session is changing the same area right now.
- A decision made in a colleague's session this morning isn't in your session's context.
- An assumption a colleague's agent made overnight can't be confirmed by the product manager who knows the answer, because nobody sees it.
None of that is a flaw in these features. They're built for one person running several sessions, and they do that well.
What does a team add on top?
A layer every teammate's sessions share, used alongside the features above:
- Area briefs across people: the first time any session touches a part of the code, it learns what everyone's sessions are changing there and what the team decided. See area brief.
- One team record of decisions and assumptions, written as sessions work and read by every later session. See team record.
- Handoffs between people, not just between one person's sessions. See handoff.
Campfyrr is that layer, as a Claude Code plugin. Keep your CLAUDE.md, auto memory and projects; Campfyrr shares what's happening across the team. More at shared team memory for Claude Code, and for how sessions share it, how do I share memory across my team's Claude Code sessions?
Words used here
- Area brief: An area brief is what a person or agent is told the first time they touch a part of the code: what's changing there now, what was decided, and what was tried.
- Team record: The team record is everything a team has written down that a person or agent can search before asking: decisions, rules, handoffs, assumptions and the reasons behind changes.
- Handoff: A handoff is what unfinished work carries for whoever continues it: what's done, what's left, the next step, and what to watch out for.
The principle behind this: Keep moving: The work never waits, and neither do we.
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).