DEV Community

TaskHandoff
TaskHandoff

Posted on AI-assisted

You can build your own Codex Desktop. The glue is the hard part.

#ai #devtools #productivity #opensource

There's a genre of blog post you've definitely seen. The title is usually something like "Own the Harness,
Rent the Intelligence."

The argument is correct: your rules, your skills, your tooling should move with you when you change models
or subscriptions — instead of being locked into somebody's account.

Someone recently actually did it, and then wrote a very honest post-mortem.

He pulled it off. Then he went back to Codex Desktop.

The post is I Wanted to Own the Harness. Then Codex Desktop Won.
(Jory Pestorious, Aug 2026). His original draft was called "Own the Harness, Rent the Intelligence."

And he genuinely did achieve portability — "portability is what let me cancel Claude Max without abandoning
my rules."

But he ends up admitting he kept opening Codex Desktop anyway. And the reason he gives is the real thesis
of this article:

"I've built the rest myself more than once. One version combined a terminal harness, a provider,
MCP servers, editor integration, remote access, a scheduler, notifications, voice, and the code
connecting them. A task started in one tool could not see the context in another. An update broke a
path I had forgotten was fragile. The pieces worked, but keeping them connected became its own project."

Every piece worked. The glue became the project.

He puts it even better a few lines later:

"'You can build it yourself' is true in the same way that 'you can change your own oil' is true.
The missing number is what I wanted to do with that Saturday."

What he was actually staying for

The interesting part is that he spells out why he stayed, and those two sentences read like a feature list:

"Codex became the window I kept open. My work sat in visible tasks instead of terminal sessions
I had to remember."

"Remote setup took a QR code. I could talk through an idea, pick up the work from my phone, and
let a scheduled task return to the conversation where it began."

Not "the model is smarter." Not "there are more tools." It's:

  1. Work you can see — instead of terminals you have to remember.
  2. Remote access that just connects — a QR code.
  3. Picking it up from your phone — no re-establishing context.

None of that has anything to do with the model. That's a control plane.

The open-source gap was never the agent

Look at where the open-source energy has actually gone:

  • OpenCode, an open-source AI coding agent — 1,274 points, 618 comments on HN. The agent layer is solved and thriving.
  • Plandex, MyCoder, Sidekick, Agentty — there are more open-source agents than anyone can try.
  • Meanwhile, "run your agent anywhere, on any machine" is almost entirely cloud products: Boxes.dev (105 points / 79 comments), Omnara (YC S25, 147 points / 161 comments).
  • The one open-source project pointed the same way, Proliferate — "open-source, self-hostable Codex for any coding agent" — sits at 46 points and 16 comments. The seat is basically empty.

And on the other side of the ledger: the Codex app launch post has 805 points and 638 comments on HN.
The "Linux support is finally in preview" post has 469 points and 315 comments.

So: the agent layer is open source and winning. The control plane is closed or hosted.
That gap is exactly why one person gluing it together by hand ends up with a project instead of a setup.

That's the seat TaskHandoff takes

TaskHandoff is an open-source (Apache-2.0) control plane. It doesn't replace your agent — it replaces
the glue that connects people, machines and sessions, and keeps them connected:

Browser / Desktop / Mobile
            │
            ▼
       Control Plane     ← one console: node inventory + instance board + session view
            │
            ▼
         Node Agent      ← one per machine (home, work, customer, cloud)
            │
            ▼
   Controlled Instance   ← one isolated container per session
Enter fullscreen mode Exit fullscreen mode

Mapped to the three things he was actually staying for:

  • Work you can see → the AI session center. Session state across instances streams in real time over WebSocket, so ten machines are still one board.
  • Remote access that just connects → install a Node Agent and that machine is a node. No signing up to someone else's cloud, and no QR code handing control to a third party.
  • Picking it up from your phone → a mobile client. iOS and Android connect directly to the Control Plane you deployed.

Plus the parts that make it hold together: the Node Agent owns instance lifecycles (restart the control
plane, close your browser — the instances keep running, so "a scheduled task returns to the conversation
where it began" doesn't require a hosted service), multi-node management, environment templates,
Controlled Instances with Docker isolation, and managed Git credentials scoped per remote.

It doesn't swap Codex for another agent. You bring your own.

Quick start 

curl -fsSL https://github.com/edgestorage/task-handoff/releases/latest/download/install-server.sh | sudo sh
Enter fullscreen mode Exit fullscreen mode

Honest caveats

TaskHandoff is not yet a product that competes with Codex Desktop on polish. There's no floating
animated dog, no voice, none of that carefully finished desktop feel. It works on the layer underneath —
how tasks, machines, sessions and credentials get seen and connected.

If what you want is a beautiful integrated desktop experience, Codex Desktop is genuinely better at it
right now. The author of that post made exactly that trade, and it's a reasonable one.

TaskHandoff is also still Beta — the README says plainly that breaking changes may land between releases.

Top comments (0)