https://docs.all-hands.dev/ logo
Join Slack
Powered by
Idea (I think it's come up before, too) If someon...
# proj-agent-canvas
e
Idea (I think it's come up before, too) If someone is already used to running Local GUI in Docker, would it make sense to bundle Agent Canvas into it so they can start using the new interface? With the changes that @better-monitor-61654 is working on, it could help make a seamless migration from Local GUI --> Agent Canvas for those existing users. Of course, preserving the existing install path (via npm) should continue to be an option for users who want to start fresh.
l
Just to clarify the question, do you mean that when people run the old docker command, they would get the new agent canvas interface instead of the old interface?
I think that’s a reasonable path, but I think that it might take a bit of logistics work, and it might be easier to add a banner that the old interface is deprecated and going to be moved elsewhere (as we plan to do on app.all-hands.dev)
c
The two GUIs are working on the same settings, and thus I think just launching the other is almost there
I saw a report here in Slack that starting the agent-canvas just worked, using existing “install”, as in, existing stuff stored in 
~/.openhands
Launching canvas via npm I think does the same, please correct me if wrong. This is more like literally alternatives GUIs on top of the same stored openhands, they work on the user’s oh settings/logs/existing stuff If it doesn’t on some aspect, can we look at that aspect?
l
I personally think it should “just work”
nod 1
(but haven’t tested much myself)
c
Yes, that’s what I mean. I think it should just work already. This isn’t a migration between two different softwares
👍 1
b
Yes, but there are still some issues with agent-canvas + OH backend that sometimes require using the old frontend. For example, agent-canvas does not yet support to setup multiple LLM profiles (at least on my version). And since we should never break things (as during the V1 transition), I would offer the option (via environment variables) to serve both frontends.
Open in Slack
PreviousNext
Powered by