DorkOS vs Conductor

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.

This used to be a Claude Code app and is not one any more: Codex arrived in late 2025, Cursor and OpenCode in mid 2026. Bundling the agents is a real convenience and a real trade. You get whichever version they ship, not the one you installed and signed in yourself. DorkOS drives the copies already on your machine, so your own accounts and settings are the ones in play.

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.

Conductor has a "background tasks" feature, but that only shows you when an agent is waiting on something, and its dispatcher, despite the name, is a box for starting new work rather than anything that runs by itself. Work in Conductor starts when a person starts it.

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.

The cloud tier answers half of this: your agents keep going with the laptop shut. It does not answer where you watch them from, because the way in is still the Mac app on your desk. A phone app is promised on their pricing page. Until it ships, that is a plan rather than a feature.

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.