Community Calls
wasmCloud 2.6 Released: Host Components, AI Inference Beyond wasi-nn, and Capability-Driven Security
The July 29, 2026 wasmCloud community call is the first after the wasmCloud 2.6 release: Bailey Hayes recaps the headline features — host components, instance pooling with concurrent subtasks, and trigger services — and asks the community to try the release and feed back on the new entity types. From there the call ranges widely: a live-on-stream creation of the new awesome-wasmcloud repo, a sketch of a wasmCloud AI inference stack that goes beyond wasi-nn by building chat APIs atop wasi-webgpu, the state of Python and cooperative threads, and a long design discussion with Yordis Prieto on capability-driven security and custom annotations in the Wasm component model.
wasmCloud 2.6 Preview: Host Components, Go WebAssembly Components, and AI Inference with Candle and Qwen3
The July 22, 2026 wasmCloud community call is a release preview. Bailey Hayes walks everything landing in wasmCloud 2.6 — host components, roughly 25,000 lines of changes, a fixed performance regression with new public benchmarks, WASI Preview 3 assumed as the default, wasi-webgpu 0.3.0-rc.2, and the DevX work that reads wkg.toml natively and upgrades old modules to P3 components automatically — then lays out the two PRs still standing between main and a release candidate. Jeremy Fleitz kicks off the quarter's "Are We Componentized Yet?" initiative by moving Go WebAssembly support beyond TinyGo to mainstream Go with componentize-go and wit-bindgen-go, and Bharat closes with a workflow demo that runs audio transcription and Qwen3-powered AI inference entirely in Wasm components using Hugging Face's Candle framework.
Host Components, Epoch Interruption, and the Q3 Roadmap for WebAssembly on Kubernetes
The July 15, 2026 wasmCloud community call is a long, unusually technical one. Bailey Hayes opens with the Q3 roadmap board that came out of the previous week's planning session — host components, macro benchmarking, a Kubernetes secrets plugin, async messaging, and epoch interruption for both cancellation and yielding long-running work — then walks the stack of PRs behind host components: trigger services with their own P3 exports and their own store, passing WASI Preview 3 values across stores, and host component plugins that add capabilities at host tenancy. Frank Schaffa pushes hard on resource boundaries, which turns into the best discussion of the call: how to bound CPU without writing a scheduler, why epochs beat fuel, and where throttling metrics belong when you run WebAssembly on Kubernetes. Mike Williamson closes with a demo that compiles an rsbuild static site straight into a .wasm component.
The wasmCloud Q3 Roadmap: Build Stuff, Agentic AI, and Platform Engineering Reference Architectures
The July 8, 2026 wasmCloud community call is the Q3 roadmap planning session. Bailey Hayes opens with a Q2 retrospective — WASI Preview 3 shipped and is enabled by default, the implements feature is essentially complete, and the SQLx example landed along with upstream fixes in mio, Tokio, and socket2 — then hands the board to the community. The number one theme for Q3 is simply build stuff on top of wasmCloud, with agentic AI and MCP pulled forward, WASI WebGPU and long-running compute alongside them, and a strong pull from platform engineering teams for reference architectures that explain when a concern belongs in a workload, a service, or a host component. Jeremy Fleitz, Aditya Salunkhe, Yordis Prieto, Bharat, Colin Murphy, and Eric Gregory fill in the rest: polyglot CI tracking, NATS queue groups for autoscaling, exploded components, and a hard argument against generic messaging interfaces.
wasmCloud 2.5: Wasm Component Model implements, WASI P3 Streaming, and Cancelling Long-Running Invocations
The July 1, 2026 wasmCloud community call opens on the 2.5 release, cut the day before: Wasmtime 46, WASI Preview 3 on by default, async support, and the Wasm component model implements feature that lets one component multiplex several backends behind a single named interface. Jeremy Fleitz demos implements with Postgres — one component importing the same query interface twice as pg-user-a and pg-user-b, each bound to a different database role with different table grants — then Bharat shows cross-component streaming on WASI P3 with a Whisper model transcribing an hour-long podcast. The back half is a deep architecture discussion with Aditya Salunkhe, Bailey Hayes, and Frank Schaffa on cancelling long-running invocations with Wasmtime epoch interruption, where health checks belong, and how breaking apart stores turns a long-lived service into a workload's front door.