Public packages
The aion-cli crate is the public command release. Its packaged source is available without repository access. The feature list includes the optional JWT auth feature.
The aion_flow package provides the Gleam workflow SDK. HexDocs describes its published API. The Gleam reference here covers the current checkout’s API.
Main-only features
-
Main - Workspace 0.31.0; Rust edition 2024; minimum Rust 1.89; AGPL-3.0-only. The source revision is shown in this page’s version badge.
-
Public release - crates.io aion-cli 0.31.0, published 18 September 2026. Its source commit is ebd8ebcd83ac49da4ed04b77e308708cfe6cf0cc.
-
Main additions - Main code commit 969e23048495fefe650d2f6283097476e1063901 is 5,736 commits beyond the public crate’s source. Venues, worker connected, store migrate-package-rows and server.grpc_addresses require this newer main code.
-
CLI - The main command tree has 55 help surfaces. Use your installed command’s help to select its supported options.
-
AWL - The main language guide has 112 entries: 72 reserved and 40 positional words.
-
MCP - 14 public workflow tools and 3 assistant conversation tools. Their schemas are in the MCP reference.
The public CLI source uses the singular gRPC listener setting. Main uses the plural listener list. Use the config generated by your installed binary.
Venues and their role bindings, the connected-worker command and the package-row migration command belong to the newer main build. They require repository access until a package containing them is published.
Python and TypeScript SDK installation in these pages uses local paths in an authorized checkout. Their package names identify the SDKs; the local paths provide the code used by these examples.
Updating
The update command chooses the latest stable Cargo registry release when no version is supplied. Its installation step runs Cargo against that registry. It targets the published code, including when that code predates a main build.
The updater compares package version strings. Matching strings can produce an already-current result even when source commits differ. Retain the build commit and executable hash as well as the version.
For main installations, build the selected authorized checkout and follow the upgrade procedure. For a registry installation, choose the published version deliberately and retain a store backup.