I just realize we could modify the CLI installation docs:

uv tool install openhands

And then

uv run openhands

which is way more efficient than

uvx --from python 3.12 openhands

which may require re-download and build everytime.

I'm on it! Xingyao Wang can track my progress here.

I think after installing as tool, running with

openhands

also works?

Summary I've successfully updated the OpenHands CLI installation documentation across the docs repository to recommend using

uv tool install openhands

instead of

uvx --python 3.12 openhands

. Changes Made ✅ Files Updated: 1.

openhands/usage/run-openhands/cli-mode.mdx

- Main CLI documentation 2.

openhands/usage/run-openhands/local-setup.mdx

- GUI server setup via CLI 3.

openhands/usage/run-openhands/gui-mode.mdx

- GUI prerequisites 4.

openhands/usage/windows-without-wsl.mdx

- Windows-specific instructions Key Improvements: • ✅ Changed installation command from

uvx --python 3.12 openhands

to

uv tool install openhands

• ✅ Added upgrade instructions using

uv tool upgrade openhands

• ✅ Simplified usage - users can now just run

openhands

or

openhands serve

after installation • ✅ Updated all related commands (Docker, serve, etc.) • ✅ Simplified shell aliases since the command is now just

openhands

Benefits of this approach: • More efficient: Avoids re-downloading and rebuilding each time • Easier to upgrade: Simple

uv tool upgrade openhands

command • Cleaner usage: Just run

openhands

directly after installation All changes have been committed locally with a clear commit message explaining the improvements. ------------------------- Would you like me to: • Push these changes to a new branch and create a pull request? • Keep the changes local for now? • Make any other adjustments before pushing? _{View full conversation}