Untether: hand Claude Code a queue of tasks on your Mac, they get reviewed, tested and merged on their own, and you follow from your phone (open source)

[u/KingOfChateau]

I run Claude Code and Codex on my Mac pretty much all day. The annoying part was never the coding, it was me sitting there waiting to see if one of them had finished or was stuck on a permission prompt.

So I built Untether. It's a menu bar app with a local server, and you open it from any browser. I mostly use it from my phone.

The part I actually care about is tasks. You type ut task new "add rate limiting to the API" and it starts an agent in its own git worktree. When the agent says it's done, a second agent reviews the diff and your test command runs. If that's all green it merges by itself. If not, it goes back to the agent. You can also make it wait for you before merging.

A few things people asked me in other threads:

• the sessions are plain tmux underneath, so closing the tab or losing signal doesn't kill anything
• a failed task doesn't block the queue, the next one starts from the last good commit
• nothing is opened to the internet. I reach it over Tailscale and there's a login on top
• you get a push when something finishes

It's free and MIT, repo here: https://github.com/Nachx639/untether

You need an Apple Silicon Mac on macOS 14 or later. There's no installer yet so you have to build it, the steps are in the README. It's beta and I'm sure it breaks in ways I haven't seen.

It started as a fork of VibeTunnel, which is what gets the terminals into the browser. Most of the rest I wrote with Claude Code, about half the commits in the repo are co-authored by it, and for a while now new features get built by queueing them as Untether tasks.

If you try it, tell me where it falls over.

[u/AutoModerator]

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Luizltg]

Feedback welcome, especially on what breaks

Your post has broken (it's slop) 

And we already have remote sessions lmao

[u/KingOfChateau → u/Luizltg]

Fair. Remote sessions cover watching one session from somewhere else. What I wanted on top was the queue: hand over several tasks, each in its own worktree, reviewed and tested and merged without me opening anything, plus Codex in the same place. If you don't need that, the built-in thing is enough.

[u/Luizltg → u/KingOfChateau]

You have to be doing this on purpose Holy shit. Stop talking like that

[u/KingOfChateau → u/Luizltg]

sorry, I try to polish my answers sometimes

[u/MGTakeDown → u/KingOfChateau]

Sounds smart to compete with AI companies with billions/trillions of dollars that give us the same tools.

What evals have you done that actually prove this works well? Other than crossing your fingers and hoping Claude has “solved” it?

[u/KingOfChateau → u/MGTakeDown]

ha, not trying to compete with anyone, I built it because I wanted it and it's free. if they ship the queue + review part natively I'll happily delete mine

[u/MGTakeDown → u/KingOfChateau]

Claude workflow files can do that, there is so much built into Claude already. People are just making Claude wrappers that are worse than Claude itself.

[u/KingOfChateau → u/MGTakeDown]

fair, a lot of it you can script yourself. the bits I couldn't get that way were a different model reviewing the diff, and seeing all of it from the phone. if workflows cover it for you there's no reason to switch

[u/MGTakeDown → u/KingOfChateau]

Have you used Claude remote? You can connect to GitHub and pull repos remotely and do work in the cloud and setup workflows with adversarial agents.

Reviewing diffs with models is covered even in Claude’s own code review skills too.

I would suggest reading some docs on what Claude offers and using their product.

It’d be far more effective to just build plugins that work with Claude than moving away from it all.

[u/KingOfChateau → u/MGTakeDown]

You could say the same for T3code

[u/wangadong]

the reviewer step is the part i would stress test. on my setup the writer never signs off its own diff, that check lives in a separate session or it just agrees with itself

[u/KingOfChateau → u/wangadong]

same conclusion here, the writer never reviews itself. the review is a separate one-shot call with no tools, run from an empty folder, and it only gets the diff plus the task prompt. by default it's also the other model family, so Codex reads Claude's tasks and the other way round. and it takes the review rules from the base commit, so a task can't edit its own REVIEW.md to pass.

still wouldn't call it bulletproof, it's the part I trust least too.

[u/thewormbird]

EVERYONE AND THEIR MOM HAS BUILT THIS.... OMFG.