Superclaw Now Runs as a Real Daemon

The gateway is now a persistent background service instead of a fragile dev-tied process.

Big reliability jump this week.

Superclaw’s gateway now runs as a persistent daemon, not as a side effect of npm run dev. That means the control plane keeps running even when UI sessions restart, shells close, or local dev tooling crashes.

Why this matters:

  • Fewer false “offline” states when the app is fine but the dev process died.
  • Faster recovery after relaunch.
  • More realistic production behavior during daily use.

This came out of a few commits in sequence:

  • b1e339b (CLI + persistent gateway daemon)
  • 676741b (gateway lifecycle no longer tied to dev process)
  • a81d8a0 (kickstart daemon after launchctl load so it actually comes up)

Small on paper, huge in practice.