Chinesezjc
9b29d0226e
Addresses the bot's follow-up review findings on the settlement-path fixes: - The _LogStream seal joined the WHOLE accumulated buffer past the fragment cap, re-copying the growing block O(B^2/cap) times for a large drip. It now seals only the current fragments into a _pending_blocks entry (character count unchanged), so a 25 M single-character drip stays O(B); the newline/flush/ _push_bounded_prefix consumers join blocks + fragments once. - The _clamped soft==hard lowering is scoped to RLIMIT_CPU: for RLIMIT_AS a one-byte soft differential would only misalign the child's applied limit with the host-side budget gate, with no signal to preserve. The hard == 1 blind spot is documented. - send_done's fallback captures memoryview at import (_memoryview) alongside os.write, so a one-line rebind of the name cannot change the fallback write; the comment now states the module-level-captured mechanism.
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.