docs: update documentation for OpenHands v1.22.0

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.21.0",
               "openhands/usage/agent-canvas/release-notes/v1.20.0",
               "openhands/usage/agent-canvas/release-notes/v1.19.0",

openhands/usage/agent-canvas/customize-and-settings.mdx

@@ -44,6 +44,8 @@
 
 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:

openhands/usage/agent-canvas/git-sync.mdx

@@ -1,9 +1,9 @@
 ---
 title: Sync Automations with Git
 description: Back up, share, and edit Agent Canvas automations through a Git repository.
 ---
 
 Git Sync keeps the automations on an Agent Canvas backend synchronized with a Git repository. It gives you version history, an off-host backup, and a reviewable workflow for changing automations through pull requests.
 
 <Warning>
   Automation definitions can contain prompts, repository names, scripts, and other sensitive configuration. Use a private repository unless you are certain every synchronized file is safe to publish.
@@ -34,11 +34,11 @@
 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
 
@@ -63,7 +63,7 @@
 
 ## Encrypt Synchronized Files
 
 An encryption key encrypts each automation file before it is committed. The repository then contains ciphertext instead of readable YAML and script content.
 
 <Warning>
   Store the encryption key in a password manager or another secure location. Agent Canvas cannot read or restore encrypted automation files without the same key.
@@ -73,7 +73,7 @@
 
 The access token and encryption key entered in Agent Canvas are encrypted before the Automation Server stores them. Leaving either secret field blank keeps its current value. Use the corresponding clear option when you intend to remove a stored secret.
 
 ## Edit Automations Through Git
 
 Use a pull request when you want to review automation changes before Agent Canvas imports them:
 
@@ -87,7 +87,7 @@
 Git Sync validates imported automation fields. It skips an invalid automation directory and reports the problem in Automation Server logs rather than applying a partial configuration.
 
 <Note>
   If file encryption is enabled, edit automations in Agent Canvas instead. Encrypted repository files are not directly editable or reviewable.
 </Note>
 
 ## Pause or Run Sync Manually
@@ -100,10 +100,10 @@
 
 | 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. |
 | Encrypted files cannot be imported | Restore the exact encryption key used to write them. A different or missing key cannot decrypt the repository contents. |
 | Changes do not sync automatically | Confirm Git Sync is enabled and `Sync every (seconds)` is greater than `0`, or use `Sync now`. |
 

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)