Choose your crates
There are five runtime crates and one independent command-line client. Start with core, snapshot, and runner for a headless environment. Add remote when another process needs to control it.
Runtime packages
| Package | Use it for | Rust API |
|---|---|---|
| bevy_agent_core | Schedules, actions, clock, RNG, observations, identities, checksums | docs.rs |
| bevy_agent_snapshot | Registered gameplay state, snapshots, validation, restore, retention | docs.rs |
| bevy_agent_replay | Input logs, checkpoint indexes, recording, branch topology | docs.rs |
| bevy_agent_runner | AgentApp, plugin composition, stepping, navigation, capture | docs.rs |
| bevy_agent_remote | JSON-RPC, HTTP, WebSocket, stdio, capabilities, operation outcomes | docs.rs |
All runtime packages target Bevy 0.18.1 and Rust 1.91+. They are experimental; pin matching exact versions. docs.rs API availability depends on its build processing; these guides are published independently.
The CLI
bevy_agent_cli on crates.io installs the agentctl executable:
cargo install bevy_agent_cli --version 0.0.4 --lockedIt does not link the simulation runtime or include a game. It sends JSON-RPC requests to a running environment. HTTP and the CLI shows a complete server/client workflow.
Feature selection
Runtime defaults are headless. AgentControlPlugins::default() composes core, snapshots, and replay. The runner and remote visual features add render/window capture support; your game chooses its rendering plugins.
| Goal | Direct dependencies |
|---|---|
| First counter | core, snapshot, runner |
| Use replay/timeline types directly | Add replay |
| Serve a separate client | Add remote |
| Capture the primary window | Enable visual on runner/remote and install presentation plugins |
| Use the command-line client only | Install bevy_agent_cli |
The platformer, Python client, agent skills, and repository documents are Git-distributed. They are not additional published Cargo packages.