Skip to main content
The OpenHands Cloud 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.
Only share plugins and skills from sources you trust. Plugin launch and installation links ask the user to trust the extension before it runs with the agent secrets configured in their account.

Step 1: Define the Plugin

Create a JSON array of plugin definitions. Each item uses this shape:
The fields are:
  • source - where the plugin lives, such as github:owner/repo or a Git URL
  • ref - optional branch, tag, or commit
  • repo_path - optional subdirectory inside the repository
  • parameters - 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

The plugins query parameter must be a base64-encoded version of your JSON array.
Convert that JSON into base64-encoded text, then use the encoded value as the 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 a message query parameter.
In this example:
  • plugins loads the pr-review plugin from OpenHands/extensions
  • message pre-fills the initial task for the conversation

Step 4: Open the Launch URL

When someone opens the link in OpenHands Cloud:
  1. They sign in if needed.
  2. OpenHands shows the plugins or skills from the URL.
  3. Any parameters values are shown as inputs that the user can review or edit.
  4. The user confirms they trust the extension.
  5. OpenHands starts the conversation with the selected plugin configuration.

Install a Plugin Automation

Add mode=automation to a /launch URL containing exactly one plugin, for example:
The confirmation modal offers 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-encoded message and omit the plugin parameters:
The recipient sees a message preview and selects 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:
This format is convenient for manual testing, but the encoded plugins format is better for production links because it also supports multiple plugins in one URL.

Next Steps