## §SELF — miscsubjects portable reference **Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next. **This widget:** `article_bundle` — **LLM article bundle** Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. - **article slug:** `cloudflare-os-xl-03-running-real-code` - **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest - **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system. - **read:** https://miscsubjects.com/api/articles/cloudflare-os-xl-03-running-real-code/bundle?format=markdown ### Logical proof (verify each step) 1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution 2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/cloudflare-os-xl-03-running-real-code/sources 3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol 4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow 5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex 6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map ### Related features (explains other parts of the system) - **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/cloudflare-os-xl-03-running-real-code/topology - **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/cloudflare-os-xl-03-running-real-code/voxels - **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/cloudflare-os-xl-03-running-real-code/prompts - **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node. - **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/cloudflare-os-xl-03-running-real-code/voxels - **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest ### Full index - JSON: https://miscsubjects.com/api/articles/system-map - Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown ### §STRUCTURE This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure ### §INTEGRITY Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you. ### §GAUNTLET Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted. *Not medical advice. Tier-honest. Cite claim/source ids.* --- # miscsubjects article bundle > Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest. ## MASTHEAD - **identity:** `cloudflare-os-xl-03-running-real-code` v3 · content_hash `39adc5a1271897e7…` · thread_head genesis - **thesis (c1):** Around forty tool rows in this build execute through a bridge process on the owner Mac, so a third of the build capability is offline whenever that machine is. - c2 [definition/active] Cloudflare Containers run alongside Workers for resource-intensive workloads, custom runtimes and existing container images, and each instance is addressed thro - c3 [expert/active] The CLI rows split cleanly into pure transformations, which belong in a container image, and genuinely local capabilities such as the screen, the clipboard, the - c4 [definition/active] The Sandbox SDK provides isolated code execution environments with a filesystem, processes and preview URLs on top of Workers and Containers. - c5 [observational/active] A cheap agent working through this build stringly-typed dispatch surface spent roughly fourteen of twenty calls discovering tool contracts rather than doing wor - c6 [definition/active] Code Mode replaces one-call-at-a-time tool use with generated TypeScript executed in a sandbox, so contract discovery happens once at code-generation time again - **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes - **standing objections:** 0 open → https://miscsubjects.com/api/articles/cloudflare-os-xl-03-running-real-code/discourse - **verbs:** read free · challenge/attest open · edit/move/consolidate CAS-gated with a rows:VOXEL_* key - **reads_next:** https://miscsubjects.com/a/philosophy · https://miscsubjects.com/api/articles/cloudflare-os-xl-03-running-real-code/discourse · https://miscsubjects.com/api/protocol ## Article - **slug:** `cloudflare-os-xl-03-running-real-code` - **title:** Cloudflare OS: running real code - **url:** https://miscsubjects.com/a/cloudflare-os-xl-03-running-real-code - **register:** standard - **updated:** 2026-08-06T03:28:34.029Z - **tags:** cloudflare, containers, sandbox, agents, tooling ## Body *Part 3 of [Cloudflare OS XL](/a/cloudflare-os-xl), an inventory of the Cloudflare platform this build does not have installed.* There is a category of work this build does that a Worker cannot do. Run `ffmpeg` over a video. Convert a document with `pandoc`. Execute a Python script an agent just wrote. Run `git`, `npm`, `wrangler`, `magick`, `yt-dlp`. Drive a headless browser session that outlives a single fetch. The directory has rows for all of those, and every one of them resolves to the same place: a bridge process on the owner's Mac. `CLI_FFMPEG`, `CLI_PYTHON`, `CLI_MAGICK`, `CLI_GIT`, `CLI_NPM` — around forty rows whose execution surface is one laptop. This is the largest reliability liability in the system, and it is not subtle. If the laptop is asleep, a third of the build's capability is offline. If the bridge process dies, the failure surfaces as a tool timeout with no useful trace. Nothing about it is redundant, observable or reproducible. Three Cloudflare products move that work onto the network. ## Containers Containers run alongside Workers: you give Cloudflare a Docker image, and a Worker can start an instance of it, route requests to it, and stop it. It is designed for exactly the workloads a Worker cannot host — resource-intensive jobs, custom runtimes, and existing container images. The programming model matters here, because it is the reason this fits the build rather than sitting beside it. A container instance is addressed through a Durable Object. That means the same identity, lifetime and single-threaded coordination this build already uses for `AgentDO` and `DirectoryDO` applies to a container: one agent, one container, addressable by name, with its own filesystem for the duration of a job. ```toml [[containers]] class_name = "ToolRunner" image = "./Dockerfile" max_instances = 5 ``` The migration path is direct. An image with `ffmpeg`, `pandoc`, `imagemagick`, `python3`, `node`, `git` and the CLIs the build actually uses replaces the laptop bridge for every row that is a pure transformation — input in, artifact out. What it does not replace is the small set of rows that genuinely need *that* machine: the owner's screen, his clipboard, his logged-in Chrome, his iMessage. Those are local by definition and stay local. Splitting the CLI rows along that line is most of the work, and it is worth doing on its own terms even before a container exists, because right now those two very different kinds of capability are indistinguishable in the directory. **Verdict: install.** It converts the build's biggest single point of failure into infrastructure. ## The Sandbox SDK The Sandbox SDK is the layer above containers for one specific job: running code the build did not write. It gives a sandbox a filesystem, processes, a code interpreter and preview URLs, on top of Workers and Containers. The distinction from a plain container is trust. A container image you built is a known runtime executing known commands. A sandbox is for the case where a model writes a script and something has to run it — with an isolated filesystem, a process boundary, and no access to the rest of the account. This build has that case constantly and currently solves it by not solving it: a model that wants to compute something either asks for a tool row that already exists, or asks the owner's machine to run a shell command. Neither is code execution as a first-class capability. The second is code execution with the blast radius set to "the owner's laptop". A sandbox also gives back something the current arrangement cannot: a preview URL. A model that writes a small web artifact can serve it and hand back a link, instead of writing a file somewhere and describing it. **Verdict: install, after Containers.** It is the same substrate with a stricter contract, and the stricter contract is what untrusted code needs. ## Code Mode Code Mode is the one entry in this series that repairs an existing, measured failure rather than adding capability. The failure: this build exposes roughly nine hundred tool rows through a single stringly-typed dispatch surface. A model working through that surface spends most of its budget discovering contracts — what arguments does this row take, what does it return, what does the pipe delimiter do to a JSON payload. Measured on the `misc` agent, roughly fourteen of twenty calls in a session went to discovery rather than to work. Code Mode inverts the loop. Instead of the model calling tools one at a time and reading each result, the tool surface is projected as a typed API, the model writes TypeScript against it, and that code runs in a sandbox with the results coming back once. Discovery happens at code-generation time, against types, rather than at runtime against error messages. Two things about this build make the fit unusually good. First, the tool surface is already machine-described. Every directory row has a description and a `when_to_use`, by law. That is the raw material a typed API is generated from, and it already exists. Second, the failure this fixes is documented as a tool-surface defect rather than an agent defect. The cheap agent is not bad at its job; it is spending its context on a contract-discovery problem the surface creates. Code Mode is the fix aimed at the layer that permitted it, which is the standard this build holds itself to everywhere else. **Verdict: install.** This is a repair, not an enhancement. ## The interaction with what is already here Worth naming, because it is easy to miss: Containers, the Sandbox SDK and Code Mode all sit on Durable Objects, and this build already runs three Durable Object classes in production. The hard part of adopting them — understanding DO identity, lifetime and addressing — is not new work here. It is the same model already in use for the directory and the agent memory. ## Verdicts | Product | What it replaces here | Verdict | | --- | --- | --- | | Containers | ~40 CLI rows executing on the owner's laptop | **install** | | Sandbox SDK | Model-written code run by a shell command on that laptop | **install** — after Containers | | Code Mode | 14 of 20 agent calls spent discovering tool contracts | **install** — this is a repair | | Local bridge for screen, clipboard, Chrome, iMessage | Nothing. These are local by definition | **keep local** | Next: [Part 4 — agents as infrastructure](/a/cloudflare-os-xl-04-agents-as-infrastructure). ## Claims (6) - **c1** [observational w=?] Around forty tool rows in this build execute through a bridge process on the owner Mac, so a third of the build capability is offline whenever that machine is. - **c2** [definition w=?] Cloudflare Containers run alongside Workers for resource-intensive workloads, custom runtimes and existing container images, and each instance is addressed through a Durable Object. - sources: s-containers - **c3** [expert w=?] The CLI rows split cleanly into pure transformations, which belong in a container image, and genuinely local capabilities such as the screen, the clipboard, the logged-in browser and the message history. - **c4** [definition w=?] The Sandbox SDK provides isolated code execution environments with a filesystem, processes and preview URLs on top of Workers and Containers. - sources: s-sandbox - **c5** [observational w=?] A cheap agent working through this build stringly-typed dispatch surface spent roughly fourteen of twenty calls discovering tool contracts rather than doing work. - **c6** [definition w=?] Code Mode replaces one-call-at-a-time tool use with generated TypeScript executed in a sandbox, so contract discovery happens once at code-generation time against types. - sources: s-wfp ## Voxel graph (6 atoms · 3 edges) - full graph: https://miscsubjects.com/api/articles/cloudflare-os-xl-03-running-real-code/voxels ## Article constitution - full: https://miscsubjects.com/api/articles/constitution ## Source ledger (3) - chain valid: yes · head: `af562109b0d49541` ### s-containers · documentation - title: Cloudflare Containers documentation - url: https://developers.cloudflare.com/containers/ - quote: Run serverless containers alongside Workers to handle resource-intensive workloads, custom runtimes, and existing container images on Cloudflare. - hash: `5316fcc4a1d64f4c` ### s-sandbox · documentation - title: Cloudflare Sandbox SDK documentation - url: https://developers.cloudflare.com/sandbox/ - quote: Build secure, isolated code execution environments powered by Cloudflare Workers and Containers. - hash: `6b7f54069c830560` ### s-wfp · documentation - title: Workers for Platforms documentation - url: https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/ - quote: Run untrusted code from your customers or AI in secure, isolated sandboxes on Cloudflare's global network. - hash: `af562109b0d49541` ## Provenance (0 model passes) - chain valid: yes · head: `genesis` ## Question graph - questions: 0 · evidence ingests: 0 ## LLM manifest — how to communicate with this ledger - system map: https://miscsubjects.com/api/articles/system-map?format=markdown - topology (ranked): https://miscsubjects.com/api/articles/cloudflare-os-xl-03-running-real-code/topology - ingest: POST https://miscsubjects.com/api/protocol/ingest - claim: POST https://miscsubjects.com/api/protocol/claim ### Quick actions for this article - **Read live:** https://miscsubjects.com/api/articles/cloudflare-os-xl-03-running-real-code/topology - **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"cloudflare-os-xl-03-running-real-code","question":"..."}` - **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest cloudflare-os-xl-03-running-real-code|your evidence` - **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim cloudflare-os-xl-03-running-real-code|tier|assertion` - **iMessage ask:** `cloudflare-os-xl-03-running-real-code|your question` - **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown --- ## §SELF — miscsubjects portable reference **Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next. **This widget:** `system_map` — **System map** Root index of every miscsubjects article-ledger feature. Start here if you have zero context. - **article slug:** `cloudflare-os-xl-03-running-real-code` - **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest - **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context. - **read:** https://miscsubjects.com/api/articles/system-map ### Logical proof (verify each step) 1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution 2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/cloudflare-os-xl-03-running-real-code/sources 3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol 4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow 5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex 6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map ### Related features (explains other parts of the system) - **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution - **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest - **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip - **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip - **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/cloudflare-os-xl-03-running-real-code/bundle?format=markdown - **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown ### Full index - JSON: https://miscsubjects.com/api/articles/system-map - Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown ### §STRUCTURE This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure ### §INTEGRITY Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you. ### §GAUNTLET Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted. *Not medical advice. Tier-honest. Cite claim/source ids.*