Bops runs a team of AI bots on a shared cloud computer
Bops is a Fair-Source Mac app, 221 stars in three days, that runs a team of AI bots on a shared cloud computer, with each bot reachable from Slack, Telegram, Discord, phone and email on paid plans and able to buy with Stripe-approved cards.
Image: GitHub
Why it mattersA small team can hand email triage, invoicing and research to a watchable fleet of bots on one cloud computer rather than build a bespoke agent stack, with every send, create and pay waiting for a human tap by default.
A small business already pays several SaaS tools for an inbox, a pipeline, invoicing and research, and asks a human assistant to drive them. A new Fair-Source Mac app replaces that human with a team of AI bots that work on a cloud computer the user can watch live and take over at any time.
The app is called Bops and is maintained in the OrgoAI organisation on GitHub by Nick Vasilescu, who created it and is now developing it with Orgo. It has 221 stars and 64 forks on day three and runs on Apple-silicon Macs.
What each bot can do
Every bot works inside a cloud computer provisioned by Orgo: four cores, 16 GB of RAM, four screens, Chrome, LibreOffice, GIMP and Inkscape. On the Free and Pro plans all a user's bots share one computer; the Max plan gives up to three. A main bot called Boppy (which the user can rename) runs the team and hands work to specialist bots the user adds, and the bots keep threads with each other and report back in the chat.
Bots reach the user through the app, Slack, Telegram and Discord. On the Pro and Max plans each team also gets a phone number and an email address ending in bops.bot, so a user can email a task or call the bot and talk to it live. The Vault stores logins and 2FA keys in the Mac's Keychain, and the README states that no model ever sees them. Reading runs at once; sending, creating and paying wait for a human yes by default, and even a bot set to "Just do it" still asks before paying.
What ships, and what powers it
The server is a Next.js app the Electron shell starts on 127.0.0.1:3210. Tasks on the bots' cloud computers run against OpenAI's Responses API with the computer-use tool. Tasks on the user's own Mac run against OpenAI's Agents API with the Codex CLI and a Chrome of the bot's own, and only have shell access when the user turns on Full access in Settings. The repository credits Orgo for the cloud computers, OpenAI for chat and tasks, Honcho for long-term memory, Composio for the roughly 1,400 app connectors, treg for business lookups, AgentMail for email, AgentPhone for text and voice, and TypeSafe for small judgment calls.
Self-host and licence
The project is under FSL-1.1 with an Apache 2.0 Future License: each version becomes Apache 2.0 two years after release, and the current licence only rules out offering Bops as a competing product or hosted service. Setting BOPS_SELF_HOSTED=1 tells the app to call each provider directly with the user's own keys in .env.local and keep state in .data/ on the Mac; a small relay in edge/ can give the webhooks a public HTTPS address. On the hosted path, Orgo's own keys stay in Bops Cloud and the user's Mac gets only a key for their own mailboxes and a spend-capped executor key for tasks.
A founder, operations lead or sales engineer who already runs these tasks across tabs can hand the drudge work to a watched fleet and keep the right to intervene, without building a bespoke agent stack. The roadmap notes multi-harness support, so the OpenAI dependency is explicitly a starting point.
Source
Primary source: OrgoAI/bops on GitHub, FSL-1.1-ALv2.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.
