everruns-runtime 0.17.26

Deprecated 0.17.x compatibility API; new applications use the Everruns Framework
Documentation

everruns-runtime

Deprecated compatibility API for existing 0.17.x applications; new applications use the Everruns Framework.

Crates.io Documentation License: MIT

Transition notice: everruns-runtime is compatibility-only in 0.17.x and will be removed in Everruns 0.18. It remains published and usable for the entire 0.17.x line.

New ordinary applications should depend on everruns, start with use everruns::{Agent, Model};, and follow the Everruns Framework. Advanced system integrators should use everruns plus everruns-host and focused provider, MCP, or integration crates, starting with use everruns_host::{HostBackends, InProcessRuntimeBuilder};.

For existing 0.17.x applications, everruns-runtime owns no execution algorithm or backend composition. It re-exports the single implementation from everruns-host, preserving established public paths and feature behavior for supported 0.17.x consumers.

Existing users can migrate incrementally because the compatibility paths execute the same canonical host code. See the authoritative runtime migration guide. All crates are part of the Everruns ecosystem.

0.17 Compatibility Example

use everruns_runtime::{InProcessRuntimeBuilder, RuntimeBackends};

let backends = RuntimeBackends::in_memory();
let builder = InProcessRuntimeBuilder::new().backends(backends);
# let _ = builder;

The builder remains usable through its 0.17 path, but its implementation is the same everruns-host::InProcessRuntimeBuilder. This example is compatibility coverage, not a starting point for new applications. The Framework quickstart is offline and requires no database, server, worker, network, or credentials.

Runnable examples ship with the crate:

cargo run -p everruns-runtime --example in_process_runtime
cargo run -p everruns-runtime --example inspect_context
cargo run -p everruns-runtime --example real_disk_file_system_tools

What It Provides

  • Established runtime types and builders are aliases or re-exports of everruns-host.
  • lua and mcp-stdio forward to the same host feature implementations.
  • Legacy mutable-history and event-bus traits are deprecated, isolated shims; canonical execution writes events only and never calls them.
  • The crate will be removed in Everruns 0.18; no independent implementation is added here during the 0.17 compatibility window.

Documentation

License

Licensed under the MIT License.