No, this is pretty much the anti-juce!

There's no c++ in it, it's all Go/Javascript. And all the UIs are HTML. JUCE is a great choice for some things, but this wasn't one of them!

▲

MomsAVoxell an hour ago | parent [-]

Ah, very interesting! I'm a little disappointed, but it's understandable.

Well, my first run wasn't very pretty .. installed it on a MacBook Air M5 with 16Gigs of RAM, set it up to access the local ollama instance (because I'm cheap like that), gave it a local JUCE app with a prompt to "analyze the project for issues porting from 32-bit to 64-bit" .. plugged in the laptop as it started processing, and then the system froze. I guess Juggler doesn't like display/USB enumeration events while its busy having ollama chug up all the resources .. well, that produced a system crash .. so came back, set it all back up again, and was .. after a few minutes .. told "the 'ls' tool is not available on this system" .. hmm .. I guess I might have missed a few setup steps in my rush to get it cranking on my JUCE project ..

In any case, will tinker with it some more, looks really great and a nice way to organize AI into a functional UI - especially better than some of the other things I've been using lately (hermes, mostly..) ..

▲

julesrms an hour ago | parent [-]

Hmm, that's odd. Would like to dig into that more if you can find any more clues about what went wrong. Feel free to message me if you want to discuss it

	▲	MomsAVoxell an hour ago \| parent [-]
		The 'ls' problem is me just being a dufus and not setting up ollama to have tool access .. but I can confirm that plugging/unplugging my laptop into a USB-C hub (to get another monitor and keyboard/mouse) seems to plague Juggler in such a way that the system reboots, and only while it is actively engaged in an ollama connection, answering a prompt. Maybe its a resource issue - this is not the fattest machine for the job, after all.