Open source · A multiplayer fork of T3 Code
T3 Code, now multiplayer.
Campfire is a thin fork for small teams that fully trust each other. See every run in one sidebar, bring a teammate into the exact thread, and steer the same agent together — without moving the work back into Slack.
The opposite of agent Slack
Bring your team to the work. Not the work back to chat.
Most multiplayer agent tools start from chat and add agents. Campfire starts from T3 Code’s purpose-built workspace and adds teammates. The run, its controls, and the human judgment around it stay together.
The team layer
Everything your team needs around the same run.
- Every run, one sidebar
- See every agent thread your teammates start, who owns it, and what needs attention. Join the same work instead of opening another silo.
- Bring in the right teammate
- Use Take a Look on the agent answer that needs judgment. Your teammate lands in the exact thread and can continue with the same agent.
- Keep team context beside the run
- Keep questions, links, and corrections in a durable team discussion attached to the agent thread that produced them.
- Catch up without adding noise
- Ask a temporary, read-only assistant to brief you on a thread. Its answers stay private to you and out of the shared conversation.
- Start reviews from the PR
- Use Review beside a pull request link to start a dedicated review thread, with its own icon and status in the sidebar.
- Steer the same run together
- See who is already in a thread, then send, interrupt, redirect, resume, or archive the same long-running agent work together.
A fork, on purpose
Staying close to upstream does not mean staying frozen. T3 Code can remain focused while Campfire ships opinionated workflows for teams who live in it all day. The code is open: add what your team needs, keep it local, or upstream the parts that generalize.
The providers — Codex, Claude Code, Cursor, Grok Build, and OpenCode — plus remote sessions, worktrees, and the web, desktop, and early mobile clients all come from T3 Code.
Source first
Run Campfire from source.
There is no packaged release yet. You need Node.js 24.13.1 or newer within major 24 and at least one T3 Code provider installed and authenticated.
git clone https://github.com/astraly-labs/campfire.git
cd campfire
corepack enable
corepack pnpm install --frozen-lockfile
corepack pnpm devOpen the pairing URL printed by the server. Local development state stays in .t3.
Read this before deploying
Campfire has no permissions model. That’s the trade we made.
There is no RBAC, tenant isolation, or per-user workspace permission. Anyone admitted to an instance can see and act on every shared agent thread and every project the Campfire service can reach.
The reference deployment binds Campfire to localhost, exposes it only through Tailscale Serve, and admits Google OIDC users whose verified email is on an explicit allowlist. Campfire records who did what, but does not authorize teammates differently. Authentication is not isolation.
Google is the current identity integration, not a requirement of the trust model. Another authentication provider can enforce the same identity boundary and allowlist before a request reaches Campfire.
Run it on a dedicated host behind a network boundary you control, use an explicit identity allowlist, and invite only people you would already trust with repository access. If you need isolation between users or teams, Campfire is the wrong tool.
Read the security model →Roadmap
Make shared agent work safer, richer, and more remote.
Directions, not dates. We want to stay close to upstream and ship each layer only when its security boundary is clear.
- Remote browser
- Attach a live browser surface to an agent task so teammates can inspect, hand off, and control the same session remotely.
- Scoped permissions
- Move beyond the all-trusted-team model with explicit scopes for projects, threads, actions, and agent capabilities.
- Stronger isolation
- Isolate agent execution and workspaces so one task does not automatically inherit everything available to the host.
- Secrets at the boundary ↗
- Explore iron-proxy for default-deny egress and per-request credential injection, keeping real secrets outside the agent workload.
- Open to suggestions ↗
- This roadmap follows how small teams actually use Campfire. Propose the workflow, boundary, or integration you need.
Upstream
T3 Code did the hard part.
Campfire exists because T3 Code built an excellent open-source foundation for driving Codex, Claude Code, Cursor, Grok Build, and OpenCode from web, desktop, and mobile clients. The architecture, provider integrations, remote workflow, worktree handling, and substantial portions of this repository are the work of Julius Marminge, Theo Browne, the T3 Code maintainers, and upstream contributors.
Our strategy is minimal divergence. We rebase onto upstream regularly, avoid renames and rewrites that create conflicts for no user-visible gain, contribute broadly useful fixes upstream when practical, and keep Campfire-only behavior at narrow boundaries.
Campfire is independently maintained and is not affiliated with, sponsored by, or endorsed by T3 Tools Inc. T3 Code and related names and marks belong to their respective owners.