Hacker News new | ask | show | jobs
by CGamesPlay 175 days ago
I strongly resonate with the problem statement, but this implementation was very far off the mark for me. Every interaction feels bad.

I fired it up, and the first thing I notice is that the arrow keys don't work. I can't select Claude Code. Oh, apparently it's in a different control, so I have to press Tab, and then the arrow keys work. Wow, this list of buttons has a slow scrolling animation when navigating it. Can I turn that off? Press enter on Claude, now I'm in a tiny modal window. Press enter, because I want to do the obvious thing, but apparently the obvious thing is "show in launcher", so the background of the modal is weirdly changing while a tiny single character inside the button is indicating that this is the part I'm supposed to be focusing on. No, I want to do the obvious thing of running Claude code. You could easily fit the 4 actions of this form on my screen, but by choosing to use a tiny modal window you're now forcing yourself to use another modal drop-down control to choose the action and a separate "yes actually do it" button, so the OBVIOUS ACTION of RUN THIS AGENT requires pressing tab, enter, down, down, down, enter, tab, enter. Great. Now I'm at a chat interface with an error screen, because it isn't installed. Quit the program, restart, enter, tab, enter, down, down, enter, tab, enter to install. It shows a successful run of the "ACP adapter" for claude. Shift-tab, enter, down, enter, tab, enter. Now I'm back at exactly the same error screen because apparently the install didn't work. Now, I know that you need to be running "npx @zed-industries/claude-code-acp", so I check the docs and apparently I can "toad run COMMAND". But it doesn't work for multi-word commands. And my trial with toad comes to an end.

So I can't test it for anything actually useful right now, but I'll add this to my list of projects to watch. Hopefully, being a UX-focused project, the creator actually focuses on the UX and fixes some of these silly decisions.

1 comments

This has been my experience also, so far. I like a lot about this and want to start using it, but beyond the initial awkwardness of key bindings feeling wrong, it just seems a bit too early for me. For example, most of the agents I tried to get working on my Arch system failed to connect, only Claude Code and Vibe worked. Most worked on MacOS (except Codex, even though it's installed on my system). But I need to be able to set the agent into Bypass Permissions mode, and when I do, I'm still constantly prompted with permissions checks. There also seem to be weird errors caused by fish shell. I'd also really like to be able to define my own custom agents (eg one use case I'd like is to be able to launch Claude Code but swapping out the Anthropic endpoint for OpenRouter's so I can try new models using CC's agent harness).

It's possible this is just part of the learning curve, but it is making me think I'll have to come back to this project in a month or two to see if there are fewer pain points. Great work so far though.