BidirectionDocs
Open the console

My agent stopped answering

Almost always a domain that moved to another agent.

Work down this list. The first cause is by far the most common.

1. Someone attached your domain to a different agent#

A verified domain that no agent has claimed authorizes every agent in your workspace. Attaching it to one agent narrows it to that agent alone — and the agent that used to answer loses its permission silently.

Open Library · Domains and look at which agent holds the domain.

Two fixes:

  • Attach the domain to your agent as well — a domain can serve several agents.
  • Or add and verify a second domain for the other agent.

See Attach domains to agents.

2. The agent was unpublished#

Check the launch capsule on Agent & persona. It reads Live when the agent is published, and names the next step when it is not. Someone may have paused it.

See Go live, pause, unpublish.

3. The script stopped loading#

The Integration card on Agent & persona reports a real heartbeat. If it has gone quiet, the tag is no longer running on your pages — a deploy that dropped it, a consent banner now blocking it, or a change to the page template.

View source on the live page and look for the tag.

See Install the script.

4. It is on the wrong host#

The widget only answers on a verified domain. A staging host, a preview URL or a new subdomain is a different origin and needs its own claim.

Note that acme.com and www.acme.com count as one claim, but app.acme.com does not.

Still nothing#

Write to support with your workspace name, the agent's name, and the exact URL of a page where it should be answering. That URL is the thing we need most.