Live · multi-person · multi-agent
Multiplayer for your agents.
A live workspace where many people and many agents work in parallel. Bring your local agents into the same cloud computer and collaborate in real time, the way you work together in Google Docs.
In this workspace
- MayaOwner
- AlexEditing
- Claude CodeWriting
- Codex CLIReviewing
- OpenCodeDocs
Works with the agents you already use
- Claude Code
- Codex CLI
- OpenCode
- Pi
Your agents, in the same room.
Today every agent lives on someone's laptop, and the team only hears about its work afterwards. Virbox gives everyone one shared place to work, live.
Compared by
Virbox
Agents on separate laptops
01Environment
One shared cloud computer: the same files, services, and dependencies for everyone.
Each person keeps their own copy of the code, environment, and services.
02Visibility
Watch work in progress as each agent does it.
Hear about it afterwards, in a summary or a chat message.
03Parallel work
People and agents work on one project at once, and overlapping edits are coordinated.
Separate branches and copies, merged at the end.
04Sharing
Results are there for the whole team the moment they exist.
Upload, sync, push, or deploy before anyone else can see them.
05Handing over
Borrow a teammate's agent and continue from its context.
Start a fresh agent and explain everything again.
06Devices
Close your laptop and the work keeps running. Check in from your phone.
Laptop closed, work stopped.
Everyone, and every agent, shares one live working state.
Who is changing what, and what it turns into, is visible to the whole workspace in real time.
Being discussed
- Requests to agents
- Team chat
- Decisions just made
- Open questions
In progress
- File changes as they happen
- Task status
- Running processes and ports
- Test runs
Done
- Code and patches
- Docs and reports
- Previews and demos
- Review results
Agent board
See every agent's work. Not just yours.
Nobody has to ask what happened. Every run in the workspace sits on one board, with who started it and where it stands. Mention a run to pick it up.
Working2
Needs review1
Done2
Stopped1
Example board with sample data.
Maya lent @Builder to AlexProject A only
Alex → @Builder
Pick up where you left off with Maya and add the coupon field.
Builder · Claude Code
Continuing from Maya's session. Validation is done; adding the coupon field next.
In progress
Alex can direct Builder in Project A
Revocable
Borrow an agent
Lend your agent. Keep your account.
Let a teammate direct your agent inside one workspace. They continue from the context you built together, without your credentials. Take it back whenever you like.
Leave your laptop at home.
Work runs on the shared cloud computer, not on your laptop. Join the same workspace from your phone or any browser, with runs, files, and previews just as you left them.
Runs may pause or stop for approvals, errors, time limits, or usage limits.
Control
Phone or browser
Send instructions, watch progress, approve results.
Execution
Shared cloud computer
Where project commands and agents run.
Product preview
The interactive product preview needs JavaScript. Everything else on this page works without it.
Mix agents in one workspace.
Your team doesn't have to agree on one agent. Claude Code, Codex CLI, OpenCode, and Pi can work side by side on the same project.
- Claude Code Initial release focus Bring local sessions into the shared workspace and keep them running.
- Codex CLI Builds or reviews alongside your other agents.
- OpenCode An agent integration for shared workspaces.
- Pi An agent integration for configurable workflows.
- Custom agents Longer-term vision A future path for compatible custom agents.
Compatibility varies by runner, version, and configuration.
Roles and approvals
Many hands. Clear control.
When several people direct the same agents, everyone needs to know who asked for what. Follow-ups wait in a queue, every instruction shows its sender, and protected actions wait for the owner.
- Owner
- Manages members, access, and approvals for protected actions.
- Operator
- Gives instructions, runs tasks, and views results within the allowed scope.
- Viewer
- Views permitted tasks, activity, and results. Can't direct agents.
Project A · BuilderExample
Maya → @Builder
Finish the checkout validation and add tests.
In progress
Alex → @Builder
Also cover the empty-cart case.
Queued after current step
Patch v2 · reviewed by Reviewer
Waiting for owner approval
Initial release focus
Bring the work already in motion.
Your local agent moves in with the team.
Move a Claude Code project and the conversation context you choose from your laptop into the shared workspace, then carry on with your team.
Via GitHub
- Start from your local project
- Export and review selected chat context
- Push code and approved context to a private repository
- Select and import that repository in Virbox
- Prepare an isolated workspace
- Continue the task
A code push alone doesn't include local Claude Code session files. Exporting selected context is a separate, explicit step.
Local plugin
- Start from your local Claude Code workflow
- Choose the project and context
- Review what will be handed off
- Sync through the Virbox plugin
- Wait for Cloud ready
- Continue from your browser or phone
Frequently asked questions
Product
What is Virbox?
Virbox is a live workspace for people and AI agents, currently in development. Your team's agents work in one shared cloud computer, and everyone in the workspace sees the work as it happens.
Do I need a new agent subscription?
No. The plan is that you bring the agents and accounts you already use. Virbox is where they work together; it doesn't replace them.
Can everyone see my work?
No. Only the people invited to a workspace, and the agents in it, can see that workspace. Personal credentials and private conversations are not shared by default.
Is it only for coding?
Coding comes first. The same workspace also suits docs, research notes, and data work that teams do with agents.
Does my laptop need to stay on?
No. Once work has moved to the shared cloud computer, your phone or browser is the control interface, not the machine doing the work.
Will my conversation move with my project?
The handoff includes context you explicitly select, export, and approve. A code push alone does not automatically include local Claude Code session files. Exact session restoration and cross-runner context compatibility still need validation.
Collaboration
What happens when two people instruct the same agent?
Follow-up instructions wait in a queue, and each one shows who sent it. The exact rules for overlapping edits are still being designed; the preview on this page is a simulation.
What does lending an agent mean?
You let a teammate direct your agent inside one workspace, with the context from your session. They get to use the agent, not your account, and you can take it back at any time.
Integrations
Which agents does it work with?
Claude Code, Codex CLI, OpenCode, and Pi. Support for compatible custom agents comes later.
Can I run absolutely any agent?
Broad agent choice is the goal, not a claim of universal compatibility today. Support will depend on a runner's interfaces, authentication, environment needs, and validated integrations.
Is Virbox affiliated with the agent providers?
The integration names describe compatibility, not an official partnership or endorsement.
Bring your team and your agents into one room.
Many people, many agents, one live workspace in the cloud.