Remove the E2B execution providers
移除 E2B 执行提供方
The E2B experiment supplied one remote filesystem/process world for file tools, Bash, PTY and language servers while the Harness, credentials, model transport and session state stayed on the host. Its three providers demonstrated that those consumers can share the existing filesystem and subprocess interfaces without provider-specific tools. PTC Node confinement requires bidirectional control traffic separate from ar
English
Problem
The E2B experiment supplied one remote filesystem/process world for file tools, Bash, PTY and language servers while the Harness, credentials, model transport and session state stayed on the host. Its three providers demonstrated that those consumers can share the existing filesystem and subprocess interfaces without provider-specific tools.
PTC Node confinement requires bidirectional control traffic separate from arbitrary program stdin/stdout/stderr. The pinned [email protected] SDK exposed standard process streams and PTY output, with no extra descriptor transport. Creating a descriptor inside the VM does not expose it to the Harness host; a remote relay or a separate authenticated stream must bridge it.
Such a bridge owns independent progress when output blocks, bounded retention, channel closure, startup publication, command identity, cancellation and disconnect cleanup. The SDK retained complete stdout/stderr even when a consumer applied backpressure, so stream-level queue bounds alone could not bound host memory. Extending that adapter would turn the experiment into a separate remote transport project.
Decision
The repository excludes the E2B sandbox owner, filesystem provider and subprocess provider, their SDK dependency, integration fixtures, opt-in workflow and generated registrations. It supplies no E2B execution backend. The removal trades that integration for a smaller maintained implementation set; it does not imply that E2B cannot support a suitable transport or that published packages have no external users.
The portable execution-world decision remains authoritative for ctx.fs and ctx.subprocess. The pair describes one path namespace and process world. Providers own path conversion, executable lookup, ordinary streams, terminal allocation and managed cleanup; consumers retain tool semantics, policy and presentation. A local/remote metadata label adds no authority to those operations.
Remote execution remains an intended capability. Terminal allocation, writes, foreground inspection and signalling retain their Promise contracts and pending-operation cancellation guarantees. A local implementation completing these calls synchronously does not justify removing the asynchronous behavior required by remote providers. Process completion, terminal readiness, emulator parsing and managed-range quiescence also retain their existing owners.
This decision removes one provider family. It changes neither PTC execution nor the shared filesystem, subprocess and terminal interfaces. Direct Node confinement and validation of program-authored control traffic require their own implementation and evidence.
Alternatives considered
Retain E2B and refuse the control-channel request. This preserves the existing remote functionality with little new transport code, but retains its SDK and remote lifecycle obligations while excluding the new execution capability. Retirement makes that maintenance tradeoff explicit.
Multiplex the channel over E2B standard streams. A relay can frame stdin/control input and stdout/stderr/control output. It also needs channel-specific flow control and closure, bounded queues, and a solution to cumulative SDK output retention. These are remote transport semantics, not descriptor plumbing.
Use a separate authenticated stream. This can avoid the SDK's retained-output path and let control traffic progress independently. It adds endpoint access, authentication, network policy, startup coordination and connection-failure cleanup. The removal does not introduce that transport.
Make terminal operations synchronous. This simplifies local wrappers but removes delayed-operation behavior needed by remote providers. The shared asynchronous interface and its cancellation/ordering tests remain useful independently of E2B.
Consequences
Custom compositions that depend on the repository's E2B packages lose that supplied backend. External adoption is unknown. Removing the integration also removes its live remote composition evidence; remaining local and delayed-provider tests protect their own contracts, not an unimplemented replacement.
The native containment, outbound proxy and workspace-file service decisions remain active. Their E2B implementation and verification inventories are retired while their process ownership, routing and file-access requirements remain intact. The portability decision is partially superseded only in its E2B realization.
Reintroduction conditions
A remote provider needs a concrete execution use case and evidence for shared file/process coordinates, policy enforcement, bounded transport retention, independent control progress, precise channel closure and managed cancellation. Source and built compositions must exercise those behaviors. A connection loss cannot justify replaying a possibly executed program or claiming unobserved cleanup succeeded.
The POSIX SSH providers use binary channels outside the E2B command SDK's retained-output path. Ordinary SSH exec does not map arbitrary child descriptors, so their remote helper owns control-stream bridging, file semantics, process lifetime and remote policy enforcement. That implementation uses the retained interfaces; the E2B integration remains retired.
Verification
The removal inventory finds no live E2B package, workflow, import, dependency or catalog entry. Every surviving lockfile importer and package resolution matches its original value. The shared subprocess and terminal implementation, delayed-provider tests and PTC source are unchanged.
The remaining filesystem, subprocess, Bash, terminal and LSP suites pass alongside the affected generator and workflow tests. pnpm run build, pnpm run test:docs, pnpm run doc-sync, pnpm run lint and pnpm run hygiene pass for the removal. These checks validate the resulting tree; deleted E2B tests provide no evidence for it.
中文
问题
E2B 实验为文件工具、Bash、PTY 和语言服务器提供了一个远程文件系统／进程世界，而 Harness、凭据、模型传输和会话状态留在宿主。三个提供方证明，这些消费方可以共享现有文件系统与子进程接口，无需特定于提供方的工具。
PTC Node 约束需要独立于任意程序 stdin/stdout/stderr 的双向控制通信。固定版本的 [email protected] SDK 提供标准进程流与 PTY 输出，没有额外描述符传输。在 VM 中创建描述符不会使其暴露给 Harness 宿主；必须通过远程中继或独立的认证流进行桥接。
这样的桥接负责输出阻塞时的独立推进、有界保留、通道关闭、启动发布、命令身份、取消和断线清理。即使消费方施加反压，SDK 仍保留完整的 stdout/stderr，因此仅限制流级队列无法约束宿主内存。扩展这一适配器会把实验变成独立的远程传输项目。
决策
仓库不包含 E2B 沙箱所有者、文件系统提供方和子进程提供方，也不包含其 SDK 依赖、集成 fixture、可选工作流和生成注册项。仓库不提供 E2B 执行后端。移除用放弃该集成换取更小的维护范围；这不意味着 E2B 无法支持合适的传输，也不意味着已发布包没有外部用户。
可移植执行世界决策继续负责 ctx.fs 与 ctx.subprocess 的约定。两者描述同一个路径命名空间与进程世界。提供方负责路径转换、可执行文件查找、普通流、终端分配和受管清理；消费方保留工具语义、策略和呈现。local/remote 元数据标签不会为这些操作增加权限依据。
远程执行仍是预期能力。终端分配、写入、前台检查和信号发送保留 Promise 约定，以及待处理操作的取消保证。本地实现同步完成这些调用，不足以支持移除远程提供方所需的异步行为。进程完成、终端就绪判断、模拟器解析和受管范围停稳也保留现有职责归属。
本决策移除一个提供方族。它既不改变 PTC 执行，也不改变共享文件系统、子进程和终端接口。直接 Node 约束与程序生成的控制通信验证需要各自的实现和证据。
考虑过的替代方案
保留 E2B 并拒绝控制通道请求。 这只需少量新传输代码即可保留现有远程功能，但仍保留 SDK 与远程生命周期维护责任，同时排除新的执行能力。移除明确表达这一维护取舍。
通过 E2B 标准流多路复用通道。 中继可以对 stdin/control 输入和 stdout/stderr/control 输出分帧。它还需要逐通道流量控制与关闭、有界队列，以及累计 SDK 输出保留的解决方案。这些是远程传输语义，不是描述符接线。
使用独立的认证流。 这可以避开 SDK 保留输出的路径，并让控制通信独立推进。它增加端点访问、认证、网络策略、启动协调和连接失败清理。本次移除不引入该传输。
把终端操作改为同步。 这可以简化本地包装，但会移除远程提供方需要的延迟操作行为。共享异步接口及其取消／排序测试在没有 E2B 时仍然有用。
后果
依赖仓库 E2B 包的自定义组合失去该后端。外部采用情况未知。移除集成也会移除其真实远程组合证据；保留的本地与延迟提供方测试保护各自约定，并不验证尚未实现的替代方案。
原生约束、出站代理和工作区文件服务决策保持有效。它们的 E2B 实现与验证清单被撤下，进程所有权、路由和文件访问要求保持完整。可移植性决策仅有 E2B 实现部分被取代。
重新引入条件
远程提供方需要具体的执行用例，并证明共享文件／进程坐标、策略强制、有界传输保留、独立控制推进、精确通道关闭和受管取消。源代码与构建后组合必须执行这些行为。连接丢失不能成为重放可能已执行程序的理由，也不能据此声称未观察到的清理已经成功。
POSIX SSH 提供方使用独立于 E2B 命令 SDK 累计输出保留路径的二进制通道。普通 SSH exec 不映射任意子进程描述符，因此其远端辅助程序负责控制流桥接、文件语义、进程生命周期及远端策略执行。该实现使用保留的接口；E2B 集成继续退役。
验证
移除清点未发现有效的 E2B 包、工作流、导入、依赖或目录条目。锁文件中每个保留的 importer 与包解析结果都保持原值。共享子进程与终端实现、延迟提供方测试和 PTC 源代码保持不变。
保留的文件系统、子进程、Bash、终端与 LSP 套件，以及受影响的生成器与工作流测试均通过。移除后的 pnpm run build、pnpm run test:docs、pnpm run doc-sync、pnpm run lint 与 pnpm run hygiene 均通过。这些检查验证得到的代码树；已删除的 E2B 测试不为其提供证据。