BuildRiot
Sign in

AISource: AG-UI

AG-UI announces Strands recovery and A2UI nested-rendering fixes

AG-UI announced @ag-ui/aws-strands 1.0.1 and @ag-ui/a2ui-middleware 0.0.13, reporting fixes for tool ownership and persistence during durable resume, plus nested rendering. The project declares no breaking changes for either package.

AG-UI logo
Cover: BuildRiot

AG-UI announced @ag-ui/aws-strands 1.0.1 and @ag-ui/a2ui-middleware 0.0.13 on October 19, 2026, reporting fixes for session recovery and nested rendering. The announcement lists publication at 11:31:23 UTC and declares no breaking changes for either package. Sources: AG-UI

AG-UI says Strands tool ownership after durable resume now follows actual frontend-proxy registration. It reports that resume receipts persist before terminal success and usage survives save failures. The release also reports shared native-agent exclusion during asynchronous setup and completion persistence. It includes an auxiliary-model SDK compatibility fix. Sources: AG-UI

For A2UI, AG-UI says different assistant-message IDs no longer imply nesting, while same-message calls and sibling surfaces remain separate. It also says missing-identity recovery remains available after outer arguments finish streaming. According to AG-UI, the optional A2UIMiddlewareConfig.a2uiGenerationToolNames setting distinguishes generation wrappers from ordinary tools. It preserves custom-wrapper defaults. Sources: AG-UI

The fixes remain upstream reports from AG-UI. The release mentions custom-wrapper migration and ancestry limits without explaining those limits or showing configuration syntax. Sources: AG-UI

The Strands setup guide on main specifies @strands-agents/sdk>=1.1.0 and Node.js 20+ for ECMAScript modules. CommonJS loading requires Node.js 20.19+ or 22.12+. It lists required peers @ag-ui/core, @ag-ui/client, @ag-ui/encoder and @ag-ui/a2ui-toolkit. SDK peers include @modelcontextprotocol/sdk, @opentelemetry/api and zod. Server helpers require Express. This guide provides current setup context rather than a frozen dependency snapshot for version 1.0.1. Sources: AG-UI

What to do

  1. Record the baseline lockfile, then run npm install @ag-ui/aws-strands@1.0.1 to evaluate the Strands update.
  2. Evaluate the middleware separately with npm install @ag-ui/a2ui-middleware@0.0.13 before testing both upgrades together, checking release-specific peer requirements first.
  3. As a proposed @ag-ui/aws-strands 1.0.1 regression check, compare baseline and patched frontend-proxied and native tools through pause, persistence, restart and resume. Capture registrations, executor identities, saved state and ordered events, including terminal success and usage data.
  4. As proposed @ag-ui/aws-strands 1.0.1 regression checks, delay or fail saves and overlap shared-agent runs during setup and completion persistence, recording save timing, terminal events, retained usage and shared-state changes.
  5. As proposed @ag-ui/a2ui-middleware 0.0.13 regression checks, compare message-ID, same-message, sibling-surface and missing-identity fixtures before and after outer argument streaming ends. Then test custom wrappers with A2UIMiddlewareConfig.a2uiGenerationToolNames. Check that generation wrappers are distinguished from ordinary tools and custom-wrapper defaults remain intact. Sources: AG-UI

Why it matters

The reported fixes target tool execution after recovery, success-event timing and nested rendering. Developers have exact versions to evaluate, but the Strands setup guide on main does not establish release-specific dependency requirements.

Attribution

Sources

  1. 1AG-UIRelease Release 2026-10-19Source published (UTC)
  2. 2NewReleasesag-ui-protocol/ag-ui release/2026-10-19 on GitHubSource published (UTC)
  3. 3AG-UIAWS Strands TypeScript integration setup guide

Read the original source for full details and context.

Report a problem

Links, dates or what you expected. Do not include passwords or private data.

More on AI

All AI stories