Current release status

What you can use today

The Portal offers public documentation and local examples. Approved private-preview participants can download the selected packages, run the Generic HTTP first action, and adapt an operation for their application. Package Access has the complete ZIP, exact versions and installation steps. The Examples Gallery explains what each example was actually tested to do.

The selected seven-archive private handoff contains Core 1.0.0-rc.1, Runtime 0.2.0-preview.5, Actions 0.2.0-preview.8, Retell adapter 0.2.0-preview.3, Retell equipment example 0.2.0-preview.4, Generic HTTP reference 0.2.0-preview.4, and Trace Local 0.1.0-preview.7; they are not available from a public registry or through unauthenticated Portal download. Protected downloads require an approved invitation, accepted agreement and active entitlement. Signing in alone does not grant access.

Authenticated Guide can help authorized participants with AnswerUp questions and proposed integration code, subject to usage limits. Guest Guide answers questions from a smaller selected documentation set. Generated code is for developer review; Guide does not run it or act on a business system. The package-free Lumber tour uses sample data and does not run the SDK.

What your application must provide

Your application still owns trusted input and authorization, its business-system functions, provider credentials, an independent verifier, durable records and recovery controls. It must check both the verified outcome and claim permission before confirming an action to a customer. A provider acknowledgment, log entry or Trace view cannot replace the authoritative business-system read. Start with Provider and verifier responsibilities and the Developer Manual.

Operating envelope for the selected packages

Use Node.js 22 or newer for the combined Core 1.0.0-rc.1, Runtime 0.2.0-preview.5 and Actions 0.2.0-preview.8 integration. Core alone supports Node 20+, but the selected combined examples use Node 22+. See Versioning and migrations.

• Bounded records and evidence. Runtime recovery records and artifact projections each have a 32,768-byte canonical UTF-8 boundary. A Runtime artifact projection includes at most 64 Trace records; optional projection data may be reduced to fit. Trace Local preview.7 accepts one supplied evidence file of at most 64 KiB. These are limits on those structures, not a general request, database or operation-size limit. See Trace Local and Host operations.
• Process resources. Selected Core and Runtime keep process-local registrations and authority state without general eviction or disposal APIs. They do not provide a package-wide concurrency governor or total operation cap. In a bounded local measurement of the selected Core/Runtime/Actions trio, each of three fresh processes performed 300 warm-up operations followed by 10,000 sequential, independent, successful operations against local callbacks at concurrency one. On one WSL2 Ryzen machine with Node 22.23.2 and explicit garbage collection between 1,000-operation blocks, Actions post-GC heap grew about 127 MiB from the post-warm-up level. The measurement used no external provider or database and did not control CPU frequency or host scheduling. This fixture is a measured retention warning, not a rate, memory-per-operation promise or production sizing result.
• Deployment planning. Start with low-volume preview use and monitor heap and resident memory (RSS) as independent operations accumulate. Set your own bounded admission, queues and process-drain policy around durable records and unresolved effects. No supported production throughput, CPU/RAM minimum, process-lifetime or sizing guarantee has been established for this package set. The HTTP and Retell examples have their own input and single-writer limits; those are not Core-wide limits.

Limits to plan for

• Local preview scope. The Portal does not provide hosted execution, a public Core control plane or public registry distribution. A private-preview result is not a production-readiness claim. The current examples use local test systems; they do not validate every provider, arbitrary process loss or distributed operation.
• Recovery after uncertainty. Actions preview.8 live reconciliation needs the original process-local, identity-bound, one-shot UNKNOWN object, so that path cannot simply resume after a restart. Runtime preview.5 can rehydrate a bounded, verifier-only continuation from a host-retained closed DurableRecoveryRecordV2 with accepted recovery authority and stable verifier registration. The host must durably admit work, preserve the original dispatch and effect-identity bindings, and verify the original effect against authoritative provider evidence. An unresolved UNKNOWN must remain uncertain; do not blindly call run() again or redispatch the provider. Hosts must retain/export the appropriate durable material and supply persistence, routing, verifier registration, authority controls, and any needed leases, fences, source-record digest, and CAS state. Recovery is not automatic after restart and is not hosted recovery, exactly-once behavior, certification, or a universal production-durability guarantee. See UNKNOWN reconciliation and Host operations.
• Evidence and cleanup. Abrupt process-loss cleanup remains unproven. Actions preview.8 returns an empty privacy-safe Trace envelope by contract; optional Trace inspection requires separately captured, bounded evidence. Logs and Trace show observations, not independently verified business truth. Keep raw payloads, credentials and live result objects out of diagnostic files. See Diagnostics & Logging and the Conformance checklist.
• Account access. Sign in with an email code or choose an offered Google, GitHub or Microsoft option. If a provider cannot complete sign-in, try email or contact Support. Connect another provider from Account security after signing in to your existing account. Signing in remains separate from invitation approval, agreement acceptance and package entitlement.

Additional adapters, hosted capabilities and the local Playground are not supplied as part of this preview. See the Roadmap for their current status; it does not promise a release date. For historical package compatibility, use Versioning and migrations.