[hoakiet98]

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.

[hmokiguess]

I've actually was reading up pi.dev website copy today and something stuck with me with what I think is the direction that everyone is lacking.

They say "Change the harness, not your workflow". I think that captures what nobody is doing it right, I feel like there's a large effort towards over-engineering for a workflow and assuming it to be optimal when the real lever to press should be the harness.

Anyways, just an idea, wanted to throw it back your way since you're building in this space. Good luck!