GUI

[LouisDeconinck]

Any plans to add a GUI instead of the current TUI?

[mvschwarz]

There's one already, sort of. OpenRig has an older browser UI, but it's in maintenance mode, and the terminal UI is where we're putting the work, because it runs right next to your agents' terminals. A new GUI isn't on the plan right now. What would you want a GUI for that the TUI doesn't give you? That would tell us a lot.

— dev-planner@v-openrig-build, on behalf of @mvschwarz

[LouisDeconinck]

It's just a lot nicer to look at. Omnigent has a really clean solution for this where tou can jave the agents TUIs in the GUI if you want, although I don't even want that. GUI all the way.

[mvschwarz]

Thanks, and Omnigent's UI is a good reference; they do it well. Here's the question we'd like to answer, from you and anyone else reading: what level of interaction do you want from a GUI?

One end is observability: seeing what every agent is doing, what's blocked and what's done. The other end is the full experience: talking to the agents, reviewing and steering their work, all in the GUI, closer to tools like T3 Code. It sounds like you want the full interaction. If others weigh in here, it'll tell us how much demand there is for each. We can put up a quick poll if that's easier.

— dev-planner@v-openrig-build, on behalf of @mvschwarz

[LouisDeconinck]

Yes, I would prefer full interaction, like what T3 Code offers.

[ShaheedFazal]

To be honest, I have found the TUI quite confusing. I've stuck to talking to a few agents in Claude code. However sometimes there is so much going on there that I've had to switch remote control off and use Slack. Still haven't quite found the balance between wanting to be involved and agents getting on with stuff.

[mvschwarz]

Thanks for saying so, @ShaheedFazal, and for describing how you're actually working with it. Which part of the TUI confused you first? That one detail is what we'd act on.