Should our team share Claude Code sessions, or share what the sessions know?
By Soumen Sarkar · October 2026
Short answer: Share what the sessions know. A shared session is a record someone opens after the work is done; shared memory reaches the next session while it works, without anyone sharing anything. Session-sharing tools such as Lore and Claude Code's own share links do the first; Campfyrr does the second.
What does sharing a session give you?
A shared session is the whole conversation, turned into a page someone can open: the prompts, the replies, the tool calls, the diffs. It's useful when you want to show exactly how something was done, or to ask a colleague to look over a session.
Several tools do it. Claude Code can share its cloud sessions as a link. Lore (lore.link) uploads a Claude Code, Codex or Amp session when you run its share command, and lets someone fork it. Others export a session to a page.
Three things are true of all of them:
- Someone has to share. The person who did the work runs a command and sends the link.
- Someone has to read it. The next person, or their agent, has to open the link and find the part that matters.
- The whole session goes along, including code and output, so it's worth checking what you're sending.
What does sharing what sessions know give you?
The next session gets the part that matters, at the moment it matters, without anyone sending anything:
- the first time it opens a part of the code, what other sessions are changing there and what the team decided (area brief);
- when a session stops, what's done and what's next (handoff);
- with each change, what it was for and what was assumed (reasons).
None of that needs a transcript. Campfyrr keeps the decisions, assumptions and handoffs, never the code or the conversation.
Which does a team need?
Mostly the second, sometimes the first. If two developers run several sessions each on one codebase, the problem isn't showing a session afterwards; it's that sessions don't know about each other while they work. Share a session when you want someone to see how something was done. Share what sessions know so nobody has to.
For the full set-up, see shared team memory for Claude Code and 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.
- 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.
- Reasons: Reasons are what a change is for, the calls made in it, and what was assumed, attached to the change for whoever reviews it.
The principle behind this: Let the work speak: Our work explains itself, so nobody ever has to come and ask us.
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).