Chinesezjc
c8139589d2
The review's remaining critical: the fd-3 data handler checked the unframed counter against the 256 MiB wire ceiling, so a single 64-256 MiB frame was fully Buffer.concat-joined (a second copy) and only then dropped in the line loop — the peak-memory doubling the pre-join check exists to prevent, for a frame the parser is guaranteed to discard. The counter is now checked against FRAME_PARSE_CAP_BYTES before the join; the regression case asserts a worker-exit with 'protocol frame exceeded' (fail-before: reverting to the ceiling turns it green, proving the join path). FRAME_CEILING_BYTES is removed. The rejection-cap fix now has its regression: a completion value whose class name is 70 MiB of Ns asserts invalid-output, not worker-exit (fail-before: uncapping the diagnostic turns it red). The settlement note (en + zh) updates the remaining stale bound text, and the fd-3 protocol note (en + zh) no longer claims protocol-only exports or a missing Python codec. Pairings re-recorded.
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.