alt Hacker NewsI think you and I are cut from the same cloth. Role-based pipelines and coordination with scoped permissions generated at runtime and the ability to communicate is the end game in my opinion, for now at least. Orchestration finally clicked with me when I tried out Gas Town six months ago and I immediately created a system to offload it to the cloud by using a combination of GCP CloudRun + Firestore (for temp file storage and to fill role of beads). Right when I finished ironing out the kinks Anthropic laid down the hammer on how users can use subscriptions and I abandoned it.
Now I am using custom pipeline/messaging control plane that spawns microvms with scoped creds minted at runtime. I had to make my own control plane specifically because everyone is focused on agents with personalities rather than roles and pods of workers. I like everything about Buzz except for that.
I'm slowly inching towards my own control plane because my skill-based workflows (not Claude Code Workflows) are brittle but still work better than anything else I've tried. Enforcing the pipeline has been mostly successful but I'd greatly prefer something more structured.
I've been dipping my toes into the waters of higher-level orchestration for a while now but keep scurrying back to driving CC mostly directly. Any extra layers I've added have just caused too much waste (time & tokens) or otherwise produced inconsistent results. I want to "live" in the decision making space. I want to be consulted for decisions (with context provided so I can context-switch easier), I want to review plans, I want to review the actual UI (when there is any), and I want to be able to easily inject new ideas/tickets into the machine (and probably so way to adjust issue priority).