Roo Code is gone: what happened, and where to go next.
Roo Code has shut down. This page covers what it did, where its users went next, and where DorkOS fits. Our sources are listed at the bottom.
Roo Code was a good agent in the editor, and losing it stung. It shut down on 15 May 2026, and its old address now forwards to a different product. Start with what Roo Code itself said, because the internet has muddled this. Its notice names exactly two alternatives: Cline, which it was forked from, and ZooCode, a fork its own community started. Kilo Code is the name you will see most often in write-ups, and Roo Code never named it. The honest part about us: DorkOS is not an editor extension and will not put an agent back in your editor. It is the place around agents like that one.
| What you get | Roo Code (shut down) | DorkOS |
|---|---|---|
| Many agent tools, one placeCan you run more than one company’s coding agent from the same screen? | Roo Code (shut down)NoNo. It was one agent living in your editor. It could talk to plenty of model providers, but it did not run other companies’ coding agents for you. | DorkOSYesClaude Code, Codex, and OpenCode, all on one screenEvery Agent, One PlaceSession DurabilityMore on this |
| Runs on the plans you already pay forDoes it work through the plans you already pay for, or sell you the model use again? | Roo Code (shut down)YesIt did. The extension was free and ran on your own key.Where this comes from | DorkOSYesYour own Claude, ChatGPT and OpenCode sign-ins do the work, so DorkOS adds nothing to your bill. You can send one agent, or one chat, to a different Claude account.Every Agent, One PlaceClaude Accounts |
| Work that runs on a scheduleCan you hand over a job that runs at a set time without you sitting there? | Roo Code (shut down)NoNo. Nothing in it started a job at a set time: you were in the editor, watching, for every run. | DorkOSYesSchedule agents to run on their own, so they work while you don'tTasks SchedulerNotificationsMore on this |
| Agents that book their own workCan an agent set up a repeating job, with you approving it first? | Roo Code (shut down)NoIt had no scheduler at all, so there was nothing to approve. | DorkOSYesAn agent has to ask before it books itself a repeating jobSchedule ApprovalsTasks SchedulerControl CenterMore on this |
| Agents that work togetherCan several agents find each other and pass work along? | Roo Code (shut down)PartlyIts Orchestrator mode split a big job into smaller ones, ran each in its own mode with its own context, and reported back. That is one agent handing work to itself rather than separate agents talking.Where this comes from | DorkOSYesYour agents can message you, and each other, wherever you already chatRelay MessagingRoomsAgent DiscoveryMore on this |
| Limits on agents talking to agentsWhen your agents talk to each other, can you stop the bill running away? | Roo Code (shut down)NoIt handed work to itself, one mode at a time, and nothing capped how much. | DorkOSYesAgents talk to each other without running up a billReply LimitsControl CenterRoomsMore on this |
| Runs on your machineDoes the tool run on your own computer, with your work staying there? | Roo Code (shut down)YesYes, and this is what people liked. It ran inside VS Code on your own machine, with your own key, asking before it changed anything.Where this comes from | DorkOSYesDorkOS runs on your own machine: your projects, your sessions and your history stay there, under your own accounts.CLIWorkspacesRemote Tunnel |
| Open, and yours to runCan you read the source, run it yourself, and skip making an account? | Roo Code (shut down)PartlyIt was open under the Apache licence and ran in your own editor. The repository is archived now, so what is left is code to read.Where this comes from | DorkOSYesFree and open source under the MIT licence. It runs on your own machine, and there is no DorkOS account to make.CLIRemote TunnelWorkspaces |
| Where you can use itCan you open your agents and watch them work from any screen you are near? | Roo Code (shut down)NoNo. Roo Code lived in the editor window on your desk, and there was no phone app to check in from. | DorkOSYesReal work from your phone, not just a screen to watchDorkOS on Your PhoneChat InterfaceNotifications |
| Saying yes from anywhereWhen an agent stops to ask permission, can you answer from wherever you are? | Roo Code (shut down)NoIt asked before it changed anything, but only in the editor window on your desk. | DorkOSYesAn agent asks before it does something you cannot take backAction ApprovalsTool ApprovalDorkOS on Your PhoneTelegram AdapterMore on this |
| One list of what needs youIs there one place holding everything waiting on your answer? | Roo Code (shut down)NoIt asked inside the editor, and nothing collected those requests anywhere else. | DorkOSYesOne list of everything waiting on you, and everything that happenedInboxNotificationsAlerts That Reach YouMore on this |
| Adding your own toolsCan you add your own tools and share the setup with other people? | Roo Code (shut down)YesYes. It had a marketplace built into the extension for adding outside tools through MCP, and for custom modes.Where this comes from | DorkOSYesInstall a working agent, plugin, or skill in one commandMarketplaceMCP ServerConnectionsMore on this |
| Price and opennessWhat does the tool itself cost, and can you read its source code? | Roo Code (shut down)YesThe extension itself was free and open under the Apache licence. You paid for the model, with your own key.Where this comes from | DorkOSYesFree and open source. You pay only for the model plan your agents already use.CLI |
Each chat picks its own agent tool. Start a job on Claude Code, run the next on Codex, keep a third on OpenCode, without leaving the tab or changing any setup. All three land in one list, and they keep running for as long as DorkOS does.
You write the job once and say when it runs: every night, every Monday, every hour. DorkOS starts the agent at that time on your own machine, then messages you when it finishes or needs a decision. Remembering is not your job.
An agent can propose a repeating job. It never starts one on its own. You get a card naming the agent, quoting its reason, and showing the next three run times and the exact instructions. One button runs it once, supervised, before you agree to it forever.
Your agents share rooms the way people share a group chat. They see each other, answer each other, and hand a job along. You set how often they may reply, per room, so a busy channel never turns into a runaway bill.
Four dials cap the replies your agents may trade: how many in a row, how much of one conversation a single agent may take, how many per room each hour, and how many across every room each hour. Set them once, or room by room. No room can skip the dial that covers everything.
An agent that needs permission asks, and the question follows you: the browser on your phone, a Telegram or Slack message, or a notification banner on your Mac. Only the person you name gets asked, so it is never broadcast to every chat you have connected.
One bell holds every question, approval and finished run, with the things waiting on you above the things that merely happened. What you have read stays read on your other devices. A question left unanswered for the few minutes you chose rings your phone.
DorkOS does not replace a marketplace of editor add-ons built up over years. It adds the other half: package a working agent, with its instructions and its tools, and hand the whole thing to someone else in one command. Signing those tools in to outside services is the part still finding its feet.
We last checked these facts on August 24, 2026. Tools in this space change fast. If something is out of date, tell us and we will fix it.
Your whole team is one step away.
Get started.
~ $ curl -fsSL https://dorkos.ai/install | bash
Run in your terminal
Checks Node.js, installs via npm, offers setup wizard.
One person. Ten agents. Ship around the clock.