From 2f8ee203e10fa9b249bf403fd14bc049463e62a7 Mon Sep 17 00:00:00 2001 From: Devin Date: Wed, 3 Jun 2026 11:13:49 -0400 Subject: [PATCH 1/2] Remove extra step about saving your secrets and replace with toggle guidance --- .../agent-canvas/prebuilt/github-pr-review.mdx | 14 ++------------ .../agent-canvas/prebuilt/github-repo-monitor.mdx | 14 ++------------ .../prebuilt/slack-channel-monitor.mdx | 14 ++------------ 3 files changed, 6 insertions(+), 36 deletions(-) diff --git a/openhands/usage/agent-canvas/prebuilt/github-pr-review.mdx b/openhands/usage/agent-canvas/prebuilt/github-pr-review.mdx index 1965e65e..6fc6e503 100644 --- a/openhands/usage/agent-canvas/prebuilt/github-pr-review.mdx +++ b/openhands/usage/agent-canvas/prebuilt/github-pr-review.mdx @@ -63,18 +63,8 @@ The GitHub MCP server gives the agent tools for reading repositories, inspecting 4. Open `MCP Servers`. 5. Select `GitHub` from the MCP library. 6. Paste the GitHub token you created earlier. -7. Save the MCP server configuration. - -## Add the GitHub Token as a Secret - -Some automations also need the token available as a backend secret, especially when the agent runs GitHub commands or accesses private repositories. - -1. Open `Settings`. -2. Open `Secrets`. -3. Click `Add a new Secret`. -4. Set the secret name to `GITHUB_TOKEN`. -5. Paste the GitHub token as the secret value. -6. Save the secret. +7. Make sure the secret-creation toggle is on so Agent Canvas creates the token secret automatically when you save the MCP server configuration. +8. Save the MCP server configuration. ## Start the PR Review Workflow diff --git a/openhands/usage/agent-canvas/prebuilt/github-repo-monitor.mdx b/openhands/usage/agent-canvas/prebuilt/github-repo-monitor.mdx index f83f5f7c..ab9602ad 100644 --- a/openhands/usage/agent-canvas/prebuilt/github-repo-monitor.mdx +++ b/openhands/usage/agent-canvas/prebuilt/github-repo-monitor.mdx @@ -65,18 +65,8 @@ The GitHub MCP server gives the agent tools for reading repository state and tak 4. Open `MCP Servers`. 5. Select `GitHub` from the MCP library. 6. Paste the GitHub token you created earlier. -7. Save the MCP server configuration. - -## Add the GitHub Token as a Secret - -Some automations also need the token available as a backend secret, especially when the agent runs GitHub commands or accesses private repositories. - -1. Open `Settings`. -2. Open `Secrets`. -3. Click `Add a new Secret`. -4. Set the secret name to `GITHUB_TOKEN`. -5. Paste the GitHub token as the secret value. -6. Save the secret. +7. Make sure the secret-creation toggle is on so Agent Canvas creates the token secret automatically when you save the MCP server configuration. +8. Save the MCP server configuration. ## Start the Repository Monitor Workflow diff --git a/openhands/usage/agent-canvas/prebuilt/slack-channel-monitor.mdx b/openhands/usage/agent-canvas/prebuilt/slack-channel-monitor.mdx index f4322e0b..7952d7a3 100644 --- a/openhands/usage/agent-canvas/prebuilt/slack-channel-monitor.mdx +++ b/openhands/usage/agent-canvas/prebuilt/slack-channel-monitor.mdx @@ -90,18 +90,8 @@ The Slack MCP server gives the agent tools for reading Slack channel activity an 5. Select `Slack` from the MCP library. 6. Paste the bot token. 7. Enter your Slack workspace ID. -8. Save the MCP server configuration. - -## Add the Slack Bot Token as a Secret - -Some automations also need the token available as a backend secret. - -1. Open `Settings`. -2. Open `Secrets`. -3. Click `Add a new Secret`. -4. Set the secret name to `SLACK_BOT_TOKEN`. -5. Paste the bot token as the secret value. -6. Save the secret. +8. Make sure the secret-creation toggle is on so Agent Canvas creates the bot token secret automatically when you save the MCP server configuration. +9. Save the MCP server configuration. ## Start the Slack Channel Monitor Workflow From 2156bfd57964b3625ed40846a5e13f331a21f553 Mon Sep 17 00:00:00 2001 From: Devin Date: Wed, 3 Jun 2026 11:25:00 -0400 Subject: [PATCH 2/2] Tweak the wording in slack channel monitor --- .../usage/agent-canvas/prebuilt/slack-channel-monitor.mdx | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/openhands/usage/agent-canvas/prebuilt/slack-channel-monitor.mdx b/openhands/usage/agent-canvas/prebuilt/slack-channel-monitor.mdx index 7952d7a3..b711a196 100644 --- a/openhands/usage/agent-canvas/prebuilt/slack-channel-monitor.mdx +++ b/openhands/usage/agent-canvas/prebuilt/slack-channel-monitor.mdx @@ -113,9 +113,15 @@ You do not need to know every detail before sending the prefilled prompt. The ag - Whether the agent should reply in Slack - Any GitHub repository or external service the agent should use + + + If you want the automation to watch for `@your-bot-name`, tell the agent to watch for Slack bot mentions as well as the trigger phrases you set. That way, it can respond when someone mentions the bot directly, not just when a specific keyword appears. + + You can edit the prefilled prompt before sending it if you want to provide any of those details up front. -For example, you can ask the monitor to watch an alerts channel, summarize new incidents, and create a GitHub issue when a message includes a production error. +For example, you can ask the tell the agent to configure the automation to watch an #alerts channel, summarize new incidents, and create a GitHub issue when a message includes a production error. + ## Verify the Automation