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.
This looks cool! I'll check it out. Out of curiosity: I assume you've also used agents to help build this, and on the site you mention working on this for ~6 months. Most one-man projects I see that use ai seem to focus on creating and presenting a concept as soon as possible
(to a lot of people I think the main benefit of stuff like vibing is that you really quickly get something that you can have others test out).
On the site you also mention being pretty opinionated about the tools you use / build, which I imagine is part of the reason why you spend more time on this before releasing it. What was your experience using ai to build a larger project with a very specific idea / taste in mind?
I must have authored literally a million lines of C++ over my career, and done many talks about clean coding, etc.. But in this one I quite appropriately wrong almost zero lines by hand!
Surprisingly, I've really enjoyed the experience. I have friends who lament that they probably won't be hand-writing code much more, but although I've always loved the craft of coding, I discovered that a lot of the fun I get is just in the end result, not how I got there.
But TBH I think a lot of the GUI agent tools so far have been pretty much terminal apps wrapped in a thin GUI layer, which is why they don't seem to add any value over just doing the same UX in a terminal
UI is clean. could install in Mac. Adding context files at the top is clean. It worked.
Currently I use zed, vscode (for UI). along with claude, codex, Hermes.
Not sure If I will continue to use. But I see it is a clean and good UI, and integrating to my exiting cli's. All the best.
Thanks! I think hearing "the UI is clean" is exactly the reaction I've been hoping for :)
While I've put huge effort into things like its architecture and extension API, it's really trying to just build a lovely UI/UX that has been my motivation on this.
Out of curiosity, did you use JUCE to build this? Were there any interesting gotcha's you encountered along the way?
I've settled on JUCE as my cross-platform app framework (not just plugins) of choice, so it'd be interesting to hear about your experience with building this app out .. could you tell us a bit more about the architecture and any impactful decisions you made along the way with regards to tooling/integration? Is there now a juce-go-module or something like that, which you've wired up to JUCE' web view functionality?
"No electron" is more about avoiding bloat and dependencies.
I come from a hardcore, real-time C++ background and the idea of a product not being a single self-contained binary is just too far for me to go!
(But I don't think the choice of JS back-end should make the slightest difference to anyone using this. I could swap electron in there in the future and probably no-one would notice)
Just wanted to add a follow-up to what I posted above..
In terms of who might be interested in this: I've watched amazing communities spring up around open agents like Opencode and Pi. People are getting into those because of their extensibility and being model-independant. They're great projects, but like many people I know, I really hate being stuck in the terminal for this kind of tool. I also had some ideas around what an agent's UX could be like if every item in the context was a plugin (with its own custom UI).
So I guess if you're a claude/codex user but want to escape the terminal (and let's face it, their GUI apps are also basically the same UX as a terminal but with nicer fonts), I'm trying to do something different here, would be really keen to hear what the enthusiasts think of it!
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.
Cheers, I'll put ACP on my list of things to investigate
This looks cool! I'll check it out. Out of curiosity: I assume you've also used agents to help build this, and on the site you mention working on this for ~6 months. Most one-man projects I see that use ai seem to focus on creating and presenting a concept as soon as possible (to a lot of people I think the main benefit of stuff like vibing is that you really quickly get something that you can have others test out).
On the site you also mention being pretty opinionated about the tools you use / build, which I imagine is part of the reason why you spend more time on this before releasing it. What was your experience using ai to build a larger project with a very specific idea / taste in mind?
I must have authored literally a million lines of C++ over my career, and done many talks about clean coding, etc.. But in this one I quite appropriately wrong almost zero lines by hand!
Surprisingly, I've really enjoyed the experience. I have friends who lament that they probably won't be hand-writing code much more, but although I've always loved the craft of coding, I discovered that a lot of the fun I get is just in the end result, not how I got there.
Great work, it is very funny that I did just the opposite :)
Got fed up with Zed, Cursor, and the other GUI agentic tools and created a console TUI agent for my own use.
There's definitely the CLI and non-CLI camps!
But TBH I think a lot of the GUI agent tools so far have been pretty much terminal apps wrapped in a thin GUI layer, which is why they don't seem to add any value over just doing the same UX in a terminal
UI is clean. could install in Mac. Adding context files at the top is clean. It worked. Currently I use zed, vscode (for UI). along with claude, codex, Hermes. Not sure If I will continue to use. But I see it is a clean and good UI, and integrating to my exiting cli's. All the best.
Thanks! I think hearing "the UI is clean" is exactly the reaction I've been hoping for :)
While I've put huge effort into things like its architecture and extension API, it's really trying to just build a lovely UI/UX that has been my motivation on this.
Out of curiosity, did you use JUCE to build this? Were there any interesting gotcha's you encountered along the way?
I've settled on JUCE as my cross-platform app framework (not just plugins) of choice, so it'd be interesting to hear about your experience with building this app out .. could you tell us a bit more about the architecture and any impactful decisions you made along the way with regards to tooling/integration? Is there now a juce-go-module or something like that, which you've wired up to JUCE' web view functionality?
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!
I thought "Wails" was gonna be short for "Wuby on Wails" lmao
Cool project actually, but I noticed the author said "No Electron" as if Electron is synonymous with JavaScript.
My biggest concern about it actually is using Go to render web front-ends in HTML/CSS hahah so I'm not sure "No electron" is selling me.
"No electron" is more about avoiding bloat and dependencies.
I come from a hardcore, real-time C++ background and the idea of a product not being a single self-contained binary is just too far for me to go!
(But I don't think the choice of JS back-end should make the slightest difference to anyone using this. I could swap electron in there in the future and probably no-one would notice)
Just wanted to add a follow-up to what I posted above..
In terms of who might be interested in this: I've watched amazing communities spring up around open agents like Opencode and Pi. People are getting into those because of their extensibility and being model-independant. They're great projects, but like many people I know, I really hate being stuck in the terminal for this kind of tool. I also had some ideas around what an agent's UX could be like if every item in the context was a plugin (with its own custom UI).
So I guess if you're a claude/codex user but want to escape the terminal (and let's face it, their GUI apps are also basically the same UX as a terminal but with nicer fonts), I'm trying to do something different here, would be really keen to hear what the enthusiasts think of it!
[delayed]