You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bots made with "Run it here" can't run when the managed agent is on loopback ("will not dial") #888
A Bot created in the app with no endpoint ("Run it here") is bound to the deployment's managed agent, MANAGED_AGENT_AG_UI_URL. When that address is on loopback, as in a local deployment where the managed agent runs on the same machine (http://127.0.0.1:<port>/ag-ui), every message to the new Bot fails at once:
This deployment will not dial http://127.0.0.1:41706/ag-ui: that address is inside OpenBot's own network, so an agent may not live there.
The guard (server/src/agents/endpoint.ts) is right for addresses a person types in, but this address is the deployment's own setting, not user input. Built-in Bots from the tenant package are unaffected, so the failure shows only for Bots made in the app.
Workarounds
Set AGENT_ENDPOINT_ALLOWED_HOSTS=127.0.0.1:<port>.
Or define the Bot in the tenant package as type: built-in.
Suggested fix
Trust the configured managed agent address implicitly: add the host and port of MANAGED_AGENT_AG_UI_URL (and any other deployment-configured agent URL) to the allowed hosts the endpoint check consults, so that only addresses entered by people go through the private-network refusal.
Activity
linear-code commentedon Oct 29, 2026
FOR-351
Trust the deployment's own agent at exactly its configured URLs