मुख्य कंटेंट तक स्किप करें

Features and crate boundaries

Most applications should depend only on microclaw-sdk. Its feature presets control how much implementation enters the dependency graph while preserving the same public run protocol.

Feature recipes​

Complete embedded Agent Engine​

microclaw-sdk = { version = "0.6.1", features = ["full"] }

Use this for providers, tools, memory, Skills, MCP, hooks, Subagents, and Worker transport in one host.

Protocol-only integration​

microclaw-sdk = {
  version = "0.6.1",
  default-features = false,
  features = ["minimal"]
}

Use the stable request, result, event, control, and Worker wire contracts without pulling microclaw-engine into the dependency graph. Add standard when the host also needs Runtime, Agent, and RunExecutor.

The minimal graph excludes the Agent Engine, Reqwest, SQLite, Tokio, Typst, and OpenTelemetry. The standard graph also excludes the Typst/PDF renderer; full enables the Engine's document-tools feature.

Runtime plus remote Worker transport​

microclaw-sdk = {
  version = "0.6.1",
  default-features = false,
  features = ["standard", "remote-worker"]
}

Use this for a control-plane application that submits work to another process.

Published crate topology​

The crates.io release exposes three supported layers:

CrateResponsibility
microclaw-coreStable run protocol, events, shared errors, and utilities
microclaw-engineAgent Engine, persistence, tools, channels, runtime, and Worker implementation
microclaw-sdkSupported application-facing facade

The remaining workspace crates are application packages. Prefer SDK re-exports unless you need the Engine's lower-level integration APIs.

Compatibility expectations​

  • The workspace declares Rust 1.93 as its minimum supported Rust version.
  • Serialized Worker messages are guarded by WORKER_PROTOCOL_VERSION.
  • CI compiles standalone downstream consumers for minimal, standard, and full.
  • The publication workflow checks public API compatibility against the previous crates.io release once a baseline exists.

Before upgrading, read the project release policy and upgrade guide.