Connect to or leave HypAware Cloud
hyp join
hyp join <url> [token] [--token-file <path>] [--bin <path>] [--no-daemon] [--force]Validates the URL syntax and requires a nonempty token, writes a
permission-restricted central seed layer, and installs or restarts the daemon.
It does not authenticate with the server. Authentication and the full organization
configuration arrive when the daemon connects. Local configuration and history remain.
--no-daemon writes only the seed. Start hyp daemon run under your own
supervisor that relaunches it on exit code 75 (see hyp daemon run), or install the service separately where a service manager exists. --force allows the existing CLI path if global
installation fails.
hyp join https://api.hypaware.ai --token-file ./enrollment-tokenPrefer --token-file or standard input. A positional token can appear in shell
history and process listings.
hyp leave
hyp leaveRemoves the central layer, identity, and sync credential, restarts the
daemon, and reverses organization-driven client attaches. It keeps the local
configuration, daemon service, recordings, and remote query sign-ins. Use
hyp remote remove <name> to remove a query target and its stored sign-in
separately. Partial failure
returns 1 and prints repair commands.
hyp leave