Trust: what Campfyrr keeps, and what it never takes
By Soumen Sarkar · October 2026
Campfyrr carries the context of your team's work, not the work itself. It keeps what people and agents need to build on each other: what's changing, what was decided and assumed, and what's left. Your code stays where it is.
What Campfyrr keeps
- The pages your team writes: decisions, rules, work logs, handoffs and notes, each with its full history.
- What your agents report as they work: the area of the code they touched (by file path), what the work is for, the assumptions they stated, and the handoff when they stop.
- A one-line goal written from the first request of each session, so work in progress can say what it's for. The request itself isn't kept.
- Who did what, and when, for every change to shared pages: the team's record of events.
What it never takes
- Your code. The hooks send file paths and what happened in the session, never the contents of your files or your diffs.
- Your session transcript. The end of a session is read once to write the handoff, and only the handoff is kept.
- Your access tokens, in readable form. Only a fingerprint of each token is stored (tokens from before that change are converted the first time they're used), so a copy of the database can't be used to sign in.
Who sees what
- Your team sees the team's pages, work in progress, assumptions and handoffs. Nobody outside your team sees any of it.
- A private page is seen by its owner and nobody else: never on Activity, in briefs, in search or in anyone's agent.
- A page is open to people outside the team only when someone on the team chooses to share it by link or publish it.
- Without a team, everything you write is yours alone.
How it uses AI
- A hosted language model (on Groq) writes the plain-words parts: handoffs, daily updates, the story of the project, and whether the record already settles an assumption.
- Secrets such as keys, tokens and passwords are taken out of everything before the model sees it, and out of work logs before they're saved.
- Nothing waits on the model. If it's unavailable, the work carries on and the plain-words parts are simpler.
Nothing is lost, and nothing is hidden
- Inside a team there are no gates: anyone can edit, move or restore what they can see. Instead, every change is recorded, so you can always see who changed what.
- Deleting moves a page to the trash, where it can be restored with its history.
- Every earlier version of a page is kept and can be brought back.
Where it runs
- The site runs on Vercel, the data lives in a Postgres database on Neon, and sign-in is handled by Clerk.
- Slack receives updates only when your team connects a channel, and only for the project it was connected to.
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).