Your own team of
always-on agents.
Give durable AI coworkers real computers, shared files, and time to finish the work. OpenBot keeps running on your infrastructure—even after you close the app.
Not another chat window.
Agents that have a place to work.
And remember where they left off.
Give agents more than
a message box.
OpenBot is a home for work that spans tools, files, agents, and time. Every capability below runs in the project today.
A real computer for every Bot.
Each agent gets its own persistent Linux display with Chrome, files, and a terminal. Watch live or take control from desktop or iPhone.
atlas@openbot:/workspace$ ls
research launch-brief.pdf sources.csv
atlas@openbot:/workspace$
Context that survives the restart.
Sessions, memory, identity, chats, and files are durable. Pick up the same work tomorrow—or after a server restart.
One task. A whole agent team.
Bring Bots into a room, let them message one another, or have a lead spin up private subagents for parallel work.
Put the repeatable work on a schedule.
Durable routines wake the right Bot on time, run through the same long-lived context, and keep an execution history you can inspect.
14 sources reviewed · 3 changes worth watching · report saved to /workspace/briefs.
Leave the desk. Stay in the loop.
Chat, search, reply, watch progress, approve actions, and take over a Bot’s computer from the iPhone app.
Watch live, or take control when your agent needs help.
Teach it your tools and your way of working.
Install MCP plugins, save reusable skills, and keep editable project and user memory on the machine you control.
Your agents.
Your computer.
Your rules.
OpenBot runs as a private Docker Compose stack with persistent volumes for every session, file, screen, and message. The desktop app holds no model credentials. Your Codex sign-in stays inside the computer service you run.
- ✓Everything survives restartsPostgres, sessions, memory, browser profiles, and shared files form one durable recovery set.
- ✓Private network friendlyCore services and agent screens stay on loopback by default, with explicit setup for a trusted private network.
- ✓Inspect it, change it, own itThe app, agent state, and deployment configuration live in code and ordinary files.
Give it the work you
keep putting off.
Deep research
Hand a Bot a folder and a question. It can browse, compare sources, write the report, and leave every artifact in your workspace.
Operations on repeat
Turn a recurring brief, follow-up, or audit into a durable routine that runs whether or not your laptop is open.
Parallel projects
Ask one lead Bot to split a complex goal across specialists, then come back to one coordinated result and the full trail behind it.
Questions,
answered.
OpenBot is young, opinionated, and meant to be run by people who want to own their agent stack.
What makes a Bot durable?+
Every Bot has a persistent Pi session, editable memory and identity files, durable chat history, and its own Linux display. Restarts do not turn it back into a blank chat.
Does OpenBot keep working when I close the desktop app?+
Yes. The server, worker, agent sessions, schedules, and computer live in the self-hosted stack. The desktop and iPhone apps are clients you can leave and return to.
Can I see and control what an agent is doing?+
Yes. Open any Bot’s live Linux screen, watch its browser, files, or terminal, and take over directly when a sign-in or judgment call needs you.
Which model does it use?+
OpenBot is built around the Pi agent runtime and OpenAI Codex authentication. Your model credential stays inside your private computer service rather than in the desktop client.
Put your agents
to work.
Docker is the only system prerequisite. One command installs the server, worker, database, migrations, and shared graphical computer.
bunx --bun @openbot/cli install⌘C