Overview

Command-line tool to inspect Foodora orders and track active deliveries, with basic automation for reordering and experimental (currently non-working) Deliveroo support.

Key Advantages

1.Enables terminal-based access to Foodora order history and live order status without using the web or mobile apps

2.Supports watching active orders to track ETA/status in real time from the CLI

3.Provides convenient reordering flows (preview and confirm, with address selection) for repeat orders

4.Offers multiple authentication approaches (email/password via stdin, browser-based login, Chrome session/cookie import) to work around bot/Cloudflare protections

5.JSON output for history detail enables scripting and integration into other tools or workflows

Use Cases

Power users who prefer managing Foodora orders from the terminal instead of the mobile or web UI
Developers or operations teams pulling Foodora order data into scripts, dashboards, or expense-reporting tools via JSON output
Users who want to monitor active delivery status (ETA, arrival) in a terminal window or multiplexed environment (tmux, screen)
Frequent customers who want a quick CLI-based reorder flow for standard/favorite orders, with address selection and confirmation
Technical users experimenting with or debugging Foodora sessions, login, and API behaviors, including cookie/session import flows

Evaluation History (1)

6.6/103/19/2026darwin-arm64

▼

OS: darwin-arm64LLM: openai/gpt-5-nano

**Quick judgement:** A niche but solid CLI for Foodora power users who want terminal access to order history, live status, and reordering. Well-suited for technical users and scripting; too narrow and technical for most end users. **What it does well** - Provides practical commands for listing past orders, inspecting details (including JSON), and watching active orders in real time. - Reordering is thoughtfully designed with preview, explicit `--confirm`, and `--address-id` options to reduce accidental changes or wrong-address orders. - Multiple auth flows (stdin password, browser-based login, Chrome cookie/session import) help work around Cloudora/bot protection and make login feasible in more environments. **Key limitations & risks** - Scope is limited: only Foodora is supported in a working state; Deliveroo is explicitly marked WIP and “not working yet.” - Depends on unofficial/unstable APIs and session mechanisms; changes on Foodora/Deliveroo’s side may break functionality without warning. - Handling credentials, bearer tokens, and session cookies in a CLI context carries security risk if the environment is not well secured (shell history, scripts, shared machines). - Likely not ideal on non-desktop environments or for non-technical users; assumes comfort with terminal, config files, and browser profiles. **Recommended scenarios** - Technical Foodora users who live in the terminal and want quick visibility into order history and current delivery status. - Developers automating Foodora-related workflows (e.g., tracking spend, exporting history, integrating with custom notifications or dashboards) via the JSON output. - Power users regularly reordering similar meals who want a fast, scriptable reorder flow with safety confirmations. **Less suitable for** - Non-technical users, or anyone uncomfortable with CLI tools, configs, and session/cookie handling. - Users expecting a polished, multi-provider delivery management tool; Deliveroo support is not production-ready and other services are not supported.

Ordercli

Overview

Key Advantages

Use Cases

Evaluation Scores

Download Trend

Evaluation History (1)

Comments (0)

Post a Comment