Why Coding Agents Need a Computer That Isn't Your Laptop

The coding harness is becoming a work environment #

In January I argued that work expressible as code can be done by LLMs. Two months later, that hypothesis keeps holding up. I underestimated how fast the same agent harness that writes software would absorb the rest of knowledge work, and how urgently it needs infrastructure beyond a laptop.

I built the AWS Diagram MCP server twelve months ago. It’s still one of the more popular ones. Last night I was using it with Opus 4.6 inside Claude Code to draw architecture diagrams for a review, and the model hit the MCP server’s constraints. So it opted out. Opus 4.6 bypassed the MCP server entirely, used the full Python diagramming library in its sandbox, and produced the diagrams itself on the first attempt.

We thought we’d need to handcraft deterministic tools for AI. The frontier model looked at the rigid tool, looked at the Python sandbox it already had, and decided it could do the job better itself.

This pattern repeats across every category of work I’ve tested. Financial analysis: Claude Code calling the Yahoo Finance API and SEC Edgar SDK, running calculations in Polars, producing verified output I can trace through the code.1Yahoo Finance API and SEC Edgar (edgartools), open-source Python SDKs for real-time financial data, SEC filings, and company disclosures.https://github.com/dgunning/edgartools Conference data analysis: hand it a re:Invent survey dataset with a one-sentence instruction; it built six Excel sheets with IFERROR formulas, conditional formatting, bar gradients inside cells, and CSAT breakdowns by time of day and day of week. Diagrams, financial research, data analysis, and infrastructure cost modeling are all code tasks now, executed through the same agent harness that ships pull requests.

Anthropic’s Cowork product validates this convergence. By their own description, Cowork is a thin interface wrapped around Claude Code.2Anthropic, "Introducing Cowork," a collaborative interface built on Claude Code for knowledge work beyond software engineering.https://claude.com/blog/cowork-research-preview The same runtime that writes your software also runs your quarterly analysis.

From model capability to runtime design #

If the coding agent harness generalizes to most digital knowledge work, the question shifts from “how good is the model” to “where does the agent run.”

Today, over 40% of experienced Claude Code users operate in full auto-approve mode, meaning full autonomy, with the agent deciding when to stop.3Anthropic, "Measuring AI agent autonomy in practice." Among experienced users, over 40% of sessions use full auto-approve; session durations nearly doubled from <25 to >45 minutes (Oct 2025 to Jan 2026).https://www.anthropic.com/research/measuring-agent-autonomy More autonomy extracts more value. It also demands more compute, longer sessions, and wider permissions, all running on a personal laptop.

Isolation, durability, and portability #

Three constraints make laptops untenable at team scale.

Portability. Developers build rich information environments around their coding agents: CLAUDE.md files, MCP servers, custom tooling, project-specific context. These don’t transfer cleanly between machines or teammates. “My Claude builds better than your Claude” is a joke that describes a configuration-drift problem across engineering teams.

Durability. Laptops sleep, lose power, and run out of memory mid-task. A greenfield agent session runs 30–60 minutes. A brownfield task with a codebase refresh takes longer. An end-to-end test suite adds more time on top. These runs need to complete without interruption.

Isolation. An autonomous agent with full disk and network access on your primary machine is a security trade-off most teams shouldn’t accept. Developers are buying dedicated Mac Minis just for Claude Code, disposable machines where a rogue rm -rf doesn’t touch their actual work environment.4Mac Mini as dedicated AI coding hardware, an observed pattern across developer communities. Hacker News, X/Twitter, Reddit r/ClaudeAI discussions on dedicating secondary machines to autonomous agent workloads.Community sources

When developers buy dedicated hardware for their AI agents, they’re buying compute and solving for isolation, durability, and scale with consumer electronics. That’s a demand signal.

Cloud infrastructure resolves all three constraints. Isolation: every session gets its own sandbox. Durability: the session outlives any power failure or network blip. Scale: dispatch ten tasks from Slack, each on its own instance, while you’re doing something else entirely.

The experience I want is to describe a bug in Slack. The agent diagnoses it, reads the code, writes a fix, runs the test suite, opens a PR. I review when I’m ready. I want ten of these running concurrently, started from my phone.

Startups see the gap and are raising money on it. E2B runs Firecracker micro-VMs for agent sandboxes.5E2B, "Cloud Sandboxes for AI Agents," a Firecracker micro-VM runtime for isolated, ephemeral agent execution environments. $35M raised, Series A led by Insight Partners.https://e2b.dev/blog/series-a Daytona raised $24M in February 2026 on the thesis that agent-native sandboxes are the next infrastructure primitive.6Daytona, $24M Series A, February 2026, led by FirstMark Capital. Agent-native sandbox infrastructure with 90ms cold start, forkable persistent state, and snapshot/branch mid-execution.https://www.daytona.io/dotfiles/daytona-raises-24m-series-a-to-give-every-agent-a-computer Fly.io launched Sprites: persistent Linux VMs on Firecracker that create in two seconds, auto-sleep when idle, and cost $0.44 for a four-hour Claude Code session.7Fly.io, "Code And Let Live" (Sprites launch). Persistent Linux VMs on Firecracker. 100GB durable filesystem, 1–2s creation, auto-sleep when idle. $0.07/CPU-hour. Launched January 2026.https://fly.io/blog/code-and-let-live/ Cursor ships background agents on Ubuntu EC2 instances.8Cursor, "Cloud Agents" (formerly Background Agents). Cloud-hosted agent execution on Ubuntu EC2 instances, running autonomously while the developer works elsewhere.https://cursor.com/blog/cloud-agents Buyers are showing up, and the implementations are converging on cloud compute with process-level isolation.

The enterprise proof points are arriving too. Stripe merges over a thousand agent-written pull requests per week on internal infrastructure.9Nader Dabit, Cognition AI, "How to Run a Fleet of Cloud Agents," March 2026. Reports Stripe merging 1,000+ agent-written PRs per week on internal infrastructure.https://nader.substack.com/p/how-to-run-a-fleet-of-cloud-agents Cognition’s Devin has shipped 1.2 million merged PRs across hundreds of organizations.10Cognition AI, Devin autonomous software engineer. 1.2 million merged pull requests across hundreds of organizations including Goldman Sachs, Citi, and Ramp.https://cognition.ai/ This is production-scale software delivery, well past the pilot stage.

Choose the runtime your team can operate #

The infrastructure underneath runs along a spectrum, and teams should pick based on where they already are. Vanilla EC2 AMIs are simple, proven, and sufficient for teams under a hundred agents; Cursor appears to be here today. Firecracker micro-VMs on EC2 bring sub-second cold starts and higher bin-packing density, worth the engineering investment at thousands of concurrent agents; E2B and AgentCore live here. Kubernetes on EKS is the natural extension for teams already running multi-cluster operations. Managed runtimes like AgentCore offer the lowest operational overhead and fastest on-ramp for teams that want to skip the infrastructure work.11Amazon, "Bedrock AgentCore," a managed agent runtime with Firecracker-based isolation, session persistence, and tool orchestration.https://aws.amazon.com/bedrock/agentcore/

The correct strategy is to make every path obvious and well-lit rather than pick one.

There’s a flywheel underneath this. Agents running in the cloud consume inference, compute, and storage. Better infrastructure makes agents more effective. More effective agents drive more usage. More usage drives more compute and inference demand.

We used to say data has gravity, meaning workloads move to where data lives. That framing is inverting. If cloud-native agent infrastructure is meaningfully better than a laptop, and the gap widens every month, then data follows agents rather than the reverse. Call it agent gravity.