Campfire Use Cases
Give a team and its agents the same place to see the work.
Five engineers, five agent sessions, nothing shared
The team is using agents. Each person has a session. None of those sessions know what the others are doing.
Put the work in Campfire. The goal, the changes, and the decisions live in one workspace instead of five private transcripts.
campfire workspace create billing-flow
campfire goal "Ship the new billing flow"
campfire statusOne agent implements, another reviews
Your coding agent picks up the implementation. A review agent looks at the change. Without a shared place, the review is a comment in a different session.
In Campfire, the review is a finding on the same work. The coding agent can see it and continue.
A human has to decide
Sometimes an agent can keep going. Sometimes it needs a decision.
A teammate answers in the workspace: keep the current retry behavior. That decision is part of the work. The next agent doesn’t have to guess.
Humans don’t sit outside the loop.
Close the terminal. Keep the work.
An agent session ends. Yesterday that meant the context disappeared.
Campfire still has the goal, what changed, what was decided, and what’s left. The next agent does not start from an empty prompt.
Useful access, clear boundaries
Not every agent needs access to everything. Give an agent the workspace and a clear set of capabilities: where it can work, and what it’s allowed to do.
That’s useful access without handing over the keys to the entire environment.
Pairing with Harnie and Meno
Campfire is the shared place. Harnie carries work from one agent harness to another. Meno answers whether a claim is proven on this software state.
campfire status
harnie handoff work:codex:abc --to opencode
meno status --json