From 305a56620865875344a34f1b24d48b8154d226b7 Mon Sep 17 00:00:00 2001 From: openhands Date: Tue, 22 Sep 2026 16:35:10 +0000 Subject: [PATCH 1/2] docs: update documentation for OpenHands v1.22.0 release - Correct Git Sync cloud availability (org admin/owner access, member no-access state) - Document cloud MCP server health testing and stdio test unavailability - Clarify who can create automations on cloud backends - Add Agent Canvas 1.22.0 release notes page Co-authored-by: openhands --- docs.json | 1 + .../agent-canvas/customize-and-settings.mdx | 2 ++ openhands/usage/agent-canvas/git-sync.mdx | 6 ++-- .../agent-canvas/managing-automations.mdx | 2 ++ .../agent-canvas/release-notes/v1.22.0.mdx | 34 +++++++++++++++++++ 5 files changed, 42 insertions(+), 3 deletions(-) create mode 100644 openhands/usage/agent-canvas/release-notes/v1.22.0.mdx diff --git a/docs.json b/docs.json index f843dd076..0944f4f32 100644 --- a/docs.json +++ b/docs.json @@ -318,6 +318,7 @@ { "group": "Release Notes", "pages": [ + "openhands/usage/agent-canvas/release-notes/v1.22.0", "openhands/usage/agent-canvas/release-notes/v1.20.0", "openhands/usage/agent-canvas/release-notes/v1.19.0", "openhands/usage/agent-canvas/release-notes/v1.18.0", diff --git a/openhands/usage/agent-canvas/customize-and-settings.mdx b/openhands/usage/agent-canvas/customize-and-settings.mdx index 00cbedea4..2e3ea4e23 100644 --- a/openhands/usage/agent-canvas/customize-and-settings.mdx +++ b/openhands/usage/agent-canvas/customize-and-settings.mdx @@ -44,6 +44,8 @@ Installed MCP server cards check their connection and retain the resulting statu Server URLs and errors redact embedded secrets. Select **Update credentials** to edit a server; saving a corrected configuration refreshes its health status without reloading the page. +On a cloud backend, health checks work for remote (SSE and Streamable HTTP) servers, which are tested through the app server. The Test button is not offered for stdio servers on a cloud backend, because those servers start inside the conversation sandbox rather than on the backend that serves the settings page. Local backends can test both remote and stdio servers. + ## Settings The `Settings` area currently includes the following sections: diff --git a/openhands/usage/agent-canvas/git-sync.mdx b/openhands/usage/agent-canvas/git-sync.mdx index 17461d936..db8d9330b 100644 --- a/openhands/usage/agent-canvas/git-sync.mdx +++ b/openhands/usage/agent-canvas/git-sync.mdx @@ -34,11 +34,11 @@ The `automation.yaml` file stores the automation configuration. Files from an up Before configuring Git Sync, make sure you have: - A healthy Agent Canvas backend with a version of Automation Server that supports Git Sync -- Permission to manage automations on that backend +- Permission to manage automations on that backend. On a cloud backend, Git Sync is available to organization admins and owners - A Git repository and branch dedicated to the synchronized automation files - An HTTPS access token with read and write access when the repository is private -Git Sync is not available for cloud backends. If the page reports that the backend does not support Git Sync, [update Agent Canvas](/openhands/usage/agent-canvas/setup#update-agent-canvas) and restart it. +On a cloud backend, the Git Sync entry point follows organization admin/owner permissions. Organization members without that permission see a no-access state instead of the configuration form. On a local backend, Git Sync is available to anyone who can manage automations. If the page reports that the backend does not support Git Sync, [update Agent Canvas](/openhands/usage/agent-canvas/setup#update-agent-canvas) and restart it. ## Configure Git Sync @@ -100,7 +100,7 @@ Select `Sync now` to start a cycle immediately. The request schedules the cycle | Problem | What to Check | |---------|---------------| -| Git Sync is not available | Confirm the active backend is local, healthy, and running a current Automation Server version. | +| Git Sync is not available | Confirm the backend is healthy and running a current Automation Server version. On a cloud backend, confirm you are an organization admin or owner; members without that permission see a no-access state. | | Repository check fails | Confirm the HTTPS URL, branch name, network access, and token. Select save again only if you intentionally want to keep settings that the check cannot verify. | | Repository check passes but push fails | Give the access token write permission for repository contents and confirm branch protection permits the configured workflow. | | Sync reports a non-fast-forward or divergence error | Update the synchronized branch through reviewed pull requests and avoid another process writing directly to it while Agent Canvas has an unpushed commit. | diff --git a/openhands/usage/agent-canvas/managing-automations.mdx b/openhands/usage/agent-canvas/managing-automations.mdx index 2671d84ac..51d8a17ea 100644 --- a/openhands/usage/agent-canvas/managing-automations.mdx +++ b/openhands/usage/agent-canvas/managing-automations.mdx @@ -13,6 +13,8 @@ The **Automate** view in Agent Canvas is the in-app control center for your auto Open the **Automate** tab in the sidebar to see all automations on the active backend. Each row shows the automation name, trigger type, and enabled state. When the active backend is healthy but has no automations, the Automate pane remains available and includes an option to add one. +Creating an automation is governed by the same view permission as the list itself, so on cloud backends organization members who can view automations also see the add and import entry points. Editing or disabling an existing automation still requires manage permissions or being the automation's creator. + Click an automation to open its detail view. The detail view shows: - The full prompt the automation runs diff --git a/openhands/usage/agent-canvas/release-notes/v1.22.0.mdx b/openhands/usage/agent-canvas/release-notes/v1.22.0.mdx new file mode 100644 index 000000000..080965e26 --- /dev/null +++ b/openhands/usage/agent-canvas/release-notes/v1.22.0.mdx @@ -0,0 +1,34 @@ +--- +title: Agent Canvas 1.22.0 +description: Release notes for Agent Canvas version 1.22.0 +--- + +# Agent Canvas 1.22.0 + +Released September 22, 2026. + +[View the full release on GitHub](https://github.com/OpenHands/OpenHands/releases/tag/v1.22.0). + +## Highlights + +- **MCP server health on cloud backends** — Remote (SSE and Streamable HTTP) MCP servers can now be tested from the MCP settings page on a cloud backend, routed through the app server's `POST /api/v1/mcp/test` endpoint. stdio servers are still not tested on cloud backends because they start inside the conversation sandbox, so no Test button is offered for them. See [Check MCP Server Health](/openhands/usage/agent-canvas/customize-and-settings#check-mcp-server-health). +- **Git Sync for organization admins** — The Git Sync entry point now follows organization admin/owner permissions on cloud backends instead of being restricted to local backends. Organization members without permission see a no-access state. See [Sync Automations with Git](/openhands/usage/agent-canvas/git-sync). +- **Turkish UI translations** — Recently added user-facing strings are translated into Turkish. + +## Fixes + +- Organization members can now reach the add and import automation entry points on cloud backends; creating an automation follows view permission rather than manage permission. See [Managing Automations](/openhands/usage/agent-canvas/managing-automations). +- Links that leave the Canvas single-page app (cmd/ctrl+click, middle-click, copied links, toast links, and exported records) keep the Canvas base path instead of resolving to the enterprise app root. +- Saving a token-based MCP server against a cloud backend no longer drops sibling MCP servers from the saved configuration. +- Home-page automation rows link to the automation view instead of the automation's latest run conversation. +- Cloud organizations the server marks as not visible are hidden from the backend selector. + +## Maintenance + +- Released agent runtime dependencies bumped: SDK, Agent Server, and TypeScript client 1.49.4, Automation 1.14.0. +- Removed the obsolete `agent-client-protocol<0.11` constraint. + +## Full Changelog + +- [GitHub release notes](https://github.com/OpenHands/OpenHands/releases/tag/v1.22.0) +- [Compare v1.21.0 to v1.22.0](https://github.com/OpenHands/OpenHands/compare/v1.21.0...v1.22.0) From c19051f997bb38b489a71dfd41321ebc4ad1a32c Mon Sep 17 00:00:00 2001 From: Devin Date: Tue, 22 Sep 2026 19:15:01 -0400 Subject: [PATCH 2/2] Update permissions details for automations Removed cloud/ohe specific guidance. --- openhands/usage/agent-canvas/managing-automations.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/openhands/usage/agent-canvas/managing-automations.mdx b/openhands/usage/agent-canvas/managing-automations.mdx index 51d8a17ea..2671d84ac 100644 --- a/openhands/usage/agent-canvas/managing-automations.mdx +++ b/openhands/usage/agent-canvas/managing-automations.mdx @@ -13,8 +13,6 @@ The **Automate** view in Agent Canvas is the in-app control center for your auto Open the **Automate** tab in the sidebar to see all automations on the active backend. Each row shows the automation name, trigger type, and enabled state. When the active backend is healthy but has no automations, the Automate pane remains available and includes an option to add one. -Creating an automation is governed by the same view permission as the list itself, so on cloud backends organization members who can view automations also see the add and import entry points. Editing or disabling an existing automation still requires manage permissions or being the automation's creator. - Click an automation to open its detail view. The detail view shows: - The full prompt the automation runs