← X

@andyfang brb downloading

X · bcherny · July 15, 2026
A DoorDash CLI tool enabling AI agents to place food orders was announced, generating mixed reactions from users ranging from enthusiasm to skepticism about its practical utility. Several users reported successful testing of the agent-based ordering system and expressed interest in beta access to the feature. The release sparked discussion about agentic AI's capabilities for real-world service integration and concerns about prompt injection vulnerabilities in automated food delivery scenarios.

Detailed Analysis

DoorDash co-founder Andy Fang's announcement of "dd-cli," a command-line interface allowing AI agents to place food delivery orders directly from a terminal, triggered a flood of reactions that reveal both enthusiasm and skepticism surrounding the rapidly expanding "agentic commerce" movement. The tool appears designed to integrate with agentic coding environments like Claude Code, enabling developers to order food without leaving their development workflow—epitomized by one commenter's quip about running "git commit && dd-cli order coffee while the build runs." The replies show a mix of genuine excitement (people signing up for waitlists, requesting Android control, and asking about beta access) and pointed criticism about whether the feature solves a real problem or represents feature-chasing by a company entering the AI agent space alongside API providers like Anthropic and Moonshot AI (whose Kimi model is repeatedly referenced as an alternative agent capable of placing orders).

The technical debate embedded in the thread is particularly telling of where the developer community's head is at regarding agent tooling standards. Multiple replies specifically ask why DoorDash chose to ship a standalone CLI rather than an MCP (Model Context Protocol) server—Anthropic's open standard for connecting AI models to external tools and data sources. This distinction matters: MCP has emerged as the preferred architecture for agent-tool integration because it allows any MCP-compatible model (including Claude) to discover and invoke capabilities dynamically, whereas a bespoke CLI requires manual scripting or shell-execution wrappers to be useful inside an agentic workflow. The question "why present your CLI tools with Claude Code" underscores how thoroughly Claude Code has become the default demonstration environment for real-world agent capabilities, even for products built by outside companies.

Beyond the technical architecture debate, the thread captures a broader cultural moment: skepticism about whether "agentic everything" is meaningful innovation or bandwagon-chasing. Comments range from dismissive ("just a vanity project," "proof you're out of ideas") to darkly comedic speculation about failure modes—repeated jokes about prompt injection attacks causing agents to order "100 pizzas" or "17 extra-large pineapple and anchovy pizzas" highlight genuine, if humorously framed, security concerns about giving autonomous agents access to real-world purchasing power. This tension—between excitement over agents that can "securely interact with real-world services" representing "a completely different computing paradigm" and legitimate worry about unverified, injectable actions with financial consequences—mirrors the exact debate playing out across the AI industry as companies push from chatbots toward action-taking agents.

This moment fits squarely within 2025-2026's dominant AI narrative: the shift from conversational assistants to agents that execute real-world tasks via APIs, browsers, and now consumer commerce platforms. Anthropic's own push with Claude's computer-use capabilities, MCP standardization, and Claude Code's popularity as an agent-building sandbox has made "can my AI order me lunch" a natural extension of what agentic AI is expected to do. That competitors in India (Swiggy, Zomato) reportedly built similar functionality first, and that commenters are already requesting equivalents from Expedia and Booking.com, suggests agentic commerce integrations are quickly becoming table stakes across consumer-facing platforms rather than a novelty—even as the industry hasn't yet resolved fundamental security questions about letting language models autonomously spend money on users' behalf.

Read original article →