DorkOS + OpenCode

If the model is the thing you want to swap, OpenCode is the best of the three at it, local models included. If the agent is the thing you want to swap, that is the gap DorkOS fills: one list holds a Claude Code session, a Codex session and an OpenCode session, and you pick per job.

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.

The pieces are there if you want to build it: OpenCode runs headless as a server with an HTTP interface, so your computer’s own timer can start a job on a schedule. What you sign up for is the plumbing around it: deciding what runs where, keeping a record of what happened, and arranging to hear about it when something needs you.

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.

Helper agents are good at keeping a long search or a noisy build out of your main conversation, which is what most people want them for. The relationship is always one agent and its helper inside a single session, so there is no group of equals comparing notes.

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.

A plugin is a plain JavaScript file you drop in a folder, which is a low bar if you would rather bend the tool to your own habits than pick something off a shelf.

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.