CLI reference
Every stridee command, generated from the CLI's own definitions. stridee <command> --help prints the same text.
- Version
- 0.1.0
- Platforms
- macOS and Linux, Intel and ARM
- Auth
stridee loginregisters an Ed25519 key for this machine — the same kind the API signs with. How signing works.
Install
macOS and Linux, Intel and ARM. One static binary, checked against the published SHA256SUMS and installed to ~/.stridee/bin — never a sudo prompt. If that directory is not on your PATH, the installer prints the line to add. Set STRIDEE_INSTALL_DIR to put it somewhere else.
curl -fsSL https://download.stridee.com/install.sh | shThen sign this machine in and start forwarding deliveries:
stridee login
stridee listen --forward-to localhost:3000/webhooksstridee login
Sign this machine in by approving it in the console
Prints a code and opens the console. Approve it there — check the code matches your terminal — and this machine is signed in.
There is no token. The CLI generates an Ed25519 keypair, sends only the public half, and your approval registers that half as a signing key on your account, listed under Keys as Made by the Stridee CLI. The private half stays in ~/.config/stridee/config.json, readable only by you — treat it like an SSH key.
Usage
Options
| Option | Value | Description |
|---|---|---|
| --device-name | <NAME> | What the console calls this machine. Defaults to its hostname |
Examples
stridee login
stridee login --device-name ci-runnerstridee logout
Revoke this machine's key and sign out
Deletes the key stridee login registered and forgets it locally. If the revoke cannot reach Stridee, this machine is signed out anyway and the command names the key to delete under Keys in the console.
Usage
Examples
stridee logoutstridee whoami
Show which account this machine is signed in to
Prints the account, the key this machine signs with and the API it talks to.
Usage
Examples
stridee whoamistridee listen
Receive webhook deliveries and forward them to a local server
Opens a signed connection to Stridee and becomes one more webhook endpoint on your account for as long as it runs. Every event your account emits is POSTed to your local server exactly as production receives it: the same sealed envelope and the same webhook-id, webhook-timestamp and webhook-signature headers. No tunnel, and nothing on your machine is exposed.
The CLI never decrypts anything, so your handler's own verify and decrypt code is what runs. On first use it makes a webhook key for this machine and writes the private half as PKCS#8 PEM, the format the console downloads, to ~/.config/stridee/. Pass --key to seal to a key your handler already loads instead.
Each delivery prints one line once Stridee has judged your handler's answer. Decrypted means it returned 2xx with the delivery's nonce in the body, which only something holding the private key can do.
Your production endpoints keep receiving deliveries while you listen: the listener gets a copy.
Usage
Options
| Option | Value | Description |
|---|---|---|
| -f, --forward-toRequired | <URL> | Where to POST each delivery, e.g. |
| --key | <KEY_ID> | Seal deliveries to a webhook key you already hold instead of making one |
Examples
stridee listen --forward-to localhost:3000/webhooks
stridee listen -f localhost:3000/webhooks --key 5a8f31d6-0c94-4b27-a3e5-71fd2809bc4estridee trigger ping
Send a `ping` to every running `stridee listen` on your account
The same event the console's test button sends, delivered only to your listeners — never to production endpoints. Prints how each listener's handler answered.
Usage
Examples
# in one terminal
stridee listen --forward-to localhost:3000/webhooks
# in another
stridee trigger pingGlobal options
Accepted by every command.
| Option | Value | Description |
|---|---|---|
| --api-url | <API_URL> | The API to talk to. Leave it alone unless you run the API yourself Env: |
Something wrong or missing on this page? Tell us in Discord. Need something the API doesn’t do yet? Request it on the roadmap.