Campfyrr vs Lore: show one agent run, or keep every session in step
By Soumen Sarkar · October 2026
Comparison. If you want to show a teammate exactly how one agent run went, use Lore. If your team's sessions keep building on decisions that changed this morning, use Campfyrr. Many teams have both problems.
What are you trying to fix?
If you want to show someone exactly how one agent run went, use Lore. If your team's sessions keep building on decisions that changed this morning, use Campfyrr. Many teams have both problems.
- "I want my teammate to see exactly what my agent did." Lore. One command turns a session into a page people can read, comment on and fork (Lore plugin).
- "My agent just undid something another session decided this morning." Campfyrr. The decision reaches the next session before it edits that code, and nobody has to send it.
- "I'm picking up half-finished work and don't know what was tried." Both help. Lore forks the one thread you're pointed at. Campfyrr writes a handoff when the session stops, and adds what every other session knows about that part of the code.
The same day, with each
This is a scene, not a customer: three developers and a PM on a normal Tuesday.
In the morning, Priya's agent works on refunds. She and the agent decide refunds go back to the original card, never as store credit. The agent also assumes partial refunds are out of scope. After lunch, Sam's agent starts on the checkout screen, which shows the refund options.
With Lore, Priya's decision lives in her session. If she runs /lore:share and posts the link, Sam can read it, and his agent can fork it with a clear goal. That works well when Sam knows to look. On this Tuesday he doesn't: he's on a different ticket, and the link sits in a channel. His agent offers store credit at checkout. The PM spots it in review on Thursday, and Sam spends an afternoon taking it back out. Nobody read the partial-refund assumption, so the PM learns about it from a customer.
With Campfyrr, nobody shares anything. When Sam's agent first opens the refund code, a hook gives it an area brief: Priya's decision with her reason, her work in progress, and the open assumption. It doesn't offer store credit. The assumption reached the PM as a link that morning. She corrected it in a line, and the answer reached Priya's agent at its next turn.
At the end of the day, the Lore team has a good page showing how Priya's run went. The Campfyrr team has no replay of that run. But Sam's afternoon wasn't wasted, and the PM wasn't surprised.
When Lore is the better choice
- You want to show a whole run. Teaching a new hire, asking a colleague to check a tricky session, keeping a prompt that worked. Campfyrr doesn't show a whole session as a transcript.
- You want a shared skills library. Lore versions skills and shares them across the team (lore.link). Campfyrr doesn't manage skills.
- You want to talk about the session itself. Teammates comment on blocks of a thread.
- One or two people touch the code at a time. If sessions rarely overlap, sharing a link when a run is worth it may be all you need.
Check two things before you choose it. Lore's local server ships for Apple Silicon Macs only, so teammates on Linux or Intel Macs can't run it yet. And a shared thread is the full transcript, code and tool output included, uploaded with no scrubbing on your machine first; whether the server scrubs secrets is unknown. We found both by reading the plugin's source (research). If your code has to stay off third-party servers, that decides it: Campfyrr never takes your code or diffs (/trust).
What it costs
Lore's Team plan is $20 per seat a month, minimum 2 seats, and each seat includes $20 of pooled AI credits. We read that in the plan settings inside its plugin, not on a pricing page, so check lore.link before you buy. For 5 developers, five seats at twenty dollars is $100 a month. We don't know whether the 3 business teammates need seats; if they do, eight seats come to $160.
Campfyrr is $9 per developer a month, minimum 3 developers, or $7 billed yearly. Business teammates who read and answer are free (/pricing). For 5 developers and 3 business teammates, five times nine is $45 a month, or $35 billed yearly. Everything is free during early access.
The cost that matters more is the daily habit. Lore works when the person who did the work remembers to share, and the next person knows which link to open. Campfyrr asks each developer to install the plugin once. After that, the only daily job is answering an assumption when one is sent to you.
Verdict
Choose Lore if you want to show, review or teach from a whole agent run, or you want a shared skills library, and your team is on Apple Silicon Macs.
Choose Campfyrr if several people run sessions on one codebase and keep tripping over each other's decisions (sessions don't know about each other), or half-done work loses its context when it changes hands (handoffs lose context). See what a session gets.
Use both if you want the replay of a good run and sessions that stay in step while they work. The general version of this choice is sharing a session link vs sharing what sessions know.
The problem this answers: Sessions don't know about each other: "My teammates' Claude Code sessions don't know what each other are doing."
The principle behind this: Build on what's coming: Unfinished work is a promise, and a promise can be built on.
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).