Skip to main content

Documentation Index

Fetch the complete documentation index at: https://allhandsai-docs-agent-canvas-docs.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Agent Canvas always works against an active backend. Conversations, backend-synced settings, and some feature availability depend on which backend is currently selected.

​
Default Local Backend

On first launch, Agent Canvas seeds a default local backend that points to the stack started by the agent-canvas command. That default backend is a good fit when you want to:
  • Run OpenHands entirely on your current machine
  • Test configuration changes quickly
  • Use the bundled automation backend locally

​
Managing Additional Backends

Use the backend switcher in the UI to open Manage Backends, then add or edit backend entries. Each backend entry stores:
  • A display name
  • A host or base URL
  • An API key when the backend requires one
Agent Canvas also tracks whether a backend is local or cloud so it can adjust the available flows.

​
Local vs. Cloud Backends

Backend TypeTypical Use
LocalA machine you control directly, such as your laptop, a VM, or a team-managed host
CloudA compatible backend running an agent-server or OpenHands Cloud

​
What Changes When You Switch Backends

Switching the active backend changes more than just where conversations run.
  • Settings read and write against the active backend
  • LLM availability depends on what that backend exposes
  • Customize > MCP Servers acts on the active backend’s MCP configuration
  • Automations depend on whether the active backend has the automation service available
If a backend is unreachable, Agent Canvas can still open the backend management flow so you can fix the host, API key, or selection without leaving the app.
A common setup is to keep one local backend for experimentation and add one or more remote backends for longer-running or more powerful workloads. Examples:
  • A laptop backend for quick local tasks
  • A dedicated VM backend for always-on work
  • A cloud backend for hosted conversations