thanks! will be checking out your project as well. if someone is running 5+ agents for different features i recommend just stating them as different objectives of the claude session and just let claude code auto-spawn sub-agents that handle them.
it seems like ai providers are getting better at deciding when to make sub-agents on their own. but i'm actively exploring this and will hopefully have more to report back sooner than later. your approach is cool.
i have found that the agent cli tools running in the panes are more dialed in by having the local directory structure as context and the best streaming text interface to show ai output on. the chat panel is kind of a nice to have as it's familiar. you can highlight text on the terminal > right click > choose Fix This|Explain This and it's sent to the chat panel to dig into more.
it's also, helpful for asking tangential questions about the current claude session, while allowing it to keep running but not interfering with it.
Creator here, happy to answer questions.
A quick demo of the auto-snap workflow: you type 'claude' or 'codex' in any pane, Yaw detects it, and splits — agent on the left, shell in the same directory on the right. When the agent exits, the split closes automatically. It sounds trivial but it removed a surprising amount of friction for me.
no dark patterns, loads quickly, uses fathom for analytics so no tracking. There are affiliate links to LendingTree, but they're just text links and i tried to be non-obtrusive to the ux.
it seems like ai providers are getting better at deciding when to make sub-agents on their own. but i'm actively exploring this and will hopefully have more to report back sooner than later. your approach is cool.