CLI
Status
Check Hookie relay connectivity and whether you are logged in
The status command pings the Hookie relay and reports whether a login token is stored. Use it when login succeeds but listen cannot connect, or when you want a quick health check.
Usage
hookie statusExample output (healthy)
Relay: OK (relay.hookie.sh)
RTT: 42ms
Auth: logged inIf you are not logged in, auth still reports clearly:
Relay: OK (relay.hookie.sh)
Auth: not logged inFailure modes
Relay unreachable
You will see a connection or ping error on stderr, plus the auth line. Confirm network access and that you are using an official build (or a correct HOOKIE_RELAY_URL for local CLI development).
Config load error
Auth may show as unknown if ~/.hookie (or HOOKIE_CONFIG_DIR) cannot be read. Fix permissions or set HOOKIE_CONFIG_DIR explicitly.
Related Commands
- Authentication —
login/logout - Listen — stream events after the relay is reachable
- Configuration — env vars including
HOOKIE_RELAY_URL