Steery connects your agent harness and your machines to your phone. Your agents ask, you
answer, and Steery sends the words. Steery's runtime (steery) uses a driver to reach
each harness and an adapter to reach each kind of machine. Drivers and adapters are small
programs. Each program speaks one protocol on its standard input and output. This repository
holds that protocol and the tools to write a program.
| PROTOCOL.md | The protocol: every message, shape, refusal word and bound. |
steery-sdk |
The Rust crate: the wire types, serve (a program's loop), the runtime's client, and the release manifest. |
| schema/protocol-v18.json | Every shape as JSON Schema. |
| examples/driver | The smallest driver. |
| examples/adapter | The smallest adapter that makes hosts. |
Steery's own programs use the same method. They are the most complete examples:
- steery-dev/drivers: omp, pi, Claude Code, Codex.
- steery-dev/adapters: macOS, Linux, and the adapters of the cloud vendors, for example Daytona.
Steery uses them exactly as it uses your programs.
- A program is one Rust executable for each target, with the name
steery-driver-<id>orsteery-adapter-<id>. The runtime does not build code. It runs what you publish. - A program states facts and does what the runtime asks. It does not speak to Steery's
server and does not hold a key. It changes only the items in a harness that its
setup/planlists. - All that a person sees of your program comes from its
initialize:label,short,tintandmark. No other part of Steery names it.
-
Copy examples/driver into your own repository. Name the SDK by git, not by path:
steery-sdk = { git = "https://github.com/steery-dev/sdk", tag = "v18.0.0" }
-
In
initialize, change the id, label and facts to those of your harness (PROTOCOL.md §3.1). -
Answer the methods of each level that you declare (§4):
observe:setup/plan,sessions/list,sessions/locate,sessions/read,mcp/list, and your hooks.drive: start and stop turns.live: reach a conversation that runs.
-
Test the driver after each change. Install Steery (
curl -fsSL https://steery.dev/install.sh | sh -s -- --install-only), then:cargo build --release steery programs test target/release/steery-driver-<id>
-
Use the driver on your own computer. You do not have to publish it:
steery programs add target/release/steery-driver-<id>
Use the same steps, but start from examples/adapter. An adapter that
makes hosts answers PROTOCOL.md §5.2 (hosts/list, hosts/ensure, start, stop,
delete, channel) through the API of your vendor. An adapter for an operating system
answers §5.1. To run the work of a computer in the hosts of your adapter, use:
steery programs add <your release>
steery setup --adapter <id> --setting YOUR_API_KEYA release is one manifest, steery-programs.json, with one .tar.gz for each program and
target (PROTOCOL.md §7.1). Build each target. Then let steery write the archives and the
manifest:
cargo zigbuild --release --target x86_64-unknown-linux-gnu.2.30 # runs in any made host
cargo build --release --target aarch64-apple-darwin
steery programs pack --release v0.1.0 --out dist \
x86_64-unknown-linux-gnu=target/x86_64-unknown-linux-gnu/release \
aarch64-apple-darwin=target/aarch64-apple-darwin/release
gh release create v0.1.0 dist/*Then any person can add each program of your latest release with this command. Steery also adds the new programs of each later release:
steery programs add https://github.com/<you>/<repo>The hosts that an adapter makes run a Linux build for x86_64-unknown-linux-gnu. Publish one.
Then your driver works in the hosts of Daytona and of every other cloud vendor.
Raise version in Cargo.toml in a pull request. Once it merges, run this from a clean
checkout of that commit of main:
./release.shIt tags the commit v<version> and pushes the tag. It records the release on Steery's
sdk-releases train: build as it starts, then shipped, or failed with the step that
stopped it. Steery's release-of-commit reads that train to say which release first carries a
commit. It needs steery signed in to the steery-dev workspace.
MIT.