packages/code-runtime/README.md

# code-runtime/ — code-execution capability family

The code-execution capability seam (see [capability seams](../../docs/rfc/implemented/architecture/2026-06-13-capability-seams.md)): an abstract runtime interface for executing one model-written program against host-provided async bindings, capturing what it printed and returned. The consumer is the tool registry's [Code Mode](../core/tools/README.md) (`tools: { mode: code }` — the `run_code` tool and the generated TypeScript SDK); design in the [Code Mode RFC](../../docs/rfc/implemented/feature/2026-06-15-code-mode.md). **Product** packages.

| Package | Role | ctx key |
|---|---|---|
| `code-runtime/` | Abstract code-execution seam (interface + vocabulary) | `ctx.codeRuntime` |
| [`code-runtime-worker/`](code-runtime-worker/README.md) | Worker-thread backend: fresh worker per run, TypeScript via host-side type-strip (annotations advisory, never type-checked), port-bridged bindings, budget/heap containment | registers `ctx.codeRuntime` |

The interface lives at `code-runtime/code-runtime/`; the shipped backend at `code-runtime/code-runtime-worker/`. Backends differ by execution substrate (worker thread, process, container) and by source language — both readonly descriptors on the service — and register `ctx.codeRuntime` without touching the interface or its consumer; that split is what makes a hardened backend a drop-in later.
feat: add the code-execution capability seam (ctx.codeRuntime) 2026-07-08 02:17:24 +08:00			`# code-runtime/ — code-execution capability family`

feat: Code Mode — the registry's mode config, the SDK codegen, and the run_code bridge 2026-07-08 12:58:23 +08:00			The code-execution capability seam (see [capability seams](../../docs/rfc/implemented/architecture/2026-06-13-capability-seams.md)): an abstract runtime interface for executing one model-written program against host-provided async bindings, capturing what it printed and returned. The consumer is the tool registry's [Code Mode](../core/tools/README.md) (`tools: { mode: code }` — the `run_code` tool and the generated TypeScript SDK); design in the [Code Mode RFC](../../docs/rfc/implemented/feature/2026-06-15-code-mode.md). Product packages.
feat: add the code-execution capability seam (ctx.codeRuntime) 2026-07-08 02:17:24 +08:00
			`\| Package \| Role \| ctx key \|`
			`\|---\|---\|---\|`
			\| `code-runtime/` \| Abstract code-execution seam (interface + vocabulary) \| `ctx.codeRuntime` \|
docs: state advisory typing in the worker row (review) 2026-07-09 00:38:21 +08:00			\| [`code-runtime-worker/`](code-runtime-worker/README.md) \| Worker-thread backend: fresh worker per run, TypeScript via host-side type-strip (annotations advisory, never type-checked), port-bridged bindings, budget/heap containment \| registers `ctx.codeRuntime` \|
feat: add the code-execution capability seam (ctx.codeRuntime) 2026-07-08 02:17:24 +08:00
feat: add the worker-thread code runtime (dsh-code-runtime-worker) 2026-07-08 11:00:06 +08:00			The interface lives at `code-runtime/code-runtime/`; the shipped backend at `code-runtime/code-runtime-worker/`. Backends differ by execution substrate (worker thread, process, container) and by source language — both readonly descriptors on the service — and register `ctx.codeRuntime` without touching the interface or its consumer; that split is what makes a hardened backend a drop-in later.