I tried a few of those and they are shiny but each eventually has their own bugs and quirks and limitations and I always felt like I was trying too much of my active workflow into a tool that could crash and lose all me sessions.
Whenever I need to change or fix ccwt I just spawn an agent with a fix and then I merge and rebuild the tool and it automatically autoupdates and restarts in the herdr tabs. This way I don't have to replace the "outer shell" of my agents for every change I make. Only when herdr itself gets reinstalled (often herdr can reattach to the same sessions but sometimes you just need to stop everything and restart all the agents. Losing progress notification state in the process)
I found a more modular approach that works for me:
1. Herdr terminal multiplexer 2. My custom orchestrator, which I grew out organically based on what I actually need and I feel I can easily change. It started like a minimal reimplementation of wt (worktrunk) but grew out into an integrated constellation of TUIs that leverage herdr API to drive herdr and help me navigate in herdr
Just sharing as an example of the pattern. It's not meant to be an useable tool by anybody else I think.