#expose pub url to a webserver runninf inside Oz agent
5 messages · Page 1 of 1 (latest)
Hi @final kestrel. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
I’m sorry, but the knowledge sources don’t mention any built‑in way to expose a public URL or HTTP tunnel directly from an Oz cloud agent container.
From the docs and blog posts, Oz focuses on:
- Orchestrating and tracking agents (runs, environments, schedules, session sharing) [How Oz works; Oz web app].
- Providing observability and collaboration via session sharing links (for viewing commands, logs, artifacts, etc.), not for exposing arbitrary web servers running inside the environment [Cloud agent session sharing].
- Managing environments as Docker images + repos + setup commands, but without any mention of HTTP ingress or public preview URLs [Environments page].
There’s no reference to:
- Built‑in port forwarding from an agent container to the public internet.
- Automatic preview URLs.
- Integrated tunneling (ngrok/grok‑style) for web servers started inside an agent.
So, based on the available docs, it appears you would need to set up your own tunneling or hosting mechanism (e.g., via your own infra or a separate tunnel tool) if you want to hit that web server from your browser.
If Warp/Oz adds a feature like public preview URLs in the future, it should show up in the changelog or Oz docs, so keeping an eye there would be the best way to know when/if this becomes available out of the box [Changelog; Oz Platform].
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
@final kestrel Kapa.ai is still learning and improving, please let me know how I did by reacting below.