Files
deepseek-harness/packages/ptc-runtime
_Kerman 94dae61fb5 fix(ptc-runtime-node): keep per-call binding waits pending when the host closes
Closing the control pipe after the result rejected outstanding birpc
calls; an unawaited binding promise then crashed the child and its trace
reached the result logs. Once the result is returned or the pipe closes,
binding calls now never settle, including those the closure rejects.
2026-10-21 10:30:31 +08:00
..
2026-10-17 15:10:31 +08:00

description, kind
description kind
Package map for the PTC execution capability family: what program execution does for you, and which package owns each part. package-group

ptc-runtime/ — PTC execution capability family

English | 中文

Summary

The ptc-runtime/ group executes model programs against host-provided async functions. The default Node backend starts a fresh process under the configured sandbox policy. Its opt-in executionMode: persistent-in-memory keeps a separate confined REPL for each explicit state owner; memory ends with the process or owner. The experimental Python backend uses a fresh CPython process. Failures return as results for callers to diagnose or present 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
ptc-runtime/ Defines what a PTC runtime does: run one program against host-provided bindings and report what it printed and returned ctx.ptcRuntime
ptc-runtime-node/ Executes TypeScript in fresh processes under file policy or an opt-in retained REPL under the same file policy registers ctx.ptcRuntime
experimental/ptc-runtime-python/ The experimental Python backend: owns the fd-3 wire protocol between a Node host and a CPython subprocess and the CPython runtime implementation —

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.

Dev Note

Working context for maintainers — click to expand

None.