Attach domains to agents
How attaching narrows authorization, the trap it sets, and how to detach.
This page explains the single most surprising rule in Bidirection. Read it before you attach anything.
The rule#
A domain on your list in Settings · Domains that no agent is attached to works for every agent in your workspace.
The moment you attach that domain to one agent, it becomes that agent's alone — other agents stop answering on it.
The trap#
On a workspace with one domain, attaching it to one agent can silently take another agent offline on your site. Nothing warns you at the moment of attaching, because attaching is a normal, correct thing to do.
If an agent suddenly stopped answering, this is the first thing to check. Open that agent's Deployment tab and read step 1: if it says your domains are attached to other agents, this is the cause. See My agent stopped answering.
Letting several agents answer on one site#
Attach the domain to each of them. A domain can serve multiple agents once you attach it deliberately. The rule is not "one agent per domain" — it is "attaching narrows, and narrowing is explicit".
Where to attach — and detach#
Open Agents, pick the agent, choose its Deployment tab, and look at step 1, Say where it may run (under Floating button or Your own button). Pick a domain from the list to attach it — the list reads Make a domain this agent's own… while the agent has none of its own, and Also answer on… once it has. That is the one place domains are attached, which is why you cannot attach from Settings · Domains itself.
The list offers every domain your workspace has added. To add a new one, follow Or add a new domain — it works there as soon as you add it. See Add your domain.
Step 1 also lists the domains attached to the agent, each with Detach. Before anything changes, Detach tells you what will happen:
- if other agents are attached to the domain, this agent stops answering there and they carry on;
- if no other agent is, the domain goes back to every agent in your workspace.
Why it works this way#
The domain check is an authorization boundary, not a preference. The server asks "may this agent answer on this site?" and the answer has to be unambiguous. Attached to no agent means "anyone in this workspace"; attached means "these agents, and nobody else".