Status

See what is usable now and what is still maturing.

Hosted agents, approvals, gateway capabilities, package management, hosted package UI, and workflow execution exist.

Usable Now

Hosted agents

Interactive agent sessions, model access, sandbox volumes, compute, transcripts, and approvals are the core working path.

Gateway capabilities

Built-in integrations, Agent identities, MCP, and package-backed tools are policy-scoped.

Capability packages

API-key JavaScript and Wasm packages can be registered, tested, published, and invoked.

Human input requests

Packages can pause a tool call for resume-only, free-text, fixed-choice, or approve/reject input before continuing.

Hosted package UI

Static package UI bundles can be attached through package management and rendered from isolated origins.

Workflow execution

Agents can create graph workflow objects, run bounded JS steps, start owned agent steps, schedule workflows, subscribe to supported event sources including webhook-emitted events, inspect history, and pause graph JS steps with durable waits.

Still Maturing

Workflow UI	Richer trigger editing, event delivery diagnostics, schedule controls, and clearer run evidence for the golden workflow loop.
Prompt-assisted workflows	The Workflows-page authoring panel can start an admin-scoped agent that validates and saves workflows or drafts missing setup. A separate review-before-save gate for manual run shape and policy is follow-up work.
OAuth package auth	Provider OAuth connection flows, token refresh, and package binding beyond API-key secrets.
Package UI bridge	Host-mediated package UI calls for setup, action invocation, live context, and resizing.
Third-party package trust	A public package marketplace, package review, signing, provenance verification, version distribution, and stronger secret handling for third-party packages do not exist today.