Terragon is gone: what happened, and where to go next.
Terragon 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.
Terragon closed in February 2026, and if you liked it, that was a real loss. You handed it a task, it worked in its own cloud machine against your repository, and you reviewed a pull request at the end. Two things before you pick a replacement. Terragon never said where to go next, so any suggested pairing you have seen online came from a commenter, not the company. And the code did not vanish: it was published as an open snapshot, so you can run it yourself, unmaintained. DorkOS fits if you want agents getting on with work and you reviewing the result. It does not fit if what you liked was that none of it ran on your own computer.
| What you get | Terragon (shut down) | DorkOS |
|---|---|---|
| Many agent tools, one placeCan you run more than one company’s coding agent from the same screen? | Terragon (shut down)YesIt did, and this is the part DorkOS carries on. You could point it at Claude Code, OpenAI Codex, Amp or Gemini, bringing your own subscription or your own keys.Where this comes from | 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? | Terragon (shut down)YesIt did. You brought your own subscription or your own keys, which is the part DorkOS carries on.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? | Terragon (shut down)YesIt did. Its automations ran on a repeat, or started when something happened in your project, like a new issue.Where this comes from | 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? | Terragon (shut down)NoIts automations were set up by a person, never proposed by an agent. | 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? | Terragon (shut down)PartlyIts own feature list said several agents could work together, though it never said much about what they actually did together.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? | Terragon (shut down)NoIts feature list said several agents could work together, without describing any limit on 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? | Terragon (shut down)NoNo, and this is the part that mattered most in the end. The work happened on Terragon’s computers, so when the company stopped, the product stopped with it. | DorkOSYesDorkOS runs on your own machine: your projects, your sessions and your history stay there, under your own accounts.CLIWorkspacesRemote TunnelMore on this |
| Open, and yours to runCan you read the source, run it yourself, and skip making an account? | Terragon (shut down)PartlyThe code is open under the Apache licence, and nobody maintains it. While it ran, it was a cloud service you signed in to.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? | Terragon (shut down)PartlyThere was no phone app, but it hooked into Slack and GitHub, so work could be started from a message or from an issue.Where this comes 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? | Terragon (shut down)NoThere was no phone app, and nothing we found describes approving an agent’s action from one. | 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? | Terragon (shut down)NoIt reported into Slack and GitHub, so whatever needed you landed wherever those did. | 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? | Terragon (shut down)PartlyIt spoke MCP, the common way of plugging outside tools into an agent, so other tools could hand it work. There was no marketplace beyond that.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? | Terragon (shut down)PartlyIt was a paid subscription while it ran, and the code is open now under the Apache licence, which is more than most closed services leave behind.Where this comes from | DorkOSYesFree and open source. You pay only for the model plan your agents already use.CLI |
Terragon got this right early: it never asked you to give up the agent you already liked. That is the same bet DorkOS makes. The only difference is where the agent runs. Terragon started a fresh cloud machine and worked against your repository there; DorkOS starts the Claude Code or Codex already signed in on your own computer, on any folder, whether or not it has been pushed anywhere.
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.
We will not pretend this was a clever argument we made in advance. It is just what happened. A cloud service is someone else’s machine, and when the business behind it winds down, so does the thing you built your week around. The agents DorkOS drives are installed on your own computer, under your own accounts. The worst we can do to you is stop writing the screen around them.
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.