OpenBot

OpenBot is a free desktop application that runs AI agents as a team on your own computer. Instead of a single chat window, OpenBot gives you persistent AI teammates: each agent has its own name, its own instructions and its own workspace, and agents can message each other, hand off tasks and share files. OpenBot is built for people who already pay for an AI plan and want to turn it into a working team rather than a single assistant. It connects to Codex, Claude Code, Gemini, Grok, OpenCode, Cursor and Cline, to any OpenAI-compatible endpoint, or to local models running in Ollama or LM Studio. Most people who use AI every day are juggling several assistants at once. They may have a ChatGPT plan for one job, a Claude plan for another, and a Gemini or Grok subscription for something else, but each of those assistants works alone, in its own silo, and none of them can hand work to the others. OpenBot brings those providers into a single workspace where agents are given clear roles and can delegate to one another. Because the app runs on your own computer, workspaces, conversations, files and browser data stay on the machine that runs OpenBot rather than on a vendor's servers, and you keep paying only for the AI provider plan or API key you already have. It is also open source, so the code can be read, changed and run for noncommercial purposes. The core of OpenBot is the idea that agents work as a team. Each agent has its own name, its own instructions and its own workspace, so a Research agent and a Builder agent can hold different briefs and different context. Agents send each other messages, hand off tasks and share files. In the product's own walkthrough, a planner asks Research to verify the evidence and Builder to check the rollout path, then references @Research and @Builder by name to turn the work into a final launch brief with the source files attached. Because the handoffs are explicit, you can see who did what and keep every decision traceable. OpenBot does not ship its own model subscription. It runs on the AI plan you already pay for: Codex signs in with your ChatGPT plan, Claude Code with your Claude plan, and Gemini works with a Google AI Pro or Ultra plan. OpenCode offers free models that need no account at all. You can also connect any OpenAI-compatible endpoint, or run local models in Ollama or LM Studio. The providers listed on the site are Codex, Claude Code, Gemini, Grok, OpenCode, Cursor and Cline, and the same names appear in the app's agent picker. The result is that your existing spend on AI is turned into a team of agents instead of a single assistant. Three design choices define how OpenBot behaves in practice. First, everything is stored on your computer: workspaces, conversations, files and browser data stay on the machine that runs OpenBot, not on OpenBot's servers, although the AI provider you choose does receive the prompts your agents send to it, and pages an agent opens use the network. Second, you can change the provider and keep the agent: an agent keeps its workspace and conversation when you restart the app or move it to a different provider, so a long-running piece of work can continue under Claude Code after starting under Codex. Third, OpenBot includes a built-in browser, and agents can open, read and control pages in it, which is how an agent can load a local sign-in page such as localhost:3000/sign-in while doing QA work. OpenBot also lets you work at your own pace and with other people. You can queue the next task: send more work while an agent is busy, and messages wait in a queue that you can pause, resume or cancel. The app is multiplayer, too, so you can invite your team to collaborate live with the same agents, and colleagues can follow work in a shared channel and watch an agent hand a task from one teammate to another. Signing in is optional; the app works without an account, and you need one only to invite other people to your team. Getting started is deliberately short: download OpenBot, connect a provider, then describe the agent you want in one prompt, check its instructions and save it. The methodology behind OpenBot is straightforward. Instead of building one more chat interface, it gives agents roles, a workspace that persists, and the ability to talk to each other. A role is defined by the prompt you write when you create the agent: you describe the agent you want, check its instructions and save it. From then on that agent keeps its name, its instructions and its workspace, and it can be moved between providers without losing its place. Work is passed around by messages and attached files rather than by copy-pasting between tools, and a queue holds new requests until the agent is free. Everything runs on the computer that runs OpenBot, with a browser built in for the pages agents need to read or control. The practical benefit is that you pay nothing extra for the app itself. OpenBot costs $0, with no hidden fees and no locked features; the only cost is whatever you already pay your AI provider, through a plan or an API key. Because agents can hand work to each other, a single request can turn into a chain of checks, an evidence review, a rollout check, a test and a rollback step, without you shuffling between apps. Because the provider can be changed without losing the agent, you are not locked into one vendor's model for the life of a task. And because workspaces, conversations, files and browser data stay on your computer, the material you produce stays with you rather than living only in a hosted service. The scenarios described on the site are concrete. In a launch planning workflow, a planner agent prepares the launch plan, tags it Research and keeps every decision traceable, while a Research agent verifies the evidence and a Builder agent checks the rollout path, producing a launch brief and metrics files. In a coding workflow, an agent reads billing code, reports that six tables use it, moves the billing tables to their own schema, changes four files and writes the migration, then hands the test work to a provider that continues the migration. In a team channel, one teammate reports a failing sign-in test on Safari, passes it to another, who fixes it in session.ts and asks a third to review and merge it. Agents can also load a local sign-in page in the built-in browser, steer a request such as summarizing the support inbox or drafting the release notes, and queue extra work, like checking new sign-ups, while the agent is still busy. OpenBot is aimed at people and small teams who already use coding and chat agents and want those agents to work together: developers, technical teams, and anyone coordinating research, releases or QA with AI. 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. The app is free at $0, with no account required unless you invite other people to your team. The source code is public on GitHub under the PolyForm Noncommercial License 1.0.0, so you can read, change and run it for any noncommercial purpose; commercial use needs a separate license. Users should note that OpenBot 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 should be given only tasks you trust, with backups kept. OpenBot's value proposition is simple: a free, local, open-source workspace that turns the AI plans you already pay for into a persistent team of agents that share work, files and conversations on your own computer, and lets your colleagues join them live.