I have a question. Why do I, as a user who clicked...
# proj-agent-canvas
c
I have a question. Why do I, as a user who clicked a link to download OpenHands, need a Web UI to Claude Code?
@nutritious-balloon-65098 make an issue on agent-canvas repo with this question
n
I'm on it! can track my progress here.
Final summary: • Completed the requested task: created a GitHub issue in
OpenHands/agent-canvas
. • Issue created:
#494
— https://github.com/OpenHands/agent-canvas/issues/494 • The issue title captures the user’s question: why downloading/starting OpenHands appears to require a Claude Code Web UI. • Included brief supporting context in the body. • Included the required disclosure that the issue was created by an AI agent on the user’s behalf. Checklist: • Made the issue on the correct repository • Used the user’s question as the basis for the issue • Added context explaining the user’s confusion • Included AI-generated disclosure • No unnecessary code or repo file changes were made Conciseness: • No code changes were made. • No extraneous repository modifications were introduced. • The only external change was the requested GitHub issue creation.
w
Is the question here, like, why does this project exist at all? 😅
c
No? ACP is a protocol that in my understanding, seems best for editors. Why does a Web UI for OpenHands need to be an interface for Claude Code?
Like, I think it's used for the right side panel in editors, for the user to choose an agent CLI or another agent CLI, right?
You said you'd like one download link for openhands. OK, then, idk, why do we try to make a UI for Claude Code - I'm not even sure how it would work... because we need to 'translate' the events? Or maybe I'm totally misunderstanding what this is supposed to do
w
oh we already have an ACPAgent in the SDK! You can plug in any other agent and it mostly connects up to all the other OpenHands stuff The big reason is so that people can use their Claude Max subscriptions etc
Also just psychology--people are really attached to their harnesses 🙃
c
Well, the Codex sub should work
nod 1
oh we already have an ACPAgent in the SDK! You can plug in any other agent and it mostly connects up to all the other OpenHands stuff
Yes, we evaluated it... but the events are different, I thought maybe if we want to make an interface we need to account for different event formats... OK maybe that's not a big problem
w
hmm good to know...I've been nervous to see how well the ACP Agent behaves in the UI
c
just psychology--people are really attached to their harnesses
I... think so, but I don't see a lot of possibility for them to care about a new UI for it... unless it's specialized for agent orchestration, but then what I see, is stuff like running 10-20 in the same time
I propose to not go for ACP: • or at least not for MVP • codex sub should be working anyway, so it is available to people • (indeed CC would not be) => agent-canvas is a Web UI for OpenHands agent, not for all agents Wouldn't that, it seems to me, solve the exact problem we're facing, a single UI/app for OpenHands?
w
I'd like to see how ACP lands in the UI before making a decision. If it "just works" I think we go with it. If it causes a ton of UI headaches maybe we pull back
👍 1