PUBLIC BETA
Current beta scope and limitations
Notice version 2026-09-28
The beta scope covers the current dashboard and CLI for Stripe, native Zendesk and their supported combined workflows. Check the release page for publication status. Supported means the documented subset can be used; it does not mean a complete reproduction of every provider feature.
Stripe
The implemented surface has real-API drift evidence. It covers the documented customer, payment, refund, invoice and subscription workflows. The dated fidelity record states what was checked, and the scope reference lists omissions and refused parameters.
Examples outside this subset include Checkout, Connect, disputes, tax, coupons, trials and multi-item subscriptions. Unimplemented routes and recognized unsupported writes fail explicitly.
Zendesk
The native profile supports the declared directory, ticket, comment, audit, bounded Search, assignment and lifecycle operations. Local conformance is tested; live API qualification is pending. It is included as beta functionality with those limits, not as a fully verified copy of your tenant.
Macros, triggers and SLAs are not implemented. Custom fields/statuses, attachments, deletion, bulk jobs and tenant-specific automation are also outside the current profile. Import is from supported offline snapshots or reviewed Full JSON exports, not live Zendesk ingestion.
In beta.2, users can be created with email, but user updates accept name only. Any email field on an update is refused before saving other changes. The beta does not enforce agent restrictions on editing other staff members or reject duplicate organization names or external IDs. Avoid tests that depend on those permissions or uniqueness rules; corrections in development are not included in this package.
The older Zendesk-shaped ticket desk is a separate demo-grade profile used by legacy billing samples. Its behavior and evidence do not establish native Zendesk parity.
CLI setup directories
Create the destination project folder before native Zendesk or combined CLI setup. These modes require an existing directory; a missing destination currently produces a generic input error. The dashboard setup guide also starts in an existing project folder.
Combined workflows and agent connections
Supported combined worlds share a clock and state. Starting data must satisfy composition rules, and grading requires explicit billing-to-ticket bindings. The dashboard offers supported combinations and retains each connector's qualification.
Agents run as local commands with the documented input/output contract. Native Zendesk requires explicit endpoint configuration; supported Stripe SDKs can use the supplied preload. Hosted-agent endpoints and tools whose destination cannot be changed are outside this release.
Results, replay and local storage
Keep the accompanying safe JSON when exporting a native HTML report. The HTML shows the overall outcome and task findings; details of protected or unexplained changes elsewhere in the world are currently available in the JSON. A passing task does not override a failed overall result.
World replay is deterministic for the same starting data and request sequence. A model may choose a different sequence on another run. Optional model judgments are advisory; inspect authoritative state expectations and any ungraded tasks.
Scripted samples contain synthetic data and teach the workflow. They are not customer performance measurements. Local evidence stays until you delete it. Beta upgrades may require recreating disposable worlds from reviewed saved inputs; preserve your project before changing versions.
The local runtime is designed for a trusted harness. It is not a security boundary for hostile code running on the same machine. Keep it on trusted infrastructure and follow the deployment reference before exposing it beyond loopback.
Platforms and optional model drafting
macOS and Linux with Node 24 or newer are the beta platforms. Windows is not verified. The first installation needs network access. Installed dashboard assets and scripted samples work offline; your own agent, source imports and selected model providers may need the network.
Optional drafting remains available. Bounded live-provider acceptance for this beta candidate is pending explicitly supplied credentials. Do not treat a configured provider, local request validation or a mocked test as a live-verified integration.
Other connectors
Other catalog listings collect interest. They are not included in this beta and carry no delivered-feature or verification promise.