Agent Canvas ships with a set of pre-built automations for the most common agent workflows. Each one is a ready-to-use starting point — pick the one that fits your use case, connect it to the right backend, and you can have an automation running in minutes.Documentation Index
Fetch the complete documentation index at: https://allhandsai-docs-onboarding-agent-canvas.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Available Pre-built Automations
| Automation | What It Does |
|---|---|
| GitHub PR Review Assistant | Automatically reviews pull requests and posts feedback as a comment |
| GitHub Repository Monitor | Watches a repository for events and triggers agent actions in response |
| Slack Channel Monitor | Listens to a Slack channel and triggers an agent when a message matches a pattern |
Agent Canvas can work with the OpenHands automation backend so you can run agents on a schedule or in response to external events.
What You Can Do
In theAutomate view, you can:
- Browse existing automations
- Inspect automation configuration and activity
- Enable or disable automations
- Work with recommended automation flows
How Creation Flows Usually Start
TheAutomations view is mainly for browsing and managing automations that already exist.
In practice, new automation setup often starts in one of two ways:
- From a conversation, where you ask OpenHands to create an automation for you
- From a recommended automation flow in the
Automationsview
Local Stack Behavior
When you start Agent Canvas with theagent-canvas command, the local stack includes the automation backend by default.
That makes the built-in local setup a good starting point for:
- Scheduled maintenance tasks
- Event-driven coding workflows
- Testing automation ideas before deploying them elsewhere
Backend Availability Matters
TheAutomations view depends on the active backend.
- If the active backend has a healthy automation service, Agent Canvas can load and manage automations.
- If it does not, Agent Canvas shows a backend-not-configured or unavailable state.
Some automation editing flows are currently focused on local backends first, while the broader hosted experience continues to evolve.

