Most preview tools make you configure tunnels, copy tokens, and explain ports to clients. Sharnix is built around a simpler loop:
1. Start your local dev server. 2. Run the agent. 3. Send the link.
The one-liner
npx @sharnix/agent --port 3000 --shareWhen the tunnel connects, the CLI prints a public HTTPS URL and a compact QR code. Scan it on your phone — you are looking at your local app through the relay, not a screenshot or a deploy.
Multi-port apps
If your project has a frontend and API on different ports, add a .sharnix.yaml manifest. Sharnix discovers it automatically and routes /api/* to your backend and / to your frontend.
The visitor still opens one URL. They do not need to know anything about localhost.
Why this matters for AI-assisted development
When you tell an agent *"share my app"*, it should not have to invent a tunnel workflow from scratch. Sharnix ships skill.md and llms.txt so agents know the exact commands, manifest rules, and permission model.
Stable tunnel IDs per project directory mean the same link works across restarts — useful when you are iterating with a client or tester over several days.
Next step: background mode
Foreground sharing is live today on macOS, Windows, and Linux. Background services (sharnix service install) are rolling out so the tunnel can survive terminal closes without changing the share link model.
See the releases page for the latest agent changes.