Reference · Error codes

HSX_E_NOT_LOGGED_IN

No HS-X session on this machine.

What this error means

A command tried to call the control plane without a stored bearer session.

When this error stops a command, hs-x exits with code 10. With --json, the failure is reported as a structured error whose code field is HSX_E_NOT_LOGGED_IN — stable to match on in scripts and agents.

Likely causes

  • hs-x login has not been run on this machine
  • Local session was cleared

How to fix it

  • Run hs-x login and paste an API token from the HS-X dashboard

Still stuck? Re-run the command with --debug for the wire-level detail, or hs-x doctor to check accounts, link state, and connectivity in one pass.

Keep going