OpenHands · jpelletier1 · May 11, 2026 · May 8, 2026 · May 8, 2026 · May 8, 2026
diff --git a/docs.json b/docs.json
@@ -62,6 +62,15 @@
                   "overview/skills/public"
                 ]
               },
+              {
+                "group": "Automations",
+                "pages": [
+                  "openhands/usage/automations/overview",
+                  "openhands/usage/automations/creating-automations",
+                  "openhands/usage/automations/event-automations",
+                  "openhands/usage/automations/managing-automations"
+                ]
+              },
               {
                 "group": "Settings",
                 "pages": [
@@ -420,16 +429,6 @@
               "openhands/usage/cloud/organizations/roles-permissions",
               "openhands/usage/cloud/organizations/settings"
             ]
-          },
-          {
-            "group": "Automations (BETA)",
-            "icon": "clock",
-            "pages": [
-              "openhands/usage/automations/overview",
-              "openhands/usage/automations/creating-automations",
-              "openhands/usage/automations/event-automations",
-              "openhands/usage/automations/managing-automations"
-            ]
           }
         ]
       },

diff --git a/enterprise/enterprise-vs-oss.mdx b/enterprise/enterprise-vs-oss.mdx
@@ -4,53 +4,53 @@
 icon: scale-balanced
 ---
 
-This page describes the key differences between **OpenHands Local GUI** (open source) for individual developers and small teams running the Local GUI on their own machines, and **OpenHands Enterprise** for organizations that need advanced collaboration, integrations, and management capabilities.
+This page describes the key differences between **OpenHands Agent Canvas** (open source) for individual developers and small teams running the Agent Canvas on their own machines, and **OpenHands Enterprise** for organizations that need advanced collaboration, integrations, and management capabilities.
 
 ## Feature Comparison
 
-The table below highlights the key differences between the OpenHands Local GUI and OpenHands Enterprise offerings:
+The table below highlights the key differences between the OpenHands Agent Canvas and OpenHands Enterprise offerings:
 
-| Feature | Local GUI | OpenHands Enterprise |
+| Feature | Agent Canvas | OpenHands Enterprise |
 |---------|-------------------|----------------------|
 | **Full breadth of agent functionality (sub-agents, MCP, skills, model agnosticism)** | ✅ | ✅ |
-| **Where does the agent run?** | Local dev machines | Scalable, runtime sandboxes |
-| **Scalability** *Run multiple concurrent agent conversations* | Limited by machine | Unlimited, on-demand |
-| **'@OpenHands' in Slack and Jira** *Important for real-time resolution of bugs and feedback* | ❌ | ✅ |
-| **'@OpenHands' in GitHub, GitLab, Bitbucket** *Important for real-time resolution of PR comments and failing tests* | ❌ | ✅ |
-| **Multiple agent conversations in one place** *Give users visibility into all agent conversations* | ✅ | ✅ |
-| **Share conversations** *Unlock collaboration use cases* | ❌ | ✅ |
-| **Remote monitoring of agent conversations** *Enable Human-in-the-Loop operations for running agents* | ❌ Requires access to machine where agent is running | ✅ Monitor remotely from OpenHands Enterprise UI |
-| **Multi-user management and RBAC** *Roll out to several users and teams* | ❌ | ✅ |
-| **Automations** *Create scheduled and event-based workflows* | ❌ | ✅ |
+| **Where does the agent run?** | Locally or on a custom backend | Scalable, Kubernetes runtimes |
+| **Automations** <br /> *Create scheduled and event-based workflows* | ✅  | ✅ |
+| **'@OpenHands' in Slack and Jira** <br /> *Important for real-time resolution of bugs and feedback* | Requires custom [Automation](/openhands/usage/automations/overview) | Native integration |
+| **'@OpenHands' in GitHub, GitLab, Bitbucket** <br /> *Important for real-time resolution of PR comments and failing tests* | Requires custom [Automation](/openhands/usage/automations/overview) | Native integration |
+| **Share conversations** <br /> *Unlock collaboration use cases* | ❌ | ✅ |
+| **Multi-user Organizations and RBAC** <br /> *Roll out to several users and teams* | ❌ | ✅ |
+| **User and Organization Budgets** <br /> *Monitor and control costs* | ❌ | ✅ |
+| **Agent Observability Integrations** <br /> *Centralized logging of conversations* | ❌ | ✅ Uses Laminar|
+| **Private Plugin Marketplace** <br /> *Publish reusable plugins for teams to use* | ❌ | ✅ |
 | **SAML** | ❌ | ✅ |
 | **REST APIs** | ❌ | ✅ |
 
 ## When to Choose Each Option
 
-### OpenHands Local GUI
+### OpenHands Agent Canvas
 
-The OpenHands Local GUI is ideal for:
+The OpenHands Agent Canvas is ideal for:
 
 - Individual developers exploring AI-assisted coding
 - Small teams with basic requirements
 - Self-hosted environments where you manage your own infrastructure
-- Running OpenHands locally on your own machine
+- Running OpenHands locally on your own machine using the Agent Canvas
 
 ### OpenHands Enterprise
 
 OpenHands Enterprise is the right choice when you need:
 
-- **Team collaboration** — Share conversations and manage multiple users from a single platform
+- **Multi-use RBAC** — Manage multiple users from a single platform
 - **Platform integrations** — Invoke OpenHands directly from Slack, Jira, GitHub, GitLab, or Bitbucket
 - **Scalability** — Run unlimited parallel agent conversations without local resource constraints
 - **Enterprise security** — SAML authentication, RBAC, and centralized audit logs
-- **Remote monitoring** — Track agent progress in real-time from anywhere
+- **Usage Monitoring** — Track and enforce budgets; monitor usage across all users
 
 ## Getting Started
 
 <CardGroup cols={2}>
   <Card
-    title="Try Local GUI"
+    title="Try Agent Canvas"
     icon="desktop"
     href="/openhands/usage/run-openhands/local-setup#start-the-app"
   >

@@ -1,21 +1,17 @@
 ---
 title: Creating Automations
 description: Learn how to create scheduled automations using the Automation Skill.
 ---
 
-<Info>
-**Beta Feature**: Automations is currently in beta and available for **OpenHands Cloud** and **OpenHands Enterprise** users only.
-</Info>
-
 The easiest way to create an automation is to ask OpenHands directly. The Automation Skill handles all the details—you just describe what you want.
 
 ## Prompt vs Plugin Automations

 There are two types of automations:

 <Tabs>
  <Tab title="Prompt-based">
    Most automations are prompt-based. Just describe the task in natural language:

    ```
    Create an automation called "Daily Standup Summary" that runs every weekday 
@@ -81,7 +77,7 @@
 
 Tell the automation what to do with its output:
 
-- "Post to the #alerts Slack channel" (requires [Slack MCP](/openhands/usage/cloud/slack-installation))
+- "Post to the #alerts Slack channel" (requires [Slack MCP](/openhands/usage/settings/mcp-settings))
 - "Save to `reports/weekly-summary.md`"
 - "Create a GitHub issue with the findings" (automatic if you logged in with GitHub)
 - "Send a message via the configured notification service"
@@ -111,7 +107,7 @@
 - **Your secrets**: Access API keys stored in Settings > Secrets
 - **MCP integrations**: Use your configured MCP servers
 - **Network access**: Make HTTP requests, connect to APIs
-- **Git provider access**: Tokens from your Cloud login (GitHub, GitLab, or Bitbucket) are automatically included
+- **Git provider access**: Tokens from your login (GitHub, GitLab, or Bitbucket) are automatically included
 
 ## Schedules
 
@@ -124,10 +120,10 @@
 - "first day of each month"
 - "twice a day at 9 AM and 5 PM"

 The agent converts this to the appropriate cron schedule.

 <Tip>
 If you're familiar with cron expressions, you can specify them directly: "Run on cron schedule `0 9 * * 1-5`"
 </Tip>

 ## After Creation

@@ -1,13 +1,9 @@
 ---
 title: Event-Based Automations
 description: Trigger automations from GitHub events or custom webhooks instead of cron schedules.
 ---
 
-<Info>
-**Beta Feature**: Event-based automations are in beta for **OpenHands Cloud** and **OpenHands Enterprise** users.
-</Info>
-
 Event-based automations run when something happens—a PR is opened, an issue is commented on, or a webhook fires—instead of on a schedule. This is ideal for responsive workflows like auto-reviewing PRs, triaging issues, or reacting to external service events.
 
 ## Built-In vs. Custom Integrations

@@ -18,7 +14,7 @@

 ## GitHub Events (Built-In)

 GitHub is a built-in integration. Create automations that respond to GitHub events without any webhook setup.

 ### Example: Auto-Review PRs with a Specific Label

@@ -85,19 +81,21 @@

 ## Custom Webhooks

 For services beyond GitHub—like Linear, Stripe, or Slack—register a custom webhook first, then create automations that use it.

 <Note>
 **Two-phase workflow for custom webhooks:**

 1. **Webhook registration (one-time setup)**: You execute the curl command yourself to register the webhook. This keeps your signing secrets secure—the agent provides the command but never handles your credentials directly.

 2. **Automation creation (repeatable)**: Once the webhook is registered, the agent can create, update, and manage automations for that webhook source conversationally—no manual curl commands needed.
 </Note>
 
 ### Walkthrough: Linear Integration
 
-This example walks through setting up a Linear webhook to auto-triage new issues.
+<Note>
+This example walks through setting up a Linear webhook to auto-triage new issues using Automations in **[OpenHands Cloud](https://app.all-hands.dev)**.
+</Note>
 
 #### Step 1: Get Your Webhook Secret from Linear
 
@@ -138,7 +136,7 @@
 The response includes a `webhook_url` that you'll configure in Linear.

 <Accordion title="Understanding event_key_expr">
 The `event_key_expr` is a JMESPath expression that extracts the event type from incoming webhook payloads. This extracted value is what you match against in the automation's `on` field.

 For example, Linear sends payloads like:
 ```json
@@ -161,7 +159,7 @@

 #### Step 4: Create the Automation

 Now the webhook is registered, the agent can create automations for you end-to-end. Just describe what you want:

 ```
 Create an event-based automation called "Triage Linear Issues" that triggers
@@ -173,7 +171,7 @@

 The agent creates the automation with:
 - **Source**: `linear` (your registered webhook)
 - **Event**: `Issue` (Linear's event type)
 - **Filter**: `action == 'create'`

 ### Custom Webhook Parameters
@@ -184,7 +182,7 @@
 |-----------|----------|-------------|
 | `name` | Yes | Human-readable name |
 | `source` | Yes | Unique identifier (lowercase, alphanumeric with hyphens) |
 | `event_key_expr` | No | JMESPath to extract event type (default: `type`) |
 | `signature_header` | No | Header containing HMAC signature (default: `X-Signature-256`) |
 | `webhook_secret` | No | Signing secret—provide yours or let the system generate one |

@@ -197,13 +195,13 @@
 | Linear | `Linear-Signature` | `type` |
 | Stripe | `Stripe-Signature` | `type` |
 | Slack | `X-Slack-Signature` | `type` |
 | Twilio | `X-Twilio-Signature` | `type` |

 ---

 ## Next Steps

 New to automations? Start with the [Automations Overview](/openhands/usage/automations/overview) for the bigger picture, including cron-based scheduling and general concepts.

 - [Automations Overview](/openhands/usage/automations/overview) — Cron-based automations and general concepts
 - [Managing Automations](/openhands/usage/automations/managing-automations) — Update, disable, or delete automations
@@ -1,15 +1,11 @@
 ---
 title: Managing Automations
 description: List, update, enable, disable, and delete your automations.
 ---
 
-<Info>
-**Beta Feature**: Automations is currently in beta and available for **OpenHands Cloud** and **OpenHands Enterprise** users only.
-</Info>
-
 You can manage your automations by asking OpenHands directly—just like you created them.
 
 ## Viewing Your Automations

 ```
 List my automations
@@ -76,7 +72,7 @@
 - **Debug** if something went wrong

 <Tip>
 Automations are user-scoped, so all your automation runs appear alongside your regular conversations. Look for them in your conversations list after each scheduled run.
 </Tip>

 ### Run Statuses
@@ -86,7 +82,7 @@
 - **Completed**: Finished successfully
 - **Failed**: Something went wrong—check the run details

 ## Deleting Automations

 ```
 Delete the "Old Report" automation

@@ -1,29 +1,25 @@
 ---
 title: Automations Overview
-description: Create scheduled tasks that run automatically in OpenHands Cloud and Enterprise.
+description: Create scheduled tasks that run automatically in OpenHands.
 ---
 
-<Info>
-**Beta Feature**: Automations is currently in beta and available for **OpenHands Cloud** and **OpenHands Enterprise** users only.
-</Info>
-
 Automations let you schedule AI-powered tasks that run automatically—daily reports, health checks, data syncs, and more. Each automation runs a full OpenHands conversation on your chosen schedule, with access to your LLM settings, stored secrets, and integrations.
 
-Your git provider credentials are automatically available—if you logged into OpenHands Cloud with GitHub, GitLab, or Bitbucket, that access is included by default.
+Your git provider credentials are automatically available—if you logged into OpenHands with GitHub, GitLab, or Bitbucket, that access is included by default.
 
 ## What Can Automations Do?
 
 - **Generate reports**: Daily standups, weekly summaries, or monthly metrics
 - **Monitor systems**: Check API health, SSL certificates, or uptime
 - **Sync data**: Pull from external APIs, update spreadsheets, or refresh dashboards
 - **Maintain code**: Run dependency checks, security scans, or cleanup tasks
 - **Send notifications**: Post updates to Slack, create GitHub issues, or send alerts
 
 <Note>
-Automations can only interact with services you've configured access to. For example, posting to Slack requires the [Slack MCP integration](/openhands/usage/cloud/slack-installation). Git providers you logged in with (GitHub, GitLab, Bitbucket) are automatically available.
+Automations can only interact with services you've configured access to. For example, posting to Slack requires the [Slack MCP integration](/openhands/usage/settings/mcp-settings). Git providers you logged in with (GitHub, GitLab, Bitbucket) are automatically available.
 </Note>
 
 ## Two Types of Automations

 When you ask OpenHands to create an automation, you can choose between:

@@ -42,7 +38,7 @@
 our open GitHub issues, then posts the summary to #engineering on Slack.
 ```

 For plugin-based automations, mention the plugin:

 ```
 Create an automation using the code-review plugin that runs daily 
@@ -65,27 +61,16 @@
 3. The conversation is saved so you can review it later
 4. You can even continue the conversation if needed
 
 Automations are user-scoped—each automation and its runs belong to you. Conversations created by your automations automatically appear in your conversations list, just like any other conversation you start.
 
-Your automation has access to everything a normal OpenHands conversation does: terminal, file editing, your configured LLM, stored secrets, and MCP integrations. Git provider tokens from your Cloud login (GitHub, GitLab, or Bitbucket) are automatically included.
+Your automation has access to everything a normal OpenHands conversation does: terminal, file editing, your configured LLM, stored secrets, and MCP integrations. Git provider tokens from your login (GitHub, GitLab, or Bitbucket) are automatically included.
 
 ## Getting Started
 
-Before creating automations, complete this one-time setup:
-
-### 1. Create an OpenHands API Key
-
-Go to [Settings > API Keys](https://app.all-hands.dev/settings/api-keys) and create a new API key.
-
-### 2. Save the API Key as a Secret
-
-Copy the API key value and go to [Settings > Secrets](https://app.all-hands.dev/settings/secrets). Create a new secret with:
-- **Name**: `OPENHANDS_API_KEY`
-- **Value**: Your API key from step 1
+**Prerequisites**
 
-This allows the Automation Skill to create and manage automations on your behalf.
-
-### 3. Start a Conversation
+- **Configured LLM** in your settings
+- **Stored secrets** (optional) for any additional API keys your automations need (e.g., Slack tokens)
 
 Open a new conversation in OpenHands and ask it to create an automation:
 
@@ -94,17 +79,15 @@
 our open GitHub issues, then posts to #engineering on Slack.
 ```
 
-You can also list existing automations, enable/disable them, or trigger manual runs—all through conversation.
+Once you create an automation, you can view them by clicking on the "Automations" icon on the left-hand navigation.
+
+You can also ask OpenHands to list [existing automations, enable/disable them, or trigger manual runs](/openhands/usage/automations/managing-automations).
 
-## Prerequisites
 
-- **OpenHands Cloud or Enterprise account** (not available in open-source)
-- **Configured LLM** in your [settings](https://app.all-hands.dev/settings)
-- **Stored secrets** (optional) for any additional API keys your automations need (e.g., Slack tokens)
 
 ---
 
 ## Use Case Automations

 {/* BEGIN:use-case-automations — auto-generated from use-case frontmatter */}

@@ -267,5 +250,5 @@
 ## Next Steps

 - [Creating Automations](/openhands/usage/automations/creating-automations) — More details on writing prompts
 - [Managing Automations](/openhands/usage/automations/managing-automations) — Update, disable, or delete automations
 - [Use Cases Overview](/openhands/usage/use-cases/overview) — Explore the full use case guides behind these automations