On July 16, 2026, TechCrunch reported a surprising development: DoorDash now offers a command-line interface (CLI) tool that allows users to place orders directly from their terminal. For developers, system administrators, and productivity enthusiasts, this is more than a novelty—it’s a glimpse into how food delivery services are evolving to integrate with developer workflows. This article dives into what the CLI tool does, how it works, and whether it’s genuinely useful or just a PR stunt.
The News in a Nutshell
According to the original article on TechCrunch (Source), DoorDash has released an experimental CLI client that lets users search for restaurants, browse menus, customize orders, and complete purchases—all without leaving the terminal. The tool is built on top of DoorDash’s existing API and is available for macOS, Linux, and Windows via package managers like Homebrew and npm.
Key features include:
- Search and filter restaurants by cuisine, rating, or delivery time.
- View menus with item descriptions and prices.
- Place orders using saved payment methods and addresses.
- Track delivery status in real-time.
The CLI tool is designed for developers who spend most of their day in the terminal and want to avoid context switching. It also supports scripting, so users can automate lunch orders or integrate with other tools.
How the CLI Tool Works
DoorDash’s CLI is written in Python and uses OAuth2 for authentication. After installing it via brew install doordash-cli or npm install -g @doordash/cli, users run dd auth login to authenticate with their DoorDash account. Then, commands like dd search "pizza" --sort rating return a list of nearby pizza places. Selecting a restaurant with dd select 2 displays the menu, and dd order "Margherita" --size large adds the item to the cart. Finally, dd checkout processes the payment.
The developers at DoorDash faced challenges with terminal-based user interfaces, such as handling Unicode characters for emoji and ensuring menu items with special characters display correctly. They also implemented a caching system to speed up repeated searches, which is critical for a smooth experience.
Practical Examples
Imagine you’re a software engineer working on a critical bug fix. You don’t want to open a browser, log into DoorDash, and navigate through a dozen clicks. Instead, you just open a new terminal tab and run:
dd search "thai" --max-price 15
dd select 1
dd order "Pad Thai" --extra-spicy
dd checkout
Within seconds, your order is placed. Or, you could set up a cron job to order your usual lunch every Friday at 11:30 AM:
0 11 * * 5 /usr/local/bin/dd order "Pepperoni Pizza" --restaurant-id 12345 --checkout
For teams, the CLI could be integrated into a Slack bot or a CI/CD pipeline. For instance, after a successful deployment, a script could order food for the team as a celebration.
Pros and Cons
| Pros | Cons |
|---|---|
| No browser needed—faster for developers | Limited visual feedback—no images or detailed ratings |
| Scriptable and automatable | Requires API knowledge for advanced use |
| Works over SSH on remote servers | No support for group orders or split payments |
| Lightweight and fast | Potential security risks if authentication tokens are exposed |
Who Should Use It?
The CLI is ideal for:
- Developers who live in the terminal.
- System administrators managing servers who want to order food without leaving SSH.
- Automation enthusiasts who want to script their lunch orders.
- Hackathon participants looking for a fun way to integrate food into projects.
However, for casual users who prefer browsing photos and reading reviews, the web or mobile app remains the better choice. The CLI is a power-user tool, not a replacement for the main platform.
Security Considerations
Since the CLI stores authentication tokens locally, users must be careful about token exposure. DoorDash recommends using dd auth logout after each session on shared machines. Additionally, the tool does not support multi-factor authentication (MFA) directly—users must generate an app-specific token through their account settings.
The Bigger Picture: APIs and Developer Ecosystems
DoorDash’s move reflects a broader trend: companies opening up their platforms via APIs to attract developers. Many businesses now offer API access for automation. For example, ASI Biont supports integration with several services through its platform, enabling users to connect workflows seamlessly. If you’re interested in learning how to leverage APIs for your own projects, check out the courses available at asibiont.com/courses.
Conclusion
Ordering DoorDash from the command line might seem like a gimmick, but it’s actually a practical tool for a specific audience. It saves time for developers, enables automation, and showcases how food delivery services can evolve. While not for everyone, it’s a clear sign that the line between consumer apps and developer tools is blurring. If you’re a terminal lover, give it a try—you might never go back to the browser.
For more details, read the original announcement on TechCrunch (Source).
Comments