a very primitive form of the near term multiagent agi future is setting up one thread to ping back once its done so you create an implicit kanban/waterfall graph of dependent threads but each preserving their own work and agents
i can't wait to setup a proper ui for this pattern but you can hack it together in most koding agents of choice rn
one way i'm developing Forge (https://x.com/swyx/status/2083654369095156219) is to use it to host all my projects going forward. so I often find myself having t...