docs(gateway): clarify portals PORT/PUBLIC_URL are agent-set

Opening a portal creates only the proxy listener; the agent sets PORT
and PUBLIC_URL in its own exec command, matching the portal tool
contract. Removes the implication of an automatic env handoff.
This commit is contained in:
Peter Steinberger
2026-08-12 17:31:49 -07:00
parent 283b58cbc8
commit d762bdefb4
+1 -1
View File
@@ -16,7 +16,7 @@ Ask the agent to open a portal:
- "Show me in a portal."
- "Start the app in a portal."
The agent opens a portal for the application's port, then starts the development server with a background `exec` call. OpenClaw passes the selected port as `PORT` and the portal's public base URL as `PUBLIC_URL`.
The agent opens a portal for the application's port, then starts the development server with a background `exec` call. Opening a portal only creates the proxy listener; it does not inject environment variables into your server. The agent sets `PORT` (the port it opened) and `PUBLIC_URL` (the portal's public base URL) in that `exec` command's own environment, so the app binds the expected port and generates correct absolute URLs.
## Declare development servers