Community Calls
Go WebAssembly Toolchains Compared, a WASI SDK GitHub Action, and Top-Level WIT Types
The August 19, 2026 wasmCloud community call is a tour of the Go WebAssembly toolchain landscape and the standards work underneath it. Eric Gregory presents the rewritten Go language guide — TinyGo versus componentized Go, trade-off by trade-off — and Bailey Hayes makes the case for skating to where the puck is heading: componentize-go, with cooperative threading for goroutines on the horizon. Victor Adossi ships a WASI SDK GitHub Action that turns C/C++-to-Wasm builds into two steps of CI, Yordis Prieto lands top-level types in the Wasm component model, and newcomer Adam de Delva introduces BTR's Wasm-powered compute portal.
wasmCloud 2.7 Ships 13.6x Concurrency, WIT Annotations Take Shape, and an OCI Registry Made of Components
The August 12, 2026 wasmCloud community call opens with Bailey Hayes unpacking wasmCloud 2.7 — max concurrency on instance pools (13.6x in her best-case benchmark), a hardened OCI registry component, and maps and implements enabled by default in the Wasm component model after a W3C WASI subgroup vote. Aditya Salunkhe walks through his epoch-interruption work for canceling runaway guest code, and Yordis Prieto lays out the plan for WIT annotations — a change that would let WIT express read/write capability views, Protobuf-style validation, and more, making WIT effectively a superset of Protobuf.
wash wizard Demo, a 13.6x HTTP Throughput Improvement, and Async wasmcloud:messaging on WASI P3
The August 5, 2026 wasmCloud community call opens with Aditya Salunkhe demoing wash wizard, a terminal UI that scaffolds custom Wasm workload architectures — ingress triggers, component chains, fan-out, capability selection — into a buildable project. From there Bailey Hayes goes deep on how wasmCloud 2.6's separate Wasmtime stores, trigger services, and concurrent instance pooling produced a 13.6x HTTP throughput improvement, Jeremy Fleitz previews core-instance metrics for the host heartbeat, and Aditya returns with the PR that makes wasmcloud:messaging natively async on WASI Preview 3.
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.