npx -y @sharnix/agent@1.1.10
The problem
Foreground npx @sharnix/agent stops when the terminal closes. Linux users needed a current-user service without hand-editing systemd units — and agents needed clear guidance on what survives logout versus what still requires starting the dev server.
What we did
@sharnix/agent 1.1.10 ships a Linux systemd user service (sharnix service install/start), fixes unit generation for Ubuntu, and documents the two-layer model: Sharnix keeps the tunnel agent running; your dev server is still your responsibility.
What you can do now
On Linux, run npx @sharnix/agent@1.1.10 service install --port <port> in your app directory. After logout/login the Sharnix service auto-starts; start your dev server separately, then check service status and your preview URL.
View technical details
- Linux:
sharnix service install/start/stop/status/logsvia systemd user units in~/.config/systemd/user/. - Fixed systemd
WorkingDirectory=generation (unquoted paths — required on Ubuntu 22.04). - Service runs as the current user; reads the same
~/.sharnix/key.jsonand stable tunnel cache as foreground mode. - Duplicate-owner detection blocks foreground + service conflicts unless
--force. service status --jsonreports OS state, relay connection, tunnel ID, and log path.- Documented in
skill.md,llms.txt, and the background services blog post.