2df28fd249
Review findings on the CPython backend: an explicit pythonBin path bypassed the load-time checks (missing/non-executable/directory paths surfaced only as a run-time worker-exit); a throwing binding member accessor escaped the fd-3 data callback and terminated the host; the reply drain waited on 'drain' alone, so a pipe destroyed under the wait hung forever; and two staging-leak assertions diffed a global tmpdir that parallel workers can perturb. resolvePythonBin now applies the same accessSync(X_OK) + isFile check to explicit paths (resolved against the host CWD), and the load error message distinguishes 'is not an executable regular file' from 'does not resolve on PATH'. validateBindings snapshots callables into a plain record during run()'s synchronous validation, turning an accessor throw into the seam-misuse rejection and fixing the key set the boot frame and dispatch share. The reply drain waits on drain/close/error together and short-circuits on proto.destroyed. The staging-leak assertions check the exact paths this test file staged (recorded by the mocked mkdtempSync) instead of a tmpdir diff. docs(code-runtime-python): add the alternatives section to the hardening note docs(config-catalog): refresh the code-runtime-python Config source line test(code-runtime-python): cover the async spawn-error worker-exit path |
||
|---|---|---|
| .. | ||
| agent-team | ||
| agent-team-profile | ||
| agent-team-web-profile | ||
| client-ui-agent-team | ||
| code-runtime-python | ||
| inspector | ||
| tool-agent-team | ||
| webworker-packer | ||
| webworker-runtime | ||
| AGENTS.md | ||
| README.i18n.yaml | ||
| README.md | ||
| README.zh.md | ||
| description | kind |
|---|---|
| The experimental group map: private prototypes and internal-only plugins excluded from official releases, for users and maintainers navigating the group. | package-group |
packages/experimental
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.