Chinesezjc
436a97a12d
The output-budget/address-space gate's 8x multiple had no room for the interpreter's own footprint, so a budget sized right at addressSpaceMb/8 was admitted while its worst-case peak plus the interpreter overran RLIMIT_AS (e.g. 15 MiB maxLogBytes against 128 MiB). Reserve a fixed INTERPRETER_BASELINE_BYTES (64 MiB) before the multiple claims the rest, so each budget times 8 must fit the room LEFT after the baseline. The host gate validates against the CONFIGURED addressSpaceMb, but a launch environment can inherit a stricter RLIMIT_AS (a ulimit -v wrapper below addressSpaceMb) that _clamped lowers the effective limit to, leaving the budgets sized for a ceiling the child never gets. bootstrap.py now re-checks both budgets against the effective clamped soft limit after applying it, mirroring the host gate's multiple and baseline, and raises at boot rather than letting a near-budget output OOM mid-run. Add regression tests for both (the load gate against a 256 MiB address space covering both budgets, and a ulimit -v wrapper for the inherited-limit re-check); register the tail-copy test in the note Testing section; sync the zh pair. Merges origin/feat/code-runtime-python-protocol to resolve the DIRTY base.
description, kind
| description | kind |
|---|---|
| Package map for the code-execution capability family: what program execution does for you, and which package owns each part. | package-group |
code-runtime/ — code-execution capability family
English | 中文
Summary
The code-runtime/ group provides program execution: a model writes one program that calls host-provided functions as ordinary async calls, and a runtime executes it in isolation and returns only what the program printed and returned. One package defines the shared capability (ctx.codeRuntime), a second executes TypeScript programs in a fresh Node worker thread, and a third owns the wire protocol between a Node host and a CPython subprocess for the Python backend. Every run is independent — no state carries from one program to the next — and failures come back as part of the result, so the caller can see why a program failed and feed that back to the model.
Table of Contents
Packages
These three packages together provide program execution; each README describes what its part does.
| Package | Role | ctx key |
|---|---|---|
code-runtime/ |
Defines what a code runtime does: run one program against host-provided bindings and report what it printed and returned | ctx.codeRuntime |
code-runtime-worker-thread/ |
Executes TypeScript programs, each in a fresh Node worker thread | registers ctx.codeRuntime |
code-runtime-python/ |
Owns the fd-3 wire protocol between a Node host and a CPython subprocess, the Python backend's protocol layer | — |
Related documentation
Start with the subsystem reference for the service contract, then the PTC mode design that consumes this capability and the capability-seam model it follows.
- Code runtime subsystem reference — request/result vocabulary, bindings, and the
ctx.codeRuntimecordis surface. - PTC mode Agent Note — how the tool registry presents
run_codeto the model. - Capability seams — the Service Definition / Service Provider / Consumer split this family follows.
Dev Note
Working context for maintainers — click to expand
None.