The CLI is the new API

Neal Stephenson once argued that the GUI was built to save users from the command line—an interface that, in Stephenson’s words, “cruelly punished laziness and imprecision.” Billions were spent on that project. It worked. Now, agents have arrived: software that’s never lazy, never imprecise about syntax, and doesn’t need protecting from demanding interfaces.

SaaS companies noticed. In the past 90 days, a wave of them shipped CLIs built specifically for agents—not for developers.

The CLI is the interface layer that determines whether a product is in the agent workflow. It’s what the API was in the 2010s—the line between connected and irrelevant.

Two waves got us here.

The first was the AI coding agents. Anthropic shipped Claude Code CLI in May 2025. Google followed with Gemini CLI in June. OpenAI launched Codex CLI in October. Mistral shipped Vibe CLI in December. GitHub and Microsoft brought Copilot CLI to general availability in February 2026. These aren’t products with CLI wrappers bolted on—the CLI is the product. Agents operate in terminals, reading flags, parsing output, and chaining commands. The terminal is the native environment for software operating on software.

That wave established the pattern. The second wave is SaaS companies responding to it.

Twenty days after Google Workspace CLI shipped, 37signals released a Basecamp CLI with 55+ commands and a Claude Code skill bundled in. DHH’s framing: “This is where the puck is going, and we’re skating to meet it.” On March 27, Stripe launched Projects CLI for agent-driven infrastructure provisioning. Vercel shipped agent-optimized CLI commands with JSON output formatted for machine consumption. Polymarket built a CLI explicitly for AI agent accessibility. The Register ran a piece on March 11 titled “AI has made the CLI more important and powerful.”

The sharpest detail in DHH’s announcement wasn’t the feature count. The Basecamp API has existed for years. DHH’s description of how many customers used it: “A vanishingly small portion.” The same API, rewrapped as a CLI with a skill bundled in, is what he expects agents to use at scale—not because humans will start typing commands, but because agents are already running them everywhere.

The fallback, when there’s no CLI, is browser automation—agents navigating GUIs the way a human would, via screenshots and simulated input. On WebVoyager, a controlled benchmark using cooperative, non-adversarial test sites, the best browser agents scored around 89% (December 2024). On WebArena, which tests against real-world web tasks, the best models scored 35.8% (arXiv, October 2024), and those numbers drop further in production. The CLI scores 100% on authentication—it was designed for this.

The CLI fits into programmatic workflows. The surface area is discoverable: --help exposes what’s available without requiring a human to navigate a UI or read documentation, which matters when the consumer is code rather than a person. Output arrives as structured text or JSON rather than a rendered visual state that requires interpretation—parse it directly, pipe it to the next tool, done. Shell pipes and scripts give CLI commands interoperability that has to be engineered separately for every other interface type.

On the builder side, the calculus is simpler: one binary instead of SDKs across languages, --help as the documentation, and a stable interface that wraps the API and insulates internal architecture from whatever is consuming it.

The API was the interface that determined whether your product was part of the connected web. Stripe’s 2011 launch reduced weeks of bank approvals, processor agreements, and gateway configuration to seven lines of code. What PayPal required of developers—“a dinosaur and a nightmare to work with,” as it was described in developer communities—Stripe replaced with a curl command that returned a successful charge in seconds. Twilio did the same thing to communications infrastructure. Neither company won on features. They won on the quality of their interface. The CLI is doing that now. It’s the interface layer that determines whether your product’s in the agent workflow or outside it—and once agents are in the workflow, the question of how they pay is next.

The Notion situation shows what “outside it” looks like. Notion has no official CLI. GitHub has at least ten community-built unofficial ones, several explicitly designed for Claude Code and AI agents. One describes itself as “built for developers and AI agents who need programmatic access without the browser.” Another offers recovery hints on errors and structured JSON output designed for agent parsing.

The wrapping happens regardless. The question is who controls the interface—the product team or whoever got there first.