https://app.all-hands.dev/launch route lets you create shareable links that open OpenHands with one or more plugins already selected, install a single plugin as an automation, or start a conversation with a message and no plugin.
This is useful for:
- adding a “Try it” link or badge to a plugin README
- sharing a pre-configured plugin in docs, issues, or Slack
- building internal test pages for plugin development
/launch is a Cloud route, not a standalone REST endpoint. When starting a conversation, the user confirms the link before OpenHands uses the normal V1 conversation flow described in the Cloud API guide.Before You Start
You will need an OpenHands Cloud account. For plugin links, you also need a plugin or skill stored in a Git repository and its source (and optionally its branch, tag, commit, or subdirectory path). Message-only links need no plugin.Step 1: Define the Plugin
Create a JSON array of plugin definitions. Each item uses this shape:source- where the plugin lives, such asgithub:owner/repoor a Git URLref- optional branch, tag, or commitrepo_path- optional subdirectory inside the repositoryparameters- optional configuration values that OpenHands shows as editable inputs before launch
The same format works for skills. For example, a skill in the OpenHands extensions repo would use
"repo_path": "skills/github".Step 2: Encode the Plugin Definition
Theplugins query parameter must be a base64-encoded version of your JSON array.
plugins query parameter in your /launch URL.
Step 3: Add an Optional Starting Message
If you want the launched conversation to start with a prompt, add amessage query parameter.
pluginsloads thepr-reviewplugin fromOpenHands/extensionsmessagepre-fills the initial task for the conversation
Step 4: Open the Launch URL
When someone opens the link in OpenHands Cloud:- They sign in if needed.
- OpenHands shows the plugins or skills from the URL.
- Any
parametersvalues are shown as inputs that the user can review or edit. - The user confirms they trust the extension.
- OpenHands starts the conversation with the selected plugin configuration.
Install a Plugin Automation
Addmode=automation to a /launch URL containing exactly one plugin, for example:
Install Automation instead of starting a conversation. If the backend supports plugin-spec preflight, you can review and edit typed configuration fields from the plugin manifest and a suggested trigger before installation. Otherwise, the modal shows the existing parameter inputs. Links with multiple plugins keep the conversation launch flow.
Start With Only a Message
To share a conversation starter without a plugin, provide a nonempty URL-encodedmessage and omit the plugin parameters:
Start. This flow has no plugin trust checkbox because no extension is loaded. Links that include plugins still require the separate plugin trust confirmation. An empty message without a plugin does not start a conversation.
Simple Format for Development
For quick local or staging tests, you can use simpler query parameters instead of base64 encoding:plugins format is better for production links because it also supports multiple plugins in one URL.
Next Steps
- Use the Cloud API guide for authentication and conversation lifecycle details.
- See the REST API (V1) overview for the V1 endpoints behind Cloud conversations.

