A remote backend is an Agent Server endpoint that runs somewhere other than the Agent Canvas client. It uses the same Agent Server API as a local backend. The backend can run on another machine, on a VM, or in a separate container on the same machine.
Agent Canvas does not distinguish a remote backend by where it runs. It connects to the endpoint URL and displays the conversations, files, settings, and automations that backend provides.
What A Remote Backend Needs
A remote backend must provide:
- An accessible Agent Server URL.
- An API key when the backend requires authentication.
- A workspace or sandbox where Agent Server can execute tools.
To use scheduled or event-driven automations, the backend must also provide Automation Server.
Connect To A Remote Backend
- Start or obtain the URL for the Agent Server backend.
- In Agent Canvas, open the backend switcher and choose
Manage Backends.
- Select
Add Backend.
- Enter a display name, the Host / Base URL, and the API key when required.
- Save the backend and select it.
The selected backend becomes the execution environment for new conversations. Its workspace, settings, profiles, secrets, MCP servers, and automation state remain separate from other backends.
Anyone who can reach Agent Server with its API key can request agent execution in that backend’s workspace. Use TLS, access controls, and a high-entropy API key before exposing a backend outside a trusted network.
Deployment Examples
Next Steps
