From chat to shipping, keep humans and AI agents in the same context.
Collaborative development for the AI era
From chat to shipping, keep humans and AI agents in the same context.
Turn a VM or Docker container into a shared dev station with shared shells, live previews, and chat-native workflows. Self-hosted by default.
Discuss in chat. Execute in shared context.
View on GitHub 
Shipping in a single thread
Thread Can we ship today? Login is flaky in prod @bunny launch live stream preview We should change the color and the layout Yes, I agree, and we should propose social login @bunny stop live preview @bunny fix and open PR Review looks good Validate Click me Reject PR merged to main AI agent GitHub gated push Code review in Thread - login(email, password) + loginWithOAuth(provider) return session.create(user) Can we ship this change? OAuth flow looks correct 🤖 Code review validated by AI agent Code review done live preview Sign in + 🧠 Replay
Same moment, one source of truth
Without bunny
Dev A ssh Dev B team chat deploy Terminal Cursor GitHub main? v2? two actions · one conflict
vs
With bunny
Dev A ssh Dev B team chat deploy ssh · VM bunny Term. Cursor Claude Codex GitHub Supabase ✓ synced two actions · one state
Governed gateway, shared context
Without bunny
Dev A Dev B IDE team chat Claude Cursor Codex GitHub Supabase other tools & services fix login deploy? ungoverned · context lost each tool, its own memory
vs
With bunny
Dev A ssh Dev B IDE team chat bunny ssh VM Claude Cursor Codex GitHub Supabase self-hosted tools managed services fix login deploy? @bunny do it governed gateway · shared context in memory chat ↔ bunny ↔ every tool
Earlier proposals
Current version
No shared context
team chat T Terminal Browser Codex Git separate contexts
vs
Shared context
team chat T bunny Terminal Browser Codex Git one shared context
Proposal: 2 devs and silos
Broken context
v2? Dev A main? Dev B fix login team chat T login? Terminal broken UI Browser v2 ≠ Codex to merge Git fix login fix login fix login fix login fix login fix login same topic · conflicting versions
vs
Relevant context
shared context discusses discusses commands @bunny run tests @bunny open preview @bunny commit fix ✓ fix login ✓ fix login control plane ✓ fix login ✓ fix login ✓ fix login source of truth ✓ fix login ✓ fix login ✓ fix login ✓ fix login Dev A team chat T tests failing? login broken? on it @bunny run tests Dev B bunny Terminal Browser Codex Git discuss in chat · control tools · shared context
◇
Shared remote environment
A VPS or container becomes the team's persistent workspace: terminals, live previews, streamed browsers, and a unified timeline where code, feedback, and experiments converge.
◎
Chat-native workflows
Work from a channel with the same context, the same coding agent, and distinct rights for every contributor, whether engineers, designers, operators, or non-technical members.
⟡
Open & self-hosted
Install the tools you already use (shell, CLIs, scripts, Codex, Claude) through prompts and shared workflows in an environment your team controls.
Beyond code
Versioning that captures how software is actually made
The Git commit is often the only durable artifact explaining a project's evolution. But in modern workflows, meaning lives elsewhere: chat threads, agent prompts, collective decisions, tests run, errors encountered, and trade-offs accepted.
bunny adds a semantic layer on top of code versioning, connecting each important change to the discussions, goals, and interactions that led to it.
- Chat discussions
- AI agent prompts
- Decisions & trade-offs
- Tests & regressions
- Code changes
- ✓One worktree per agent and per shell session
- ✓Shared object store with no duplicate clones
- ✓Parallel branches, integrated through your usual Git flow
- ✓Role-based access for humans and agents
- ✓Policy enforcement on every connected tool
- ✓Centralized audit trail in chat context
One collaboration graph, not just a commit log.
Why was this commit made?
Which discussion led to this implementation?
What objective did this change serve?
Which agents or contributors influenced this decision?
Parallel validation
CI feedback at the speed of vibe coding
Current workflows are poorly suited to AI-assisted development. Teams iterate faster, rely more on agents, yet CI arrives too late, takes too long, and sometimes gets bypassed entirely.
bunny integrates a validation agent that works in parallel with development: continuously testing changes, detecting regressions, analyzing errors, and suggesting fixes directly in chat.
Create Humans & coding agents ship changes
Validate Validation agent tests in parallel
Discuss Fixes & trade-offs in chat
Traditional CI Slow, disconnected, often too late
Parallel editing
True collaboration without overwrites or conflicts
On a shared VM, many contributors work at once: engineers in their shells, multiple AI agents in parallel. A single checkout would mean constant collisions, with one session stomping another's files mid-edit.
bunny provisions a git worktree for every agent and every user shell. Each session gets its own working directory and branch on the same repository, locally on the machine for isolated edits, safe parallelism, and merge when ready.
.git / objects git worktree Agent A feat/oauth Agent B fix/login Shell alice/ui Shell bob/api Parallel edits · zero overwrite
One repo. Many trees. Everyone ships in parallel.
Governance
Authorization on every action, for everyone
bunny sits between your team and every connected tool with a verification and enforcement layer. Before any teammate or AI agent runs a command, opens a PR, or touches an integration, bunny checks authorizations against your policies and RBAC rules.
The same governance applies whether the request comes from a human in chat or an autonomous agent, with no backdoors or shadow access. Policies travel with context across GitHub, shells, browsers, and every MCP-connected service.
Teammate AI agent Guest Governance RBAC + policies GitHub Shell MCP Authorization granted Policy denied, no access
One gate. Every tool. Humans and agents alike.
Collaborate around context, not just a repository
Software development as a living process where humans, AI agents, environments, discussions, tests, and decisions stay connected in one flow.