Files

alexion 6081e3e325 chore(vendor): import pi 1.3.0

Imported as a linear vendor commit so forge rebases do not replay the upstream root tree.

git-subtree-dir: third_party/pi

git-subtree-split: 71023aec1546d6d677a65669c5665c0927ce0dd0

2026-10-15 17:58:48 -04:00

agent

chore(vendor): import pi 1.3.0

2026-10-15 17:58:48 -04:00

sandbox

chore(vendor): import pi 1.3.0

2026-10-15 17:58:48 -04:00

README.md

chore(vendor): import pi 1.3.0

2026-10-15 17:58:48 -04:00

README.md

pi-codemode on Cloudflare

This example has two Workers:

sandbox/ deploys CodemodeSandboxDurableObject as its own Worker, pi-codemode-sandbox. Scripts run there, in a separate isolate.
agent/ has a Session Durable Object that owns the tools. It runs scripts through RemoteCodemodeSandbox, which keeps the tools and results in Session while the sandbox Worker runs the VM.

The README of the package explains why the sandbox must be a separate Worker, and which limits apply.

Try it locally

Install @earendil-works/pi-codemode and wrangler in each directory, then start both Workers in one process:

npx wrangler dev -c agent/wrangler.jsonc -c sandbox/wrangler.jsonc
curl -X POST http://localhost:8787 --data 'const n = await tools.count({ add: 2 }); text("n=" + n); return n'

Deploy

Deploy the sandbox first, because the agent's binding refers to it by name:

(cd sandbox && npx wrangler deploy)
(cd agent && npx wrangler deploy)