Summary
Agents and operators using hey often need to answer: “which HEY OAuth installs/sessions are active for this identity?” Today the CLI only exposes this machine’s login (hey auth status) and linked mailboxes (hey account list). There is no command to list remote sessions (browsers, phones, other CLI installs).
Motivation
- Security / audit: confirm what is still logged in after rotating devices or sharing a box.
- Multi-agent setups: several machines may hold
hey-cli credentials; operators want a single place to see installs without opening the web UI.
- Today
hey auth status --json returns useful local fields (install_id, expires_at, storage, etc.) but nothing about peer sessions.
Proposal
Add something like:
hey auth sessions --json
# or
hey sessions list --json
Ideal fields per session (whatever the API already exposes):
- install / session id
- device or client label (CLI vs web vs mobile if known)
- created / last used
- current token expiry (or “active”)
- whether this is the calling install
Optional follow-ups (separate issues are fine):
hey auth sessions revoke <id> for remote logout
- mark / filter CLI installs vs browser
Current workaround
Use the HEY web account UI for device/session management; use hey auth status / hey doctor only for the local install.
Environment
- hey-cli 1.6.x on a headless Linux agent box
- Auth via OAuth; credentials file storage when keyring unavailable
Thanks!
Summary
Agents and operators using
heyoften need to answer: “which HEY OAuth installs/sessions are active for this identity?” Today the CLI only exposes this machine’s login (hey auth status) and linked mailboxes (hey account list). There is no command to list remote sessions (browsers, phones, other CLI installs).Motivation
hey-clicredentials; operators want a single place to see installs without opening the web UI.hey auth status --jsonreturns useful local fields (install_id,expires_at,storage, etc.) but nothing about peer sessions.Proposal
Add something like:
hey auth sessions --json # or hey sessions list --jsonIdeal fields per session (whatever the API already exposes):
Optional follow-ups (separate issues are fine):
hey auth sessions revoke <id>for remote logoutCurrent workaround
Use the HEY web account UI for device/session management; use
hey auth status/hey doctoronly for the local install.Environment
Thanks!