Stridee
Stridee Platform Docs

CLI reference

Every stridee command, generated from the CLI's own definitions. stridee <command> --help prints the same text.

Version
0.3.0
Platforms
macOS and Linux, Intel and ARM
Auth
stridee login registers an Ed25519 key for this machine — the same kind the API signs with. How signing works.

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.

Then sign this machine in and start forwarding deliveries.

Install
curl -fsSL https://download.stridee.com/install.sh | sh
Then
stridee login
stridee listen --forward-to localhost:3000/webhooks

stridee 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.

Options

--device-name<NAME>

What the console calls this machine. Defaults to its hostname

Usage
stridee login [OPTIONS]
Examples
stridee login
stridee login --device-name ci-runner

stridee 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
stridee logout
Examples
stridee logout

stridee whoami

Show which account this machine is signed in to

Prints the account and the key this machine signs with.

Usage
stridee whoami
Examples
stridee whoami

stridee 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.

Options

-f, --forward-to<URL>Required

Where to POST each delivery, e.g. localhost:3000/webhooks

--key<KEY_ID>

Seal deliveries to a webhook key you already hold instead of making one

Usage
stridee listen [OPTIONS] --forward-to <URL>
Examples
stridee listen --forward-to localhost:3000/webhooks
stridee listen -f localhost:3000/webhooks --key 5a8f31d6-0c94-4b27-a3e5-71fd2809bc4e

stridee 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
stridee trigger ping
Examples
# in one terminal
stridee listen --forward-to localhost:3000/webhooks
# in another
stridee trigger ping

stridee community

Chat with other developers and the Stridee team on Discord

Prints the link and, in a terminal, opens it in your browser when you press Enter. The place to get unstuck: a delivery that won't decrypt, an error you can't place, a page of the docs that's wrong.

Usage
stridee community
Examples
stridee community

stridee feedback

Request features and vote on the Stridee platform's roadmap

Prints the link to the platform's public feedback board and, in a terminal, opens it in your browser when you press Enter. The place for anything the API, the console or the CLI doesn't do yet.

Usage
stridee feedback
Examples
stridee feedback

stridee update

Update the CLI to the latest release

Downloads the latest build for this machine from download.stridee.com, checks it against the published SHA256SUMS, and replaces this binary with it. Pass --version to install a specific release instead, including an older one.

Other commands check for a newer release about once a day and say so when they finish; they never install anything. Set STRIDEE_NO_UPDATE_CHECK=1 to stop the check. A stridee built with cargo is updated with cargo.

Options

--version<VERSION>

The release to install instead of the latest, e.g. 0.2.0

Usage
stridee update
Examples
stridee update
stridee update --version 0.2.0

Something wrong or missing on this page? Tell us in Discord. Need something the API doesn’t do yet? Request it on the roadmap.