Ai

ZeroClaw v0.7.0 Beta Reshapes the Platform With Cargo Workspace and Config V2

ZeroClaw v0.7.0 Beta Reshapes the Platform With Cargo Workspace and Config V2

ZeroClaw v0.7.0-beta.1030 marks the most significant platform rewrite in the project’s history. The update is centered on a deep architectural rework that breaks the former monolith into a structured Cargo workspace, while also introducing a new Config V2 schema with live migration support. Alongside that foundation work, the release improves provider streaming behavior and separates the web dashboard from the core binary, signaling a more modular and scalable direction for future development.

What Changed

The biggest change in this beta is the completion of ZeroClaw’s workspace split. The codebase has been reorganized into more than a dozen focused Rust crates, including modules for runtime, gateway, channels, tools, memory, providers, config, plugins, hardware, and infrastructure. This is a major engineering milestone because it replaces a monolithic source tree with a maintainable multi-crate architecture that should make the project easier to build, test, and extend over time.

The release also ships a new Config V2 schema with an automatic migration path. Users can run zeroclaw config migrate to upgrade existing configurations in place while preserving comments, reducing upgrade friction. The older props command remains available for compatibility, but it is now officially deprecated in favor of the new zeroclaw config workflow.

Another notable improvement is OpenRouter streaming support. The OpenRouter provider now streams responses token by token rather than waiting for a full completion, bringing its user experience closer to native model providers and improving responsiveness in interactive sessions.

The web dashboard has also been decoupled from the core binary. Instead of being tightly bundled during normal builds, it is now built separately and embedded at release time. That design should simplify release engineering and keep the core binary leaner.

Why It Matters

This beta is important because it is less about a single feature and more about preparing ZeroClaw for long-term scale. Moving to a proper Cargo workspace gives the maintainers a cleaner platform for shipping new capabilities across providers, channels, memory systems, and hardware integrations without repeatedly fighting monolithic complexity.

The Config V2 migration path is equally important for operational reliability. Infrastructure and AI tooling projects often struggle when configuration formats evolve, but ZeroClaw is trying to reduce that pain by offering an in-place migration command that preserves existing file structure and comments. That makes upgrades more realistic for active deployments.

The OpenRouter streaming enhancement matters for end-user experience. Faster visible output can make hosted providers feel substantially more responsive, especially in chat and agent workflows where perceived latency affects usability.

Overall, ZeroClaw v0.7.0-beta.1030 looks like a foundational release focused on developer ergonomics, modularity, and runtime experience. If the new architecture holds up in beta, it could make future releases faster to ship and easier to operate across a wider set of AI deployment scenarios.

Official Source: https://github.com/zeroclaw-labs/zeroclaw/releases/tag/v0.7.0-beta.1030