2026-08-30 · NextClaw v0.47.0
Published: 2026-08-30 Tags: release apps wasm runtime
NextClaw v0.47.0 turns Portable Service Apps from “Rust/WASM Components can run” into an application runtime that can be developed, authorized, observed, and distributed. Apps still ship as a single .napp and remain self-contained by default; extra capabilities are explicitly mediated by the NextClaw host.
A complete application capability set
- Data and files: Apps can use host-managed KV, SQLite, and granted directories with read-only/read-write modes, revocation, and traversal protection.
- Network and secrets: HTTP follows an allowlist. Secrets are injected only for a call and never written into packages, echoed configuration, or logs.
- Background work: Cancellable jobs, progress, timeout isolation, streaming results, Resident Services, and retryable events continue beyond a Panel's lifetime.
- AI and Agents: Components declare model or Agent slots and call them after binding, with stable denial, cancellation, and timeout behavior.
- Composition: Providers expose versioned capability contracts to other apps. Self-contained apps remain the default; external requirements are disclosed before installation and enablement.
One app, three entry points
Panels, Agents, and nextclaw app invoke now reach the same installed instance, data, and permission decisions. The CLI also exposes dependency setup, secret binding, acceptance status, and evidence export so AI can perform every delegable setup step.
From creation to release
Rust developers can create a template and follow doctor, build, check, test, dev, call, pack, install, and enable as one supported path. Built-in reference apps cover everyday tools, HTTP + secrets, provider composition, Resident events, and persistence with source and smoke fixtures included.
Verified rather than merely claimed
This release defines 22 stable acceptance IDs covering execution, data, files, networking, secrets, jobs, streaming, AI, composition, lifecycle, resource bounds, developer experience, distribution, and documentation. Product UI, CLI, and release automation consume one contract, and evidence is bound to the current version, platform, and scenario fingerprint.
Continue with Portable Service Apps and the runtime capability contracts.