# wasmCloud 2.8: Async messaging, admission control, and a backstop for runaway guests

DevFeed: [wasmCloud 2.8: Async messaging, admission control, and a backstop for runaway guests](<https://devfeed.tech/articles/wasmcloud-2-8-async-messaging-admission-control-and-a-backstop-for-runaway-guests-15444.md>)

Original publisher: [Read original article](<https://wasmcloud.com/blog/wasmcloud-2-8-release/>)

Author: Eric Gregory

Published: 2026-08-26T00:00:00Z

Content type: release

Language: en

Sources: [wasmCloud Blog](<https://devfeed.tech/sources/wasmcloud-blog.md>)

Topics: [Messaging](<https://devfeed.tech/topics/messaging.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [configuration](<https://devfeed.tech/topics/configuration.md>)

Tags: [async](<https://devfeed.tech/tags/async.md>), [interfaces](<https://devfeed.tech/tags/interfaces.md>), [memory](<https://devfeed.tech/tags/memory.md>), [messaging](<https://devfeed.tech/tags/messaging.md>), [wasmcloud](<https://devfeed.tech/tags/wasmcloud.md>)

## AI overview

wasmCloud 2.8.0 introduces asynchronous messaging interfaces with streamed payloads, typed errors, and timeouts. It also adds admission control for messaging deliveries, detects guests that consume CPU without yielding, exposes wasmtime memory tuning through Helm, and tightens related defaults.

## Source excerpt

wasmCloud 2.8 ships the async wasmcloud:messaging 0.3.0 interfaces with streamed payloads, brings messaging deliveries under admission control, opens up wasmtime memory tuning, and reclaims CPU from guests that never yield.