Skip to content

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 ​

PackageUse it forRust API
bevy_agent_coreSchedules, actions, clock, RNG, observations, identities, checksumsdocs.rs
bevy_agent_snapshotRegistered gameplay state, snapshots, validation, restore, retentiondocs.rs
bevy_agent_replayInput logs, checkpoint indexes, recording, branch topologydocs.rs
bevy_agent_runnerAgentApp, plugin composition, stepping, navigation, capturedocs.rs
bevy_agent_remoteJSON-RPC, HTTP, WebSocket, stdio, capabilities, operation outcomesdocs.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:

sh
cargo install bevy_agent_cli --version 0.0.4 --locked

It 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.

GoalDirect dependencies
First countercore, snapshot, runner
Use replay/timeline types directlyAdd replay
Serve a separate clientAdd remote
Capture the primary windowEnable visual on runner/remote and install presentation plugins
Use the command-line client onlyInstall bevy_agent_cli

The platformer, Python client, agent skills, and repository documents are Git-distributed. They are not additional published Cargo packages.

Released under MIT or Apache-2.0.