brainless
3 days ago
Nice to see a gui coding agent. I use tui agents all the time but I am building a gui one. I use Claude Code, Codex, opencode and a couple other but I do not like the DX/UX.
I often want click a part of the wall of text (from agent) and search for related text, open them up on the side or so. I want to open a linked file. I want to answer multiple questions in an async manner, even come back and continue answering the next day.
There are many prompt level features I want too - orchestrate with subagents, but only the tasks I select - how do I select when there is no checkbox. Or maybe delegate a subagent to dig into (read only) one portion of the chat response. Maybe codify (write) only one task in a list of tasks. So many many other small things.
As a full-time user of coding agents, the TUI barely works for me. I think splitting text, searching in text, merging text are more important in agent driven development than ever before. It is all text, all the way. This is what I am building myself, with my own gui framework.
julesrms
3 days ago
You're not alone - I also revolted against the TUI crowd and created my own GUI-centric harness juggler (https://github.com/juggler-ai/juggler). Might be up your street. If you're not too involved in your own project, maybe help out on mine :)
Honestly, I just don't get the TUI obsession, other than the fact that people are multiplexing many remote sessions over ssh. So my aim with juggler was to have an architecture that could do all the multi-client remote sessions with a GUI/websockets/Y.js sync etc.
subsection1h
3 days ago
> I just don't get the TUI obsession
TUIs can be run on minimal VMs that lack window systems. Using minimal VMs rather than heavyweight VMs allows a dev to run more VMs.
Do you not sandbox agents on VMs?
chicagobuss
3 days ago
Ha, your columns look a lot like why I made my own as well - https://github.com/chicagobuss/crusteo
I loved the utility of paseo but like the OP didn't want to build on web frameworks, so I re-wrote all of it in rust with zed's ui framework for the frontend desktop client.
More on my personal blog about it here: https://chicagobuss.dev/blog/my-setup/
atombender
3 days ago
Hi, I tried Juggler a few months back, and while it's technically impressive as a one-person product, I found it super stressful to use. It emits so much output and activity, in various nested forms.
Where Claude Code and Codex have made progress recently, I feel, is with sharpening the interactivity. For example, Codex will emit a lightweight ream of "thinking", then on completion it will erase this and only show the final, coherent answer. It doesn't show much detail about which commands it runs, either. You can still drill into that, but it's usually the least important thing. Claude also does sub/side-sessions that can talk to the other sessions. So if a session finds an unrelated, pre-existing bug, it can start an adjacent session for the bug fix, and keep abreast on when the fix lands. If you start a side session to do research, it can message the other session with new findings.
I don't know if Juggler is still like it was, but I strongly recommend making it less verbose. I just couldn't deal with the noise.
julesrms
2 days ago
Thanks - that's really interesting feedback!
I guess my schtick with it has always been that I wanted to see all the hidden stuff that claude and others try to hide away inside their "made a bunch of tool calls" type opaque messages. And I've heard from other people who appreciate it for that reason, but really interesting to hear that you found it stressful! I'll definitely go away and have a think about that.
I did add a feature a few weeks ago which lets you toggle whether it folds groups of commands into a single summary item (in juggler style the column view works really well here because you can still browse into those groups and see the tool calls if you want). I've found myself not using that mode because I like to see all the detail, but your comment makes me wonder if that should be the default, and if maybe I should add other "less detail" modes.
atombender
2 days ago
People work in different ways, of course. From my perspective, agents have gotten so good that there is no reason whatsoever to look at what they are doing while they're doing it.
I think we are moving in the direction where agents work a lot more autonomously. Most of my work these days is done by cooperative teams of remote, autonomous agents. They can work for hours and periodically reach out to humans with questions and updates. But there's rarely any point in looking at their work (mostly diagnostic or auditing purposes). So for me, at least, the days of staring at the agent's output are long gone.
But I still use local harnesses for some tasks, and I'm not happy with OpenCode's desktop app. I'd be nice to have a viable alternative.
brainless
3 days ago
Thanks Julian, I just checked it and it looks lovely and ticks quite a few of the boxes in my mental model. I will clone and dig in.
Also, I don't remember how but I have heard of JUCE before and I immediately recognized it even though I have never used it. I think I spend too much time on github :D
natsucks
3 days ago
Using TUI is also architecturally simpler. I don't want to rely upon third-party mappings of the CLI/MCP to the GUI, which are potentially incomplete or buggy.
filoeleven
3 days ago
If you think those are buggy, you should see the first-party mappings of the CLI to the GUI!
LeFantome
3 days ago
I was doing dark magic on my Linux distro the other day and borked it terribly. I had no desktop. I knew my system would reboot. But I was able to get into a TTY and, from there, I was able to run OpenCode. With a little AI help, I get my desktop back and fully recovered. I did not even have to reboot.
0xcafefood
3 days ago
His GUI looks like it's inspired at least in part by Google's Antigravity 2 (https://antigravity.google/product/antigravity-2).
34679
3 days ago
I recently switched from the OpenCode GUI to OpenChamber, which still uses the OpenCode backend. It's pretty great. One of the features is the ability to select a portion of an agent's response and add a comment to it. Comments are sent along with the next prompt. It's also much better at handling subagents. With a proper plan in place, it will send out swarms in waves.
natebc
3 days ago
I'm similar but not really a programmer. I've been a linux sysadmin for a few decades but for whatever reason I prefer using Codex via the desktop app rather than the TUI. The desktop app on linux is fine for me. Note: i've not used it anywhere else but since linux was the last to get the desktop client i'm assuming it's at least as good on other operating systems.
On looking at Prospero it's ... simpler than this is so maybe not robust enough for your wants.
johnny5211
3 days ago
I see the argument but personally I find LLMs to be a perfect TUI application because of their functionality. Text in -> text out is precisely how the models work so the interface doesn't need to go much beyond that.
brainless
3 days ago
I would agree 100% with you if context was not an issue. But it is and a big one. In a chat, I have questions and investigations that should always branch off. I also make tiny test implementations from an ongoing idea (in the chat). Forking the idea, or even running parallel ideas. None of these are possible unless we can manipulate the text, split into smaller chunks and send off to agents.
flufluflufluffy
3 days ago
Yeah but it fails the instant you want to do something audio/visual and actually see/hear anything. Good example right on the OPs site, smoothing a Mandelbrot fractal and working on a set of color palettes.