Yes, you can now order DoorDash from the command line

We have spent the last decade complaining about the friction of mobile apps. We hate the notifications, the endless updates, and the cluttered interfaces. But the reality is that those apps were designed for human eyes and human fingers. Now, the landscape is shifting. DoorDash just announced a limited beta for a command-line interface, which they are calling dd-cli. It is exactly what it sounds like: a way to order a burrito without ever leaving your terminal.

The End of the Shiny Interface

For a founder, this is a signal that the era of the 'shiny wrapper' is dying. We are moving into a period where the back-end utility of a service is more important than the front-end aesthetics. This tool allows developers or, more importantly, AI agents to search local stores, add items to a cart, and execute a checkout through a text-based environment.

If you are building in the crypto or AI space, you should pay attention to this. We have been talking about 'agentic workflows' for a year now, but mostly in the context of writing code or organizing spreadsheets. DoorDash is moving this concept into the physical world. They are essentially providing a standardized API-as-a-tool for autonomous actors. This isn't really for the guy who thinks it is cool to order pizza from Linux; it is for the bot that knows you are hungry and busy, and decides to handle the logistics for you.

Why Builders Should Care

When I look at this from a founder's perspective, I see two major shifts. First, the 'user' is no longer a person. When you build software today, you have to ask yourself if your product can be effectively navigated by a Large Language Model. If your service requires a human to click a specific red button to work, you are building a legacy product. DoorDash is essentially stripping away the fluff to make their service digestible for machines.

Second, this opens up a massive opportunity for integration. Imagine a decentralized autonomous organization (DAO) hosting a hackathon. You could theoretically write a script that monitors the progress of the developers and automatically triggers a catering order once a certain amount of code is pushed to GitHub. This bridges the gap between digital triggers and physical fulfillment.

• Efficiency over Aesthetics: The terminal is faster than a web browser. For power users and agents, speed is the only metric that matters.
• Programmable Logistics: We are looking at the beginning of a world where logistics are just another line of code.
• Market Expansion: By allowing agents to spend money, companies like DoorDash are tapping into a new class of consumer that doesn't get tired or distracted.

The Skeptical Take

I have to be honest: there is a lot of room for this to go wrong. If you give an AI agent the ability to spend your money via a command line, you better have some damn good guardrails in place. We have seen what happens in the crypto world when a smart contract has a bug; now imagine that bug results in fifty bags of McDonald's showing up at your front door because a bot got stuck in a loop.

The transition to agent-first software requires a level of security and verification that most consumer companies aren't prepared for yet.

There is also the question of the 'walled garden' problem. DoorDash is doing this because they want to be the default infrastructure for automated food delivery. But as a builder, you have to wonder if we are just trading one type of platform dependency for another. If your agent relies on a proprietary CLI to function, you are beholden to their updates, their fees, and their uptime.

The Crypto Connection

In the blockchain world, we have been building 'headless' applications for years. A smart contract doesn't care if you have a pretty UI; it just cares if the transaction is signed correctly. DoorDash's move is a massive validation of this philosophy. They are acknowledging that the future of commerce is decentralized in its execution, even if the service itself is centralized. We are seeing a convergence where 'real world' companies are adopting the developer-first, machine-readable standards that define the Web3 ecosystem.

If you are a developer, this is your cue to start thinking about 'Agentic APIs.' Don't just build a dashboard. Build a way for software to talk to your software without a middleman. The companies that win the next decade will be the ones that make it easiest for bots to buy their products.

The Long Game

This isn't just about food. This is about any service that can be reduced to a set of commands. Grocery delivery, ride-sharing, and even home maintenance are likely next. We are building a world where the operating system is the commerce layer. The command line was the original interface of the computer, and it is ironic that we are returning to it to solve the problems of the modern AI era.

For those of us in the trenches building these tools, the takeaway is clear: stop obsessing over how things look and start focusing on how they can be programmed. The most valuable users of the future won't have eyes; they will have API keys.

DoorDash is taking a gamble that developers want to integrate food delivery into their dev environments and autonomous agents. It is a smart bet, but it requires a complete rethink of how we handle payments, security, and user intent. It is a step toward a much more efficient world, even if it feels a little cold and mechanical at first glance.

The Final Word for Builders: Start treating your service as a set of programmable actions. If an AI agent can't use your product, eventually, humans won't either.

---

Read the original at TechCrunch AI →