[jonnyasmar]

Super interesting mental model here. I'm building a tool, called atrium, that set out to solve similar problems, but I landed on a pretty different model -- workspace > room > stack > pane. I'm really curious to understand more about your concept of topologies, though. How exactly does it manifest in practice? Are they essentially organized units of collaborative work that your agents are executing? Has this unlocked different ways to solve problems for you than you were doing before or is it primarily organizational sugar?

At any rate -- really cool concept. Wish you the best of luck with it!

[mschwarz]

Yes exactly, topologies, aka rigs are basically ways of organizing work that benefits from agent collaboration, but it unlocks many benefits. One of the main benefits is "Context Domains", described in the linked video. Where you can extend the context window for the task you are working on by distributing it across multiple agents. Each agent or pod of agents works on a slice of the task together, sharing state, staying in their lane of expertise. The rig becomes a sum of its parts. A 10 agent rig, each agent with a 1 million context window, could effectively be viewed or operated as if it had a 10 million token context window. For my day job I work on very large brownfield codebases and this was one of my early solutions to being able to work on broad cross-cutting features. I don't rely on this alone but this general ability is quite useful for lots of things.