packages/experimental
September 4, 2026 · View on GitHub
English | 中文
Summary
The experimental group contains prototype capabilities that are not part of any official release: they run on the real harness, but their contracts can change and they carry no support promise. The group holds Agent Teams, the cross-realm Inspector, the CPython subprocess backend for the code-execution seam, and the browser-worker runtime and image packer used by preview deployments. Use these packages to try an unreleased capability; they carry no stability promise, and released products must not depend on them.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
agent-team-profile | Explicit source-checkout profile layer for Agent Teams | — |
agent-team | Named teammates with durable messages and a shared task board | ctx.agentTeams |
agent-team-web-profile | Explicit source-checkout Web layer for Agent Teams | — |
client-ui-agent-team | Team roster, task board, and teammate navigation for Web | — |
code-runtime-python | CPython subprocess backend for the code-execution seam | ctx.codeRuntime |
inspector | Cross-realm CDP hub for Host debugging, Client Runtime inspection, network capture, and Cordis trees | ctx.inspector |
tool-agent-team | Ten tools that let the model create, message, and coordinate teammates | registers scoped tools on ctx.tools |
webworker-packer | Builds the gzip-compressed VFS image consumed by the browser worker preview | library and CLI — no ctx key |
webworker-runtime | Runs the harness plugin tree inside a dedicated browser worker | library and worker entry — no ctx key |
Related documentation
- Experimental package decision — placement, release exclusion, and dependency isolation.
- Agent Teams subsystem — durable Team types and the
ctx.agentTeamsservice API. - Experimental subtree rules — what experimental status does and does not relax.
Dev Note
Working context for maintainers — click to expand
None.