The auto-snap detection is clever - automatically splitting when it detects an agent CLI is a great UX decision.
I took a similar "own the terminal" approach with Pane (https://runpane.com), but organized around git worktrees instead of splits. Each feature gets its own isolated worktree with N terminals, so agents never step on each other's files. The worktree lifecycle is fully automated.
Curious how you handle the case where someone is running 5+ agents on different features simultaneously? That's where the worktree isolation really shines vs. splits in a single repo checkout.
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 took a similar "own the terminal" approach with Pane (https://runpane.com), but organized around git worktrees instead of splits. Each feature gets its own isolated worktree with N terminals, so agents never step on each other's files. The worktree lifecycle is fully automated.
Curious how you handle the case where someone is running 5+ agents on different features simultaneously? That's where the worktree isolation really shines vs. splits in a single repo checkout.
Repo: https://github.com/Dcouple-Inc/Pane (AGPL-3.0)