The wasmCloud community is testing Release Candidate 5 (RC5) for wasmCloud 2.0, which brings significant CLI consistency improvements and a simplified wash new command that uses git repositories as project templates. The Linux Foundation announced a new Agentic AI Foundation that will host MCP (Model Context Protocol), highlighting the growing intersection of AI agents and wasmCloud's sandboxing capabilities for security.
wash new Simplified: The templating feature is temporarily removed; projects are now created by cloning git repositories directly.wash/config.json with more format options comingThe wasmCloud team has released Release Candidate 5 for testing. Lucas and Bailey have been refining CLI consistency, ensuring flags, arguments, and terminology are predictable and well-documented. The command reference documentation has been updated to reflect these changes.
The most significant change in RC5 is how wash new works. Previously, users would run a CLI wizard to select their language and project type. Now, users clone directly from a git repository:
wash new <git-url> --name <project-name> --subfolder <path>
The templating feature has been removed from the v2.0 MVP to allow for proper implementation and testing in a future release. This means you can point to any git repository and use it as your starting point, with options to specify a branch, tag, or commit via the --git-ref flag.
The Rust hello world example has been updated to use the WT Rust standard library for WASM components. This change aligns wasmCloud with the broader WebAssembly ecosystem and uses simple async functions for handling HTTP requests.
The wasmcloud.toml configuration file from v1 is being revamped. Currently, v2.0 uses a config.json file in the .wash subdirectory, but this format will undergo major changes. The team plans to support multiple configuration formats for user flexibility.
The Linux Foundation announced the Agentic AI Foundation (AIF), which will host three projects:
This is particularly relevant to wasmCloud because the community is using wasmCloud's sandboxing capabilities for MCP components to address security concerns. The non-deterministic nature of LLM I/O creates vulnerabilities including prompt injection, remote code execution, lateral movement, and data exfiltration.
The team acknowledged community contributors, specifically calling out Pavle (five commits in recent weeks) and Dicha along with the Betty Blocks team for their consistent contributions to the project.
"The way wash new works right now in RC5 is it's going to grab an example repo, a git reference, and clone that down and you can use that as your starting point."
"We're now using the WT Rust standard library for WASM components in an effort to try to be as ecosystem aligned and centralized as possible."
"The sort of non-deterministic IO of LLMs creates a whole set of opportunities and a whole set of problems that need to be addressed such as prompt injection, remote code execution, lateral movement, and ultimately data exfiltration."
| Time | Topic |
|---|---|
| 00:00 | Welcome and RC5 announcement |
| 00:45 | Documentation and CLI consistency updates |
| 01:55 | How wash new works in RC5 |
| 03:27 | Demo: Creating a Rust project with wash new |
| 05:05 | Updated Rust hello world example |
| 06:08 | Linux Foundation Agentic AI Foundation announcement |
| 07:00 | MCP and Sandbox MCP for security |
| 08:10 | Q&A: wasmcloud.toml configuration changes |
| 09:08 | Community contributor recognition |
| 09:53 | Holiday schedule and wrap-up |