OpenHands setup: choosing CLI, Cloud or SDK

This introductory webinar explains how to choose an OpenHands setup for coding tasks. The presenters separate where it runs, locally, in the cloud or in a self-hosted enterprise environment, from how users interact with it through the CLI, GUI or SDK. They recommend the CLI for solo work on local files, Cloud for background tasks and team collaboration, and the SDK for custom automation such as dependency updates and migrations.

OpenHands is presented as an AI agent that runs commands and edits code. The speakers describe it as model agnostic, with support for bringing your own model or API key. Local execution in this discussion does not establish that model inference happens offline. They describe isolated sandboxes as the default and advise starting with a test repository. Cloud organization features were in private beta at the time of the webinar.

The demo uses Slack to request an issue for translating a repository into Portuguese, then asks OpenHands to fix it. The Q&A explains how skills can use application APIs and how MCP servers provide another integration route. A presenter says Cloud lacked OAuth support for MCP authentication at the time, while the CLI and local GUI supported it. The SDK is described as open source and intended for engineers who need control over custom coding workflows.