Would the work you did on getting agent-canvas NPM...
# proj-agent-canvas
h
Would the work you did on getting agent-canvas NPM install ready cover https://github.com/OpenHands/agent-canvas/issues/451 @quick-window-91705?
q
Yes, assuming we aren't interested in install paths besides npm
h
Could you post on that issue with what that looks like now? If we have a solution right now that would help with documentation and could get us to an initial happy path
q
Will leave a note in a sec
🙏 1
For the launch command after npm installation, do we prefer
openhands
or
agent-canvas
?
1️⃣ 3
c
i like
openhands
although it might means conflicts with our current openhands CLI 😞
nod 1
q
We could try to support both? (I think npm allows for multiple launch commands)
c
only concern is that this might break the PATH for existing CLI users since it might just override their CLIs
nod 1
c
could compromise,
openhands-canvas
😅
h
openhands
would be great but it does seem like it'll break CLI for anyone who tries to use it. Does
npm uninstall -g openhands
automagically let the CLI continue to work by chance? Then we could say 'if you want to keep using the CLI you can do this and switch back later? 😬
@quick-window-91705 So you aren't left hanging here
agent-canvas
is 👍 so we don't break things imo
w
yeah I had the same thought. if we think we can adequately take over
openhands
from existing paths that's great