Claude 4 API: Tool Use Streaming & Prompt Caching vs Modal Labs Sandboxed Code Execution API

“The primitive here is clean: incremental tool-call deltas over SSE, and a cache-control header you attach to prompt segments to pin them server-side. The DX bet is that complexity lives in the HTTP layer, not in a new SDK abstraction — you opt in per-request, no new mental model required. The moment of truth is calling `stream=true` on a tool-use request and watching partial JSON arguments arrive before the model finishes thinking, which actually matters for agent loops where you want to dispatch work early. This is not a weekend-script replacement — implementing correct incremental JSON parsing for partial tool arguments plus a reliable distributed cache with 2M token capacity is a real engineering problem Anthropic has solved for you. The specific decision that earns the ship: cache invalidation is explicit and cache hits are reflected in the usage object, so you can actually measure what you're saving instead of guessing.”

“The primitive here is clean: ephemeral container spawn, code in, result out, billed by the second. The DX bet Modal made is that developers shouldn't have to think about container lifecycle, networking, or cleanup — and they're right. The moment of truth is `modal.Sandbox.create()`, and it survives: secrets inject cleanly, resource limits are set at call time, not in a config file, and the sandbox tears down automatically. You could replicate this with Firecracker microVMs, some Lambda plumbing, and a weekend — but you'd also spend the next month debugging cold starts and network egress. The specific decision that earns the ship: resource limits are first-class parameters in the API call, not an afterthought in a YAML manifest somewhere.”

“Direct competitors are OpenAI's cached completions and Google's context caching in Gemini 1.5 — both shipping for months — so Anthropic is catching up, not leading. The specific scenario where this breaks: cache hit rates depend entirely on prompt structure, and developers who dynamically compose system prompts (inserting user-specific context at the top) will see near-zero cache utilization and pay full price while assuming they're saving money. The prediction: this feature doesn't get killed — it becomes table stakes infrastructure and Anthropic wins by having the largest cache window (2M vs. competitors' current limits). What would have to be true for me to be wrong: OpenAI ships a 10M token cache window before Anthropic's ecosystem matures, commoditizing the advantage. Still a ship because the streaming tool-use delta is genuinely differentiated — no competitor has clean partial-argument streaming for tool calls yet, and that changes agent loop architecture in ways that matter.”

“The direct competitor is E2B, which has been doing sandboxed code execution for agents longer and has a larger community. Modal wins on infrastructure maturity — their container cold start story is genuinely better than most, and the secret injection model is cleaner than E2B's current approach. Where this breaks: long-running agent workflows that need persistent filesystem state across multiple sandbox calls will hit friction fast, because Modal's ephemerality is a feature until it isn't. What kills this in 12 months isn't a competitor — it's that OpenAI and Anthropic both ship native code execution environments inside their agent frameworks, commoditizing the standalone sandbox market. Modal survives only if they've built enough workflow lock-in through the broader platform before that happens.”

“The thesis this bets on: by 2027, the dominant AI application architecture is a persistent agent with a large, stable context (tools, memory, instructions) that gets reused across thousands of user interactions — making context I/O cost the primary unit economics lever, not generation cost. The dependency that has to hold: agents don't collapse back to stateless chatbots, and context windows keep growing faster than per-token prices fall. The second-order effect nobody's talking about: prompt caching at 2M tokens makes it economically viable to give every enterprise user a fully-loaded, role-specific agent context at request time — which shifts competitive differentiation from 'who has the best model' to 'who has the best cached context corpus,' effectively making knowledge curation the new moat. This tool is riding the trend of context-window expansion-as-infrastructure, and it's on-time, not early — but the streaming tool-use primitive is ahead of the curve on agent loop efficiency. The future state where this is infrastructure: every production agentic system has a cache manifest the same way it has a CDN config.”

“The thesis here is falsifiable: within 2 years, most AI agents will need to execute code as a core capability, and the teams building those agents won't want to own execution infrastructure. That bet is on-time, not early — the agentic coding wave is already visible in Devin, Claude's computer use, and every copilot that runs tests. The second-order effect that matters isn't faster code execution — it's that safe sandboxing lowers the activation energy for agents to attempt side-effectful actions, which expands what agents can be trusted to do autonomously. The dependency that has to hold: agent frameworks must stay polyglot and API-driven rather than consolidating into vertically integrated stacks that bundle their own execution. If LangChain or the next dominant framework ships a native sandbox, Modal needs the broader platform relationship to matter more than this single API.”

“The buyer is the engineering team at any company running Claude in production with long system prompts or multi-step agents — this comes out of the AI infrastructure budget, not a new budget line, which means no procurement friction. The pricing architecture is sound: cache reads at ~90% discount means the savings are real and measurable in the first billing cycle, which creates immediate retention — developers who restructure prompts to maximize cache hits are now architecturally coupled to Anthropic's caching implementation. The moat question is the honest one: this is infrastructure that OpenAI and Google will match, so the defensible position isn't the feature itself but the ecosystem of developers who've restructured their codebases around it. What survives a 10x model price drop: the streaming tool-use architecture, because that's about latency, not cost. The specific business decision that makes this viable is pricing cache reads as a separate SKU — it lets Anthropic capture value from high-volume production workloads without losing price-sensitive experimenters.”

“The buyer is a developer or ML engineer at a company building an AI agent product, pulling from an infra or tooling budget — this is a real buyer with a real check. The pricing architecture is Modal's standard compute billing, which scales with usage and aligns cost with value delivered, though it can surprise teams at scale who don't instrument their sandbox call frequency. The moat concern is real: this is one API surface on top of Modal's broader platform, and the defensibility comes from Modal's overall container infrastructure quality and the stickiness of platform-level billing consolidation, not from the sandbox feature alone. The business survives model commoditization because Modal is selling compute, not intelligence — when models get cheaper, agents run more sandboxes, not fewer.”