Skip to content

docs(user): the outside agents guide says which addresses agents can sign in over #22377

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
t3dotgg merged 1 commit into from
Oct 21, 2026
Merged

docs(user): the outside agents guide says which addresses agents can sign in over #22377

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions docs/user/outside-agents.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,13 @@ https://<environment-address>/mcp
The copied URL uses the route this device is connected over, so an agent on the
same device can reach it.

- **An agent on your own computers** can use any address that computer reaches
the environment at: a LAN or Tailscale address, T3 Connect, or `localhost` on
the host. See [remote access](./remote-access.md).
- **An agent on your own computers** can use `localhost` on the host, T3
Connect, or any `https` address, such as
[Tailscale HTTPS](./remote-access.md#tailscale-https). Signing in sends the
agent's credentials to the environment, and agents only do that over `https`
or to `localhost`. A plain-`http` LAN or Tailscale address, like
`http://100.x.y.z:3773`, lets an agent find the environment but not finish
signing in.
- **A hosted agent**, such as ChatGPT or a bot running in the cloud, must reach
the environment from the internet. Use the T3 Connect address. A Tailscale
address only works from your own tailnet.
Expand Down
Loading