Support

Last updated 20 September 2026

Steery carries a request from an agent to a person and a signed response back. This page covers setup, the failures people actually hit, and how to reach us.

Contact us

Email hello@steery.dev. We answer in English.

Include the command you ran, its exit code, the error text, and your operating system. Replace keys, tokens, and anything private with [redacted].

Your agent can file a report itself with steery bugs create. That works before setup has ever run, and the server refuses a report that still carries a credential.

Getting started

Setup is written for your coding agent, not for you: point it at steery.dev/install.md and let it run the whole thing. You tap three times:

1. Pick which harnesses to set up.
2. Confirm the sign-in in the browser tab it opens.
3. Confirm each signer fingerprint against your phone.

Steps 2 and 3 happen on first install only. You need the iPhone app before any of it can be approved: Steery on TestFlight.

The binary installs with curl -fsSL https://steery.dev/install.sh | sh, into ~/.local/bin/steery, never with sudo.

No phone enrolled, or no signer pinned

Only a signer signs, so a machine with no pinned signer cannot verify anything. The runtime refuses to start, exits 4, and prints this machine has pinned no signers on stderr and into run.log.

1. Install the iPhone app and sign in with the same account.
2. Run steery setup again; it prints each signer and its fingerprint.
3. Open Settings in the app and compare the 16-character fingerprint shown there.
4. Re-run setup with --trust <fingerprint> for each one that matches.

Compare the fingerprint yourself. A pin nobody compared is a pin against a list the server wrote, and it is the one step that protects you from us.

this machine pinned its signers for <other url> means an earlier install pinned against a different server. Every other command still works; steery setup … --trust replaces those pins.

Alerts are not arriving

Open Settings in the iPhone app. The Notifications row shows the current state and the button that fixes it:

• Enable notifications — iOS has not been asked yet.
• Open iOS Settings — permission was denied and only iOS can restore it.
• Retry notification setup — permission is granted but registration with Apple did not finish.

Still quiet, and the row says permission is granted? Check How loud in the same screen. Normal follows Focus and the Silent switch. Time-sensitive breaks through Focus, but silent stays silent. Critical sounds even on silent, and iOS can switch it off separately.

A missed alert loses nothing. The request waits in the app until it is answered or withdrawn, and alerts carry no request text.

An agent cannot reach Steery

A refused call authorizes nothing, and a correct agent stops rather than proceeding. Work through this in order:

1. Start a new session. A harness reads its MCP entry when a session starts, so sessions open before setup have no Steery.
2. Check the binary. If steery --version fails, ~/.local/bin is not on PATH.
3. Check the runtime. An empty World in the app means steery run is not running; a machine appears only once it has reported.
4. Read the reason. run.log in ~/.config/steery says why, and steery run in the foreground says the same and exits non-zero.
5. Put the service back with steery install if it was removed by Quit Steery.

Run steery setup --detect to see which harnesses this machine found and which are usable.

Other errors Steery reports

Every message names its own fix. None of them is a reason to work around Steery.

Accounts and data

Revoke machines under Machines, and phones and chat accounts under Signers, in the dashboard.

For a copy of your data or account deletion, email privacy@steery.dev.

Privacy and terms

Privacy Policy · Terms of Service