forge docs

Rust Guide

Use the Rust reference implementation as the release-gate anchor for Forge.

Rust Guide

Rust is the Forge reference implementation and the anchor for release-gate expectations.

Primary surfaces

  • forge-rs/crates/forge-core
  • forge-rs/crates/forge-agent
  • forge-rs/crates/forge-identity
  • forge-rs/crates/forge-auth
  • forge-rs/crates/forge-mcp

Choose Rust when

  • you want the reference behavior first
  • you need the strongest view into the release gate
  • you are working close to conformance, performance, or WASM-adjacent runtime behavior

Use Rust when you need

  • reference behavior
  • release-gate and conformance anchoring
  • workspace-wide testing and verification
  • the earliest implementation of new core runtime features

Baseline developer workflow

  1. start from the forge-rs workspace
  2. verify the release gate and crate-level tests
  3. use the crate map rather than treating forge-sdk as the only entry point
  4. read the provider, identity, auth, and agent contracts together

Useful verification commands

  • cargo test --workspace
  • python3 tools/release_gate.py --root .

Current guidance

Treat Rust as the most complete reference surface, but rely on the repo-level release gate rather than assumptions when determining production readiness.