|
|
|
|
|
by thurn
42 days ago
|
|
I really fundamentally do not understand what problem Gas City solves that is not already solved by normal subagent orchestration patterns. If you want to call your main LLM session the "mayor" and have it delegate its work out to planners and coders and reviewers and QA and so on, this is already a thing you can do! If you want to do this in a reusable way you can create skills and subagent definitions and use /commands, etc. Why do we need hundreds of thousands of lines of opaque Go code to accomplish any of this? |
|
Cynically, he published a book on vibe coding recently, so he may just be grabbing attention as some effort to boost book sales.