Skip to main content
See Connections for how to configure one.

Naming one on a request

Required when the agent wires a customer patch with no connection pinned to it. Otherwise optional.

As embedded in a run

uuid
The connection used for this run.
string
Its name, unique within your workspace.
null when the run touched no customer endpoint.

MCP configuration

Two optional fields, set in the dashboard, that belong to the connection rather than to any agent:
string
Your login bridge. Present means published agents on this connection are reachable over MCP; absent means that door is shut for all of them.
string
Where we fetch this connection’s public keys. Blank falls back to your workspace key, which is what most integrations want.

Fixed for the life of a run

Once a run resolves a connection, that choice is locked. Resuming a paused run while naming a different connection is refused — a multi-turn conversation must not silently change which of your hosts it is talking to.

Errors