AI Agents and Asyx: Publish What Your Assistant Built
Coding assistants—Cursor, Claude Code, GitHub Copilot, Windsurf, and others—excel at generating apps that run on localhost. Stakeholders cannot see that work until you give them a public URL. Asyx closes that gap: one terminal command turns localhost:3000 into https://yourname.tunnel.asyx.ai.
The workflow
Agent writes code → you run the dev server → asyx tunnel → share HTTPS link
The agent does not need Asyx credentials. It needs a clear instruction to start your app and tell you which port to tunnel—or to run the tunnel command in the integrated terminal after enrollment.
Roles: human vs agent
| Step | Who | Action |
|---|---|---|
| Account + device enroll | Human (once) | asyx setup at asyx.ai/register |
| Build / edit code | Agent | Writes or runs project locally |
| Start dev server | Agent or human | npm run dev, etc. |
| Open public URL | Human or agent (terminal) | asyx tunnel --http --port 3000 |
| Share link | Human | Send URL to reviewer or client |
Enrollment is intentionally human-gated so random prompts cannot open tunnels from an unbound machine.
Agent instructions (copy into your prompt)
After the dev server is running on port PORT:
1. Run: asyx tunnel --http --port PORT
2. Report the printed https://*.tunnel.asyx.ai URL as the public demo link.
3. Do not commit certificates or ~/.asyx/ contents to git.
Prerequisite: asyx setup has been completed on this machine.
Replace PORT with the actual port (e.g. 3000).
Example: demo after a feature branch
- Ask your agent to implement a UI change and run
npm run dev. - In the project terminal (or a second one):
asyx tunnel --http --port 3000
- Paste the tunnel URL in a PR comment, Slack message, or email: “Live preview (while my machine is on).”
Private demos with Quickpass
Public tunnels are fine for open previews. For client-only or team-only access, add a security group:
asyx tunnel --http --port 3000 --secgroup reviewers
Members enroll via Quickpass. See Quickpass.
Safety notes for agent workflows
- Never paste device certificates or private keys into chat or git.
- Do not tunnel database admin ports without authentication.
- Stop the tunnel when the demo ends (
Ctrl+C). - Treat the public URL like a temporary staging link—not a production deploy.
What agents cannot do (by design)
- Enroll a new device without browser verification
- Open tunnels from a machine that has not run
asyx setup - Bypass Quickpass membership on protected tunnels
Related guides
- Cursor + Asyx — Cursor-specific workflow
- Agent Checklist — copy-paste steps for any terminal agent
- Local LLM / Ollama — expose a model API publicly
- Publish in 60 Seconds — fastest path to a public link
- Expose localhost — concepts and FAQ
- Expose Web + API — when the agent built both frontend and API
FAQ
Can the agent run asyx tunnel itself?
Yes, if your IDE gives the agent shell access and asyx is installed. Many teams prefer the human run the tunnel command for visibility.
Does this work with local LLMs (Ollama)?
Yes—tunnel the HTTP port your LLM UI or API uses. See Local LLM / Ollama.
Will the URL work when my laptop sleeps?
No. The tunnel is active while the CLI runs and your machine is awake and online.