yeah us and similar categories of tools prescribe a lot of our specific workflow for worktrees, review, code editing where iterm + tmux is much more flexible. we have to tow the line of what's useful as a built-in feature vs being very agnostic.

i do agree that there's a more novel UX than the same left sidebar with worktrees and middle chat/terminal that is not yet explored.

we've been spiking on what the UI is like to program and monitor the specific steps in the workflow from triggering agent -> planning -> coding -> review -> merge.