A team of AI Bots that work for you. Each one has a name, a job, memory, and a real computer.
Open source. Self-hosted on your VPS. Runs on the coding agent you already use.
An open-source alternative to Grok Bot. Not affiliated with xAI or X. "Grok" is a trademark of xAI.
You message Bots like teammates. They finish work end to end and only ask you when they need approval.
- A team of Bots: named teammates, each with one job, its own chat, and its own memory.
- Memory that grows: Bots save your rules and preferences as plain files. Ask "What do you remember about me?"
- Routines: run a Bot on a schedule. Bots create their own cron jobs.
- Bot to Bot: Bots ask each other for help and pass work along.
- Any agent: Claude Code, Codex, or Pi, through one small adapter each.
- Approvals (soon): Bots pause and ask before risky actions.
Also planned: computer use (Bots drive the browser and GUI apps), skills, and Slack.
- You talk to SuperBot, your main Bot.
- It hands work to focused Bots, like Developer, Researcher, or Inbox.
- Each Bot runs on the agent you picked for it.
- They all share one Linux computer on your VPS. Files and sign-ins stick around between tasks.
Every Bot gets a robot. Pick one of 12 shapes and 11 colors when you create it.
cargo build --release # makes target/release/botd and target/release/botctl
cp .env.example .env # fill it in
set -a; . ./.env; set +a
./target/release/botdThen open the web app and say hi to SuperBot. Install and log in to the agent CLIs you want (claude, codex, pi) as the same user that runs botd.
Deploying on a VPS: see Backend.
Bots run on the coding agent you choose:
- Claude Code CLI (first)
- Codex CLI
- Pi Agent
- Grok Build (planned)
- Hermes Agent (planned)
Each harness plugs in through one small adapter. Everything else stays the same.
As much as possible is Rust: the server, adapters, and CLI. That means speed, low memory use, and one small binary to self-host. Web code is used only where the browser needs it.
Our rough guess at how Grok Bot works under the hood: one shared Linux VM per account, and every Bot gets its own little world on it. Based on what a Grok Bot told us about its own VM. Not official.
Details: VM specs and running many Bots on one VM.
- Grok Bot reference: what we are rebuilding.
- Architecture: the plan and open decisions.
- Backend: how the server works, and how to run and deploy it.
Early. Chat with Bots on Claude Code, Codex, or Pi works, with memory, routines, and Bot to Bot. Approvals and computer use are next.
MIT





