CLI

Install

The installer places the Shhhs CLI and MCP adapter on the local machine. Authenticated CLI access requires a scoped automation identity.

curl -fsSL https://shhhs.net/install.sh | bash

Authenticate

Create an automation identity in the web app after passkey authentication. The CLI validates the key before writing local config. Account-token login is disabled so the CLI cannot bypass passkey verification.

shhhs login --api-key <automation-identity-key>

Safe text entry

For sensitive text, let the CLI prompt for input instead of passing the secret as an argument.

shhhs push text
# The CLI opens a hidden prompt for the secret value.

Automation

For scripts and CI, use environment references, files, or secret-manager injection. Avoid command arguments that can appear in process lists, history, or logs.

• Prefer stdin or hidden prompt
• Avoid shell history
• Keep output redacted

Private Rooms from CLI

The CLI can create invite rooms, join invites, send encrypted room messages, read metadata, and close rooms with a scoped automation identity. Direct token-to-token rooms remain a web/PWA flow because that path uses passkey-verified account-token state.

shhhs chat create --label incident --ttl 3600 --json
shhhs chat join "$REDACTED_INVITE_URL" --json
printf '%s' "$TEMPORARY_CONTEXT" | shhhs chat send room_test --source stdin
shhhs chat read room_test --output json-metadata