Community Calls
wash RC6: Persistent Blobstore, Virtual TCP Loopback & The Path to wasmCloud v2
The January 21, 2026 wasmCloud community call covers wash RC6 — one of the largest release candidates yet — with significant behavior and API changes focused on simplicity and a narrower scope for the v2.0 release. Lucas Fontes walks through the RC6 highlights: a filesystem-backed Blobstore and wasi-keyvalue (so data persists across wash dev restarts), virtual TCP loopback between components in the same workload (so two workloads can both bind port 80 with no collision), and significant correctness improvements in service-to-component context passing. A new QR code generator example in 71 lines of Rust demonstrates HTTP, POST handling, error handling, and PNG generation server-side. The team identifies three remaining items before the v2 release: an internal Kubernetes identifier change, NATS authentication support in the operator and wash host, and gRPC-aware outbound transport. Eric has the RC6 doc rev in PR; ossfellow asks about the wash → wasmCloud repo move and Bailey confirms the plan: v1 goes to its own repo, v2 takes over the main wasmcloud/wasmcloud repo, artifacts release from there.
Blobby UI Demo, wash build/dev Project Inference & v2 Service/Component Workloads
The January 14, 2026 wasmCloud community call is anchored by Lucas Fontes' Blobby UI demo and a deep architectural change to wash build and wash dev. Blobby — the long-running Blobstore example — gets a proper web UI that uploads, downloads, copies links, and shows a recent-activity bar, with both the UI and the API served by the same WebAssembly component. Under the hood, wash build and wash dev move from implicit file-sniffing project inference to explicit build commands in config — solving the monorepo problem, enabling environment-variable interpolation in build commands, separate debug vs release commands, and direct integration with Make or any other build tool. Service-and-component co-development is now first-class through the new wash dev config that lets you bring additional Wasm files into the workload (demoed with a cron service + cron component). Bailey Hayes highlights the importance of explicit configuration as a long-term maintenance win. luk3ark asks how plugins compare to bringing in components for backend interfaces, and Lucas explains the host-plugin model. Eric introduces the new v2 Glossary and the draft Quick Start guide with a local Kubernetes deployment step. The team closes with notes on the next WASI P3 release candidate landing in Wasmtime and a refreshed Go component SDK compatible with the latest tinygo and wasm-tools.
Path to wasmCloud v2: RC6 Plan, gRPC, P2→P3 WIT Translator & WIT Map Support
The first wasmCloud community call of 2026 — January 7 — focuses on the release plan for wasmCloud v2 RC6. Lucas Fontes walks through a GitHub project dashboard of the issues and PRs still open, what's validated vs needs validation, and which features land in v2.0 vs a fast-follow point release. The big additions targeted for RC6: multi-Wasm dev (services + components side-by-side), NATS authentication for the host and operator, Kubernetes workload IDs for resiliency, in-memory Blobstore and wasi-keyvalue in wash dev, and a published WIT package for wash. Deferred to point releases: component restart (semantics conflict with orchestrator behavior in clusters), virtual TCP/UDP loopback (waiting for Wasmtime 41 to avoid a Wasmtime fork), and integration tests with the new fixture handling. Aditya commits to refactoring the gRPC PR to be default behavior (not modular) by end of week. ossfellow shares his LLM-driven P2→P3 WIT translator built as a Goose recipe, which sparks a broader conversation about where this kind of tooling could live (personal repo first, possibly wasm-tools later). Yordis Prieto lands a major WIT map type addition to wasm-tools and is working on the Wasmtime host bindings for it next. Bailey closes with the v2 syntax changes from the latest WASI P3 RC and a discussion of the wash → wasmCloud monorepo move ahead.
wasmCloud v2 RC5: wash new, the Wasm Component Model & Agentic AI
The December 17, 2025 wasmCloud community call is a short, focused look at wasmCloud v2 Release Candidate 5 and the developer experience for building Wasm component model projects. Eric Gregory walks through how wash new has been refactored — the old interactive templating wizard is gone, replaced by cloning an example repo directly from a Git URL — and demos the updated Rust hello world that now uses the wstd standard library for Wasm components. Liam Randall closes with the news that the Linux Foundation has launched an Agentic AI Foundation, with Anthropic donating the Model Context Protocol (MCP).
WebAssembly on Kubernetes: Volume Mounts, Services & HTTP Ingress
The December 10, 2025 wasmCloud community call is all about running WebAssembly on Kubernetes in production. Eric Gregory walks through a new doc and demo for mounting Kubernetes volumes into a Rust component in wasmCloud v2, then shares a fresh overview of workload services as the stateful companions to stateless components. Lucas Fontes lays out the project's biggest remaining deficiency — HTTP ingress across many hosts — and proposes an intelligent ingress gateway that routes by ephemeral workload ID for zero-downtime deployments, all without tying wasmCloud to Kubernetes.