[addajones]

I currently have Claude Desktop installed on a separate Mac mini M4 and control it with Dispatch. Is there a reason to do this method, it still seems the way I have it setup it has full control over the local account I gave it on the Mac mini.

[tyre]

Why would you need an M4 for this? If most of the "thinking" is happening on Anthropic's side, are you running particularly resource-intensive apps?

[spunker540]

The gpu inference happens on anthropics side, but the output of the gpu inference is often many local tool calls. The agent is locally reading files, writing files, compiling programs, downloading artifacts, running tests, invoking CLIs, monitoring logs, inspecting web sites, grepping etc, and can be doing all of that at once, in parallel via subagents, much faster than a single human ever could.

[theptip]

I found Dispatch to be less capable than RC. The latter is more like the direct Code experience (though there are some gaps in RC mode vs in a Claude-owned sandbox).

I’d love to just have Claude use my machine as a sandbox host instead of having to run RC on each host session. (In case you are listening Boris ;) ).

In the meantime I have a janky master RC session that creates new tmux windows and Claude RC sessions for each new code trajectory that I want to run.

The other benefit here is you can drop down and use termux to use Code directly if you hit a RC bug, I found permissions UX to be a bit flaky in the iOS UI.

[hahajk]

Dispatch/Cowork is basically claude code in a container. The section "Why not run it in a container?" would address your question in the post. One example I run into is that Cowork won't download and fill out or read pdfs or other files due to container permissions. Vanilla claude code has no problem using curl and wget.

[_puk]

Cowork gets tangled with git as well. Fails, and then can't delete lock files.

Running a helper from the terminal, making Claude work in a working directory, and then create a .commit file has been my workaround for this for a while now.

Imagine there's a better solution nowadays, but this allows me to use dispatch building on Vercel, so I can check it out from wherever, without too much pain.

[j45]

Claude dispatch does things differently than this. Dispatch is very convenient for somethings (including connectors).

But increasingly it seems like dispatch was slapped on top of cowork incrementally, when there was not an integrated and cohesive strategy across cowork between mobile/desktop/laptop. This is kind of what many of us get/got to learn in our 20's.