So the difference here is it works exactly the same way. It's just the equivalent of ones running on-prem hardware (i.e., your laptop or computer). If you turn that off you can't remote into a session because it's relying on that device's compute to function. Whereas in this case it's a cloud-based instance that's running, separate from your local hardware, which means you can turn your laptop off and you can remote in. Otherwise it's effectively the same thing: an instance is functioning as an orchestrator and it is spinning up agents that are doing parallel tasks that contribute to whatever the orchestrator is trying to achieve. Otherwise I don't really get it because an orchestrator is just an instance that is telling other instances what to do.
2026-10-17 10:28:02
0
DaCkE :
not that usefull tbh, different agents can already do majority of tasks in a single session so this would just be a waste of tokens and usage
2026-10-17 10:44:00
0
Dad :
Claude code or cowork?
2026-10-16 23:18:08
0
Rafael :
have people not been using claude in this manner? i have one orchestrator that will lead various agents (ux, back end, data). works fantastic
2026-10-16 22:43:56
0
Somedudewhodudes :
The problem is I have to talk to the threads to get it to actually build. Have you found a work around for that?
2026-10-17 00:27:48
0
Jorge Santos :
The memory is lost easily. When that is resolved it's going to be great. Until then... Just no
2026-10-17 00:05:21
0
Sftechbro :
Love projects!
2026-10-16 23:57:35
0
To see more videos from user @chase_ai_, please go to the Tikwm
homepage.