Hey all! Sorry if this is not the right place for this (let me know and I'll move it) but curious on progress for the Rust compile target? We've been buildling our AI factory of sorts called Compressor. Compressor is a local-first AI runtime that compresses knowledge into dense, executable capsules (EKUs) and runs them through a jet engine pipeline—Intake, Compressor, Combustor, Turbine, Afterburner, Runtime—where each stage is a factory that transforms input into deployable intelligence. Our ethos: intelligence is compression; schema emerges from observation, not committee; we build factories that build artifacts, not artisanal outputs; we compress the stack itself, replacing Kubernetes with Unix processes, message queues with pipes, observability platforms with ls and git log. The vision is cognitive-native infrastructure—systems built for a world where intelligence is ubiquitous, specialized, and local—not AI bolted onto legacy architecture. Everything runs local, everything is inspectable, everything composes; the 50-year-old operating system is the right foundation for the next era of AI. We're doign it all in Rust & WASM Issue #1539: https://github.com/BoundaryML/baml/issues/1539 Requests first-class Rust client generation (like Python/TS/Ruby/Go have) without needing the OpenAPI workaround. Current state: - BAML is written in Rust, but generates clients for Python/TS/Ruby/Go - Rust users can use BAML via OpenAPI client generation (workaround since v0.55.0) - 10+ thumbs up on the issue

Your in luck! I would wait for the next release 🙂 https://github.com/BoundaryML/baml/pull/2832

all good! Rust and then Compressor generates it's own WASM runtimes for the EKUs.