GPT-5.6 Writes JavaScript to Orchestrate Its Own Tool Calls

Every tool result round-tripping through the model is a tax you've been paying without noticing.

OpenAI's Responses API now ships Programmatic Tool Calling. The model writes JavaScript that coordinates your tools. It calls them in parallel, loops over results, branches on conditionals, and holds intermediate values in a hosted V8 runtime. Those intermediate values never pass back through the model's context. Only the final result does.

Think about what that kills. The classic agentic pattern is: model calls tool, tool returns 4,000 tokens of JSON, model reads all 4,000 tokens, model calls the next tool, repeat. Thirty tools deep and you've burned 120,000 input tokens re-reading data the model already decided what to do with. Programmatic tool calling lets the model say "fetch these forty records, filter to the ones where status is failed, call the remediation tool on each," and none of the forty records ever enter the context window.

The sandbox is deliberately thin, and the constraints tell you exactly which workflows qualify. Top-level await works. There's no Node.js, no package installation, no network access, no filesystem, no subprocess, and no state persistence between programs. So: no fetching data outside your declared tools, no npm, no writing a scratch file. It's a pure orchestration layer over the tools you already gave it.

That means this is for bounded, tool-heavy workflows where the model doesn't need fresh judgment at every step. Data reconciliation. Batch remediation. Fan-out queries against a set of known endpoints. It's not for tasks where each tool result should genuinely change the plan, because the model isn't looking at the intermediate results.

I've been building a research pipeline that dispatches thirteen agents and merges their findings, and roughly a third of my token spend is the merge step re-reading what the agents produced. That's exactly the shape this targets. I haven't ported it yet. I'm suspicious of any abstraction that moves control flow into generated code I don't review, and "the model wrote a loop" is a sentence that should make you check the loop.

Connect this to Sam Altman at Sun Valley on July 10, telling CNBC that this is the first year AI spend has been a "very big topic" among attending CEOs, with "everyone asking what we can do to help reduce spend or increase value." He pitched GPT-5.6 as the answer, on agentic coding efficiency rather than raw capability. Programmatic tool calling is the mechanism behind that pitch. The buyer conversation flipped from "how smart is it" to "what does a task cost," and the labs are shipping architecture, not just weights, in response.

What to do: audit one agent loop for tool results the model reads but doesn't reason about. That's your candidate. If you find a step where the model's only job is to pass data from tool A to tool B, you just found free money.