Campfire is a shared workspace for humans and AI agents. Give them a goal, the context they need, and the tools they’re allowed to use. Campfire keeps the work, decisions, and results in one place.
curl -fsSL https://boringinfra.company/campfire/install.sh | shcargo install --git https://github.com/BoringInfraCo/Campfire campfireYou start with a goal. Your coding agent picks up the implementation. Another agent reviews the change. A teammate makes a decision that changes the plan.
Campfire gives all of them the same place to see the work and leave behind what the next person — or agent — needs.
Goal Ship the new billing flow Alex Created the workspace and added the requirements. Codex Implemented the checkout changes. → 4 files changed → tests passing Review Agent Found an edge case with expired cards. → added finding Alex Keep the current retry behavior. → decision recorded Codex Picked up the decision and continued. Nobody has to reconstruct what happened from three different agent sessions.
Sergio → Agent A → session Carolina → Agent B → session Engineer → Agent C → session nothing shared Five engineers using agents. None of these things know what the others are doing.
without campfire agent session 1 gone agent session 2 gone a decision in chat somewhere else with campfire goal Ship the new billing flow change checkout, 4 files finding expired cards decision keep current retry Close the terminal. Keep the work.
campfirebilling-flowAlex·Codex·Reviewaround the fire
Campfirethe workspacein the workspace
Everyone can see it. Everyone can leave something.
The shared place where the team and its agents work.
# what you get
Agents are good at doing work. The problem starts when more than one person or agent is involved. One agent knows what it changed. Another knows what it found. A teammate made a decision in a different session. Campfire gives that work a shared home.
How a workspace works →Sergio → Agent A → session Carolina → Agent B → session Engineer → Agent C → session nothing shared The work lives in three sessions. Nobody else can see it.
Campfire doesn’t replace Codex, Claude Code, OpenCode, or your own agents. Keep using the tools you like. Campfire sits between the people and agents doing the work so they can share goals, context, decisions, and results. Your agents stay your agents.
What Campfire is not →Codex still Codex Claude Code still Claude Code OpenCode still OpenCode your agent still yours Campfire sits between them. goals · context · decisions · results
Campfire doesn’t orchestrate your agents. It gives them someplace to gather.
An agent session ends. The work shouldn’t disappear with it. Campfire keeps track of what the team was trying to do, what happened, what was decided, and what’s left. The next agent doesn’t have to start from an empty prompt. Close the terminal. Keep the work.
When a session ends →$ exit session ended. goal still here decision still here what’s left still here the next agent does not start empty.
Not every agent needs access to everything. Campfire gives agents a workspace and a clear set of capabilities. You decide where they can work and what they’re allowed to do. That makes it easier to give agents useful access without handing them the keys to the entire environment. Useful access. Clear boundaries.
Capabilities →workspace billing-flow allowed read requirements edit checkout/ run tests denied prod credentials the rest of the repo useful access. clear boundaries.
Humans don’t sit outside the loop.
Campfire keeps the important parts of the work together: who did something, which agent session it came from, what changed, and what decisions shaped the result. When something looks wrong, you don’t have to guess which agent did what. The work has a history.
How work is recorded →Alex created the goal Codex 4 files changed Review Agent expired-card finding Alex decision: keep retry Codex continued from that when something looks wrong, you don’t guess which agent did what.
You shouldn’t have to design a multi-agent system just to get two agents working on the same problem. Create a workspace. Add the people and agents involved. Give them a goal. Campfire handles the shared state underneath.
Start with a goal →1. create a workspace 2. add the people and agents 3. give them a goal Campfire handles the shared state. no orchestration graph required.