You finally got the feature working. You drop the preview link in Slack, send it to a cofounder, or scan the QR on your phone. Then you close the laptop, restart the dev server, or run the agent again the next morning.
With most tunnel tools, that means a new URL — and another round of *"hey, use this link instead."*
Sharnix is built so you don't live in that loop.
One project, one preview link
When you share from a project folder, Sharnix remembers that project. Run the agent again from the same place and you get the same preview link — not a random new one.
That means:
- Client reviews — send the link on Monday. Still the right link on Friday.
- Phone testing — scan the QR once. Restart your app; the link you saved still works.
- AI-assisted builds — tell your agent *"share my app"* from the same repo; you're not minting a fresh URL every session.
Less time re-sending links. More time actually building.
The vibe-coder loop
This is the workflow Sharnix is meant for:
1. Build locally (often with an AI agent in the loop). 2. Share once — npx @sharnix/agent --port 3000 --share. 3. Get feedback on your phone or from a teammate. 4. Fix, refresh, repeat — same link.
No deploy step just to show progress. No explaining localhost to someone who just wants to tap a link and see the app.
When the preview goes quiet
If your local app or the Sharnix agent stops, visitors see a clear "preview paused" page — not a scary browser error. Start your dev server and agent again, and the same link comes back.
That's a feature, not a bug: the preview shows what's actually running on your machine right now.
Try it on your next build
cd my-app
npx @sharnix/agent --port 3000 --shareSend the link. Close the terminal. Open it again tomorrow from the same folder. Same URL.
Keep going
- Share a local app from your phone — the 60-second version
- Releases — what's new in the agent