Live data from Hacker News

Show HN: Juggler – an open-source GUI coding agent, by the creator of JUCE

github.com

41–50 of 128 posts

Re: Show HN: Juggler – an open-source GUI coding agent, by the creator of JUCE

#41
post #32

Having now given it a quick spin, I like the UI concept and could definitely see myself working with this. I ran into a bug(?) almost immediately though, I hooked up Deepseek 4 Pro, gave it a small task and got this ``` LLM error: POST " https://api.deepseek.com/v1/chat/completions ": 400 Bad Request {"message":"The `reasoning_content` in the thinking mode must be passed back to the API.","type":"invalid_request_erro…

Ta for the heads-up, these provider API things are super easy to fix, but hard to keep on top of them changing under our feet!

No problem. A tiny bit more working with it and I think I'm sold, it fits my mental model really nicely, thanks!

Re: Show HN: Juggler – an open-source GUI coding agent, by the creator of JUCE

#42

Earlier quoted context omitted.

TBH I'm not coming from the same angle as all the gas-town fever-dream agent swarming stuff. I'm much more on the hands-on coding side, I tend to do one thing at a time and still do the git commits myself. So that's the UX I'm dogfooding.. However I see all those people out there trying to build these huge agent orchestration schemes, and if juggler's extension system can do that (or could be made to do that with a f…

I think I'm more on your side on that rather than letting agents go wild like Steve Yegge/Pete Steinberger do. In fact OrcaBot quickly adapted into a knee jerk reaction to OpenClaw because I saw that as inherently dangerous. But with regard to Juggler and orchestration, have you seen "claude agents" (started in the terminal as claude agents instead of just claude). I ask because your tree like approach has similariti…

I think that's basically the same as juggler's subthreads. As it progresses I'll work my way through all these kinds of thing and dig into whether there are things I can add or tweak to match their features. I'm aiming to make juggler's extension API flexible enough to support pretty much anything

Re: Show HN: Juggler – an open-source GUI coding agent, by the creator of JUCE

#44
post #40

ACP support would be a big deal and would make this a real contender for me. It looks super nice, but the idea of re-writing my Pi plugins is a real blocker. I’m generally happy with my agent and want to keep that, but I do think the UI could be better and this looks like a neat step that way.

Agreed, ACP should be a minimum requirement on new agentic tooling. Hope this gets it, then I can try using my niche agent.

Message received, I'll make ACP the top item on my TODO list!

Re: Show HN: Juggler – an open-source GUI coding agent, by the creator of JUCE

#45
post #43

Why not use JUCE for UI? :)

An LLM conversation contains a massive mess of markdown, code, HTML, images, god-knows-what else, it needs to reflow and animate. Neither JUCE or any other non-HTML UI framework would be realistic for that!

Re: Show HN: Juggler – an open-source GUI coding agent, by the creator of JUCE

#46
post #41

Earlier quoted context omitted.

Ta for the heads-up, these provider API things are super easy to fix, but hard to keep on top of them changing under our feet!

No problem. A tiny bit more working with it and I think I'm sold, it fits my mental model really nicely, thanks!

Awesome to hear it. I built something that fitted my own mental model, and am assuming others out there have a similar one!

Re: Show HN: Juggler – an open-source GUI coding agent, by the creator of JUCE

#47

@julesrms thank you for lending more credibility to the idea that agent conversations need to be natively branching. It's crazy that we're almost 3 years in on this LLM joyride and we still don't have the ability to do, like, reddit/slack-style "aside" convo threads. ~~edit~~ wait, are you doing that? Love JUCE btw

Can you go more in depth on why LLM conversations should branch reddit-style? That doesn't seem immediately clear to me, and I'd be afraid that the different branches would step on each others toes? (also I'm assuming what you're describing here goes beyond the "fork" feature found in many agent harnesses).

Re: Show HN: Juggler – an open-source GUI coding agent, by the creator of JUCE

#48

@julesrms thank you for lending more credibility to the idea that agent conversations need to be natively branching. It's crazy that we're almost 3 years in on this LLM joyride and we still don't have the ability to do, like, reddit/slack-style "aside" convo threads. ~~edit~~ wait, are you doing that? Love JUCE btw

Can you go more in depth on why LLM conversations should branch reddit-style? That doesn't seem immediately clear to me, and I'd be afraid that the different branches would step on each others toes? (also I'm assuming what you're describing here goes beyond the "fork" feature found in many agent harnesses).

An agent like claude might run a subagent (e.g. to fetch and summarise a web page, or explore a code question) as if it's a tool, so you can't really see what's going on inside it. Juggler makes these sub-threads part of the overall structure, so you can navigate into them.

Another really elegant thing that pops out of subthreads is that to do a compaction, you simply move the entire conversation into a subthread, and let the subthread summarise itself (which they do anyway). So we get compaction as part of the architecture, and you can also dig into that old thread if you need to revisit any of it

Post reply on HN