Manage the daemon
hyp daemon <subcommand> [args...]Use hyp daemon --help to list service operations:
hyp daemon --helpDaemon commands don't activate plugins.
hyp daemon install
hyp daemon install [--config <path>] [--bin <path>] [--force] [--dry-run [--json] [--platform darwin|linux|win32]]Installs the persistent launchd or systemd user service, or on Windows the
per-user Scheduled Task. When invoked from an ephemeral npx path, it
installs a durable global package before it writes the service. --force
allows the existing CLI path if that global installation fails; removing that
directory later can break capture. --dry-run renders the exact service
definition without changing the host; add --json for structured plan output.
With --dry-run, --platform darwin, linux or win32 renders the plan
for that platform instead of this one.
On success it names the service it installed, such as
LaunchAgent: com.hyperparam.hypaware, systemd unit: hypaware.service or
Scheduled Task: \hypaware, then its target and the config path. The Windows
label names the task folder; the target line names the task itself,
\hypaware\<SID>. On macOS and Linux it also prints the service log path. On
Windows the task keeps no service log, so there is no logs line; it says
instead that Windows restarts a crashed daemon within about a minute. A Windows install also writes the
windowless launcher the task runs, daemon-launcher.vbs; --dry-run shows its
content after the task definition.
hyp daemon install --dry-run --jsonhyp daemon uninstall
hyp daemon uninstallWarning: This command stops persistent capture and detaches clients. Check
hyp status before you uninstall the daemon so you know which clients it
changes.
Removes the persistent service, then detaches every attached client so no
client points at a dead gateway. It keeps configuration, recordings, and logs.
The command doesn't ask for confirmation. If service removal succeeds but a
detach fails, the command returns 1 and prints the detach command needed to
finish.
hyp daemon uninstallhyp daemon run
hyp daemon run [--config <path>]Runs the daemon in the current terminal until it receives a stop signal.
daemon start starts the installed service.
When the daemon applies a new organization configuration or a plugin change,
it restarts as a new process to load the new code. An installed service
relaunches it automatically. A foreground run with no service manager (a
container, say) relaunches itself with the same arguments, environment and
output, up to 5 times in 10 minutes, waiting a little longer each time. Past
that it stops, prints the staged configuration it was applying, and exits with
code 75. A run under systemd or launchd, or started by a Node process manager
such as pm2, exits with 75 on every restart instead and leaves the relaunch to
it. To keep relaunching after the limit, run it again on 75. This loop does
that and exits with the daemon's own status otherwise, so a supervisor still
sees a failed start:
rc=75
while [ "$rc" -eq 75 ]; do hyp daemon run && rc=0 || rc=$?; done
exit "$rc"The first daemon start after hyp join or hyp remote login --no-daemon
usually takes this path, because that is when the organization configuration
arrives.
hyp daemon runhyp daemon start
hyp daemon startStarts the installed service. It returns 1 if no service is installed or the
service manager can't start it.
hyp daemon starthyp daemon status
hyp daemon status [--json]Reads the daemon status and process ID files without activating plugins. A
missing status file prints not started and returns 0. Malformed status or
read failures return 1.
hyp daemon status --jsonhyp daemon stop
hyp daemon stopSignals the running daemon and waits up to 10 seconds. An already stopped
daemon succeeds. A timeout returns 1.
On Windows, when the installed task's daemon is still running after those 10
seconds, stop force-ends the task and the daemon it launched instead of
returning 1. It prints a warning that the daemon was force-stopped and that
anything it had not saved yet may be lost.
hyp daemon stophyp daemon restart
hyp daemon restart [--processing]Restarts an installed service. If no service is installed, it stops a foreground daemon and tells you how to relaunch or install it.
On Windows the restart is graceful: it asks the daemon to exit cleanly, then runs the task again. It force-ends the task only when that request does not land.
--processing replaces only the supervised processing daemon (recording,
sinks, backfill and maintenance) and leaves the gateway listener, its sockets
and its in-flight streams alone. It asks the running gateway to bounce its
child and returns as soon as the request is written; the gateway allows the
child four seconds to stop before killing it. With no gateway supervising a
processing daemon it prints that and returns 1.
hyp daemon restart
hyp daemon restart --processing