Community Calls
WASI OTel Host Plugin Demo, TypeScript Templates & v2 Service Docs
The February 11, 2026 wasmCloud community call is anchored by Jeremy Fleitz's live demo of the WASI OTel host plugin — tracing, logging, and metrics emitted directly from inside a Wasm component into an Aspire collector, with the host adding workload-ID context so component-level spans line up cleanly with host-level spans. Eric walks through new TypeScript templates for HTTP clients and services with wasi-keyvalue and Blobstore backends, plus an expanded services documentation page and a fresh custom hosts / host plugins guide. Bailey updates the community on WASI 0.2.10 (hopefully the final 0.2.x release) and WASI P3 release-candidate progress, and Yordis Prieto confirms he's two code reviews away from landing map support in WIT and is heading for struct next.
TypeScript Templates, Component Interposition Middleware & A C-Advisor for WebAssembly
The February 4, 2026 wasmCloud community call covers the home stretch of v2 hardening and two strong outside demos. Eric walks through the new TypeScript template conventions for v2 — interface-named templates, standardized config.yaml for auto dev/build, package and world naming, gitignored generated artifacts — landing in the wasmCloud TypeScript repo. Elizabeth Gilbert demos component-interposition, her WASI P3 project that interposes middleware components between an HTTP request and a service — single middleware, then three nested onion-style — with the full WAT walkthrough showing exactly how the wac DSL composes the chain. Marcin Ziółkowski presents his work on a C-advisor equivalent for WebAssembly, hitting the wall of how to measure per-instance resource consumption when Wasm runtimes don't sit cleanly inside cgroups; Lucas walks him through the thread-pinning angle, and the call connects him with Elizabeth and the Wizard research engine community. Bailey also covers v2 RC7, the upcoming repo reconciliation that merges wash into wasmcloud/wasmcloud, the imminent WASI 0.2.10 release, and the next WASI P3 RC.
wasmCloud v2 RC7 OTel Demo, Ten Years of Wasm Retrospective & WASI Socket Forking
The January 28, 2026 wasmCloud community call lands on the RC7 observability story: Lucas Fontes demos the new OpenTelemetry host plumbing that ships with RC7, showing traces, logs, and metrics flowing into Aspire dashboard from both wash dev and a Kubernetes deployment — with automatic instrumentation of any component that uses host-implemented WASI APIs (no plugin-author code needed). Eric's "Ten Years of WebAssembly: A Retrospective" goes live as the doc of the week, with Bailey teasing what the next two months of WebAssembly adoption could look like as cooperative threads land and Python, Go, and TypeScript get first-class component compilation. Frank Schaffa drives an extended discussion on LLM-assisted Rust adoption as the real enterprise unlock. The call closes with Bailey and Aditya unpacking why wasmCloud has a forked wasmtime-wasi crate — the TCP-loopback enhancement needed for wasmCloud's service feature — and the upstreaming work that will eventually retire the fork.
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.