Skip to main content
These are the failures contributors hit most often. Each accordion title is the literal error or symptom, so you can search this page for what you see in your terminal.
aomi-run refuses to load a plugin whose pinned aomi-sdk does not match aomi-run’s own version. The loader gates on an exact match, so a plugin built against a different SDK never runs.
For a local run, pin the plugin’s aomi-sdk to the version your installed aomi-run reports in its boot banner (the (aomi-sdk X.Y.Z) on the first line at startup):
Cargo.toml
[dependencies]
aomi-sdk = "=X.Y.Z"   # match the version aomi-run prints at startup
When you go to ship, pin instead to the platform’s required_sdk_version (see platform.json in the platform repo) so CI and the backend accept the build. The community platform pins a specific version, such as =0.1.20, which can differ from whatever aomi-run you have installed.
Installing with --features cli alone builds only aomi-build and aomi-git. The cli feature does not include aomi-run.
Install with both features so the dev-runtime feature builds aomi-run:
cargo install --git https://github.com/aomi-labs/aomi-sdk --features cli,dev-runtime aomi-sdk
None of the three binaries (aomi-build, aomi-run, aomi-git) accept --version. Running it errors instead of printing a version.
Use --help to confirm an install and see the available commands:
aomi-git --help
aomi-build --help
aomi-run --help

​
Next

The CLI toolchain

The full reference for the three Rust binaries: aomi-build, aomi-run, and aomi-git.
Last modified on June 4, 2026