14 November 2026 · 4 min read
Agent Zero vs deck: two self-hosted agents with a computer of their own
Two open-source alternatives to Grok Bot, and which one to pick.
IThe short answer
Pick Agent Zero if you want a general agent with a Linux desktop that you can run today. It runs in Docker, works with cloud or local models and can hand parts of a task to other agents.
Pick deck if you want several bots that must stay apart, such as an email bot and a job-hunting bot, each with its own virtual machine, logins and permissions, and with your approval before a post, payment or message goes out. deck is early. I build it, so read this page as the author's comparison.
IICompared
| Agent Zero | deck | |
|---|---|---|
| The agent's computer | A Linux workspace with an XFCE desktop, in Docker | One QEMU/KVM virtual machine per bot, with an Arch Linux desktop |
| Several agents | Delegates parts of a task to other agents; supports A2A | Several bots, each with its own accounts, files, memory and permissions |
| Models | Cloud providers, a ChatGPT sign-in or a local model server | Any OpenAI-compatible endpoint |
| Browser | A browser in the workspace | bare, a browser engine written from scratch in Rust, with no fallback |
| Owner control | You can take over the desktop with your own mouse and keyboard | Approval rules and a spending budget per bot; one inbox for approvals and failures |
| Idle cost | Not stated in the README | A bot's VM is saved to disk when idle and restored when work arrives |
| Interface | Web UI, by default on port 5080 | Web app on laptop or phone, a chat with each bot |
| License | MIT | MIT or Apache-2.0 |
| Status | Ready to install | One-bot runtime passed its tests on 12 November 2026; many features not shipped |
From the Agent Zero README and the deck project page, checked on 14 November 2026.
IIIAgent Zero
Agent Zero describes itself as an open-source AI agent with its own Linux workspace. It uses a terminal, a browser and desktop apps such as LibreOffice for research, coding and documents. You install it with its launcher, an install script or docker run agent0ai/agent-zero. Its README says to keep it inside Docker or another isolated environment.
It is the more complete tool today. Plugins add model providers and features.
IVdeck
deck is built around separation. One Rust service runs the agent loop for every bot, outside the bots' computers. Each bot gets its own virtual machine, so one bot never sees another bot's logins. A post, a payment or a sent message can wait for my approval, and each bot has a spending budget.
On 12 November 2026, the one-bot runtime passed its tests in a real VM: browser, shell and file work, an idle save and a restore for the next task. In one run, a working bot used about 531 MiB of VM memory. Bot creation through chat, real account integrations, automatic spending accounting, memory and load tests with many bots are not shipped. The source is on GitHub.
VWhich to choose
For one capable agent now, choose Agent Zero. For several long-lived bots with separate accounts and strict approval, deck is designed for that case, but expect gaps until the features above ship. For other options, including cua and OpenHands, see self-hosted alternatives to Grok Bot.
VIQuestions
What is the difference between Agent Zero and deck?
Agent Zero is a general open-source agent with one Linux workspace in Docker and support for cloud or local models. deck runs several separate bots, each in its own QEMU/KVM virtual machine, with owner approval and a budget per bot. Agent Zero is more complete today; deck is early.
Can Agent Zero run local models?
Yes. Its setup offers a cloud provider, an AI account such as a ChatGPT sign-in, or a local model server.
Is deck open source?
Yes. deck is dual-licensed under MIT and Apache-2.0, and the source is at github.com/mrwick1/deck.
Which self-hosted agent keeps bots isolated from each other?
deck gives each bot its own virtual machine, accounts, files, memory and permissions, so one bot cannot see another bot's logins.