OpenBot is a free desktop app that runs a team of AI agents on your own computer. Rather than a single chat window, OpenBot gives you persistent AI teammates: each agent has its own name, instructions and workspace, and agents can send each other messages, hand off tasks and share files while they work. OpenBot connects to Codex, Claude Code, Gemini, Grok, OpenCode, Cursor and Cline, so you can run your agents with the ChatGPT, Claude, Gemini or Grok plan you already pay for, or with your own model. It is available for macOS, Windows and Linux.
The usual way to work with an AI assistant is one assistant, one chat, one provider. OpenBot starts from a different assumption: that the AI plans people already pay for should be able to work together as a team on the machine in front of them. OpenBot is positioned as an alternative to Grok Bot, and the site describes it as a free, local, open-source and multiplayer workspace for AI teammates. The problem it addresses is practical. Agent work is fragmented across providers and accounts, an agent loses its context when you close it or switch tools, and everything it touches tends to live on someone else's servers. OpenBot answers those points directly: agents keep their workspace and conversation when you restart the app or move an agent to a different provider, and workspaces, conversations, files and browser data stay on the computer that runs OpenBot rather than on OpenBot's servers. The source code is public on GitHub, so you can read, change and run it for any noncommercial purpose.
Agents work as a team. Each agent you create has its own name, its own instructions and its own workspace, so you can describe the agent you want in one prompt, check its instructions and save it. From there the agents act like colleagues rather than tools: they send each other messages, hand off tasks and share files. In the launch example shown on the site, an agent called Research verifies the evidence while Builder checks the rollout path and Launch owns the release, and the user asks the team to prepare the launch plan, tag Research, and keep every decision traceable. The result comes back as a written plan with a workstream table, owners and statuses, plus attached files such as launch-brief.md and launch-metrics.csv. A later message asks the team to turn this into the final launch brief, using @Research's evidence and @Builder's rollout notes and attaching the source files. Because the agents are named and addressable, you can direct work to a specific teammate instead of hoping a single assistant remembers everything. The site also shows an agent handing a task to another agent, who fixes a file, asks a third to review it, and gets the change merged and the issue closed.
OpenBot works with the AI plans you already have. Codex signs in with your ChatGPT plan and Claude Code signs in with your Claude plan; Gemini uses a Google AI Pro or Ultra plan, and OpenCode ships free models that need no account at all. Grok, Cursor and Cline are also supported providers. If none of those fit, you can connect any OpenAI-compatible endpoint, or run local models through Ollama or LM Studio. The provider is not a lock-in either: an agent keeps its workspace and conversation when you move it to a different provider, so the same teammate can start a job on one model and continue it on another. In the demo on the site, an agent called Ada begins a billing migration with Codex, which reports that six tables use the billing code and then changes four files and writes the migration, and Ada then continues the work on Claude Code to write the test for that migration.
Everything the agents produce is stored on your computer. Workspaces, conversations, files and browser data stay on the machine that runs OpenBot, not on OpenBot's servers; the only external traffic is the prompts your agents send to the AI provider you chose, and the pages an agent opens in its browser. That browser is built into OpenBot: agents can open, read and control pages inside it, which is how they can work through a sign-in screen or a dashboard without you switching windows. OpenBot also lets you queue work. If an agent is already busy, you can send more messages and they wait in a queue that you can pause, resume or cancel, so you can line up the next task without interrupting the current one. And the workspace is multiplayer: you can invite other people to your team and collaborate live with the same agents, which requires an account.
OpenBot's approach is to keep the orchestration on your desktop and to treat each model as an interchangeable worker. You download the app, connect a provider, describe the agent you want in one prompt, review its instructions and save it, then send it work immediately. Agents are described as persistent AI teammates, which means an agent is not a conversation you lose when the app restarts: its workspace and its conversation survive restarts and provider changes. Roles, rather than one-off prompts, are the organising unit. One agent can own research, another the build, another the release, and they coordinate by messaging each other and handing off tasks while you steer from the same window. Tasks given to a busy agent simply wait in the queue instead of being dropped.
Because OpenBot is free, with no hidden fees and no locked features, the only cost is the AI plan you already pay for. Because it runs locally, your workspaces, conversations, files and browser data remain on your own machine. Because agents keep their workspace and conversation, work can continue across restarts and across providers rather than starting from zero each time. Because agents have names, instructions and their own workspaces, responsibility for a task is visible and handoffs between teammates are explicit. And because the source is public under the PolyForm Noncommercial License 1.0.0, you can read, change and run the code for any noncommercial purpose, although commercial use needs a separate license. OpenBot is explicit that it is a development preview: agents can read and change files, run commands, use the network and control the built-in browser without asking each time, so it advises giving them only tasks you trust and keeping backups.
From the material on the site, OpenBot's use cases cluster around multi-step work that benefits from several specialised agents. Launch coordination is one: preparing a launch plan, tagging work, verifying claims and evidence, checking a rollout path, confirming the rollback owner and publishing a release note. Software changes are another: reading billing code, moving tables to their own schema, editing files, writing a migration and then writing the test for it, with a second agent reviewing a change before it is merged and the issue closed. Ongoing operational chores are a third: summarising the support inbox, drafting release notes and checking new sign-ups, all queued up while another agent is busy. Web-based tasks are a fourth, since an agent can drive the built-in browser through a page such as a sign-in screen or a dashboard as part of its work. And for anyone who wants to avoid hosted plans, Ollama or LM Studio plus an OpenAI-compatible endpoint covers the local-model path.
OpenBot is aimed at people who already pay for an AI plan and want more than a single chatbot: developers, small product teams and anyone coordinating multi-step work, including teams that want to share the same agents live. It runs on macOS 13 or newer on Apple silicon or Intel, Windows 10 or newer on x64, and Linux on x64 or arm64 as an AppImage. No account is needed to use the app; you only need one to invite other people to your team. Pricing is $0, with no hidden fees and no locked features, and the code is published on GitHub under the PolyForm Noncommercial License 1.0.0, which is not an OSI open-source license because commercial use requires a separate license.
OpenBot is, in short, a free and open-source desktop workspace that turns the AI plans you already pay for into a persistent team of local agents, complete with roles, handoffs, shared files, a built-in browser, a task queue and live multiplayer collaboration, all running on your own computer.