| name | checkers60 |
| description | Order groceries from Checkers Sixty60 via CLI. Search products, manage cart, view orders and delivery slots. |
checkers60
CLI tool for Checkers Sixty60 grocery delivery — search products, manage a cart, browse categories, view orders, and check delivery slots.
Install
brew install yashiels/tap/checkers60
Requires Node.js ≥ 20. After install, the checkers60 binary is available on your PATH.
Credentials
Place your session credentials in:
~/.openclaw/credentials/checkers60.json
The file should contain the token fields written by the OTP login flow (otp-trigger → otp-verify). The CLI reads this path automatically — no environment variable or flag needed.
Auth commands
| Command | Description |
|---|
checkers60 status | Show current auth status (logged in / token expiry) |
checkers60 otp-trigger | Send a one-time password to your registered phone number |
checkers60 otp-verify <ref> <code> | Verify the OTP and save tokens to credentials file |
checkers60 logout | Clear saved tokens from the credentials file |
Safety note: otp-trigger sends a live SMS. Never call it automatically or in a loop — only trigger it explicitly when the user asks to log in.
Headless / agent usage
Once logged in, everything is headless. Shopping, cart, orders, slots — all read the saved tokens from the credentials file and need no interaction. Run them freely.
Login is the one interactive step, and an agent CANNOT complete it alone. The OTP arrives by SMS to the user's phone, out of band — the agent has no way to read it. When checkers60 status shows a missing or expired token, the agent MUST:
- Run
checkers60 otp-trigger (this fires one live SMS — run it exactly once).
- Stop and ask the user to paste the code from the SMS. Do not guess, retry, or re-trigger.
- Run
checkers60 otp-verify <ref> <code> with the reference from step 1 and the code the user gives you.
Use --json on otp-trigger/otp-verify when driving this programmatically so you can parse the reference and confirm loggedIn.
The CHECKERS60_OTP_RELAY_URL / CHECKERS60_OTP_RELAY_TOKEN env vars are reserved for a future SMS-to-HTTPS relay but are not yet wired into the CLI — there is no auto-fetch of the OTP today. Always fall back to asking the user.
Product commands
| Command | Description |
|---|
checkers60 search <query> | Search for products by name or keyword |
checkers60 categories | Browse top-level product categories |
checkers60 trending | List currently trending products |
Cart commands
| Command | Description |
|---|
checkers60 cart | Show the current cart contents and total |
checkers60 add <target> [qty] | Add a product to the cart; target is a product ID or search term; qty defaults to 1 |
checkers60 remove <target> | Remove a product from the cart by ID or search term |
checkers60 clear | Empty the entire cart |
Delivery commands
| Command | Description |
|---|
checkers60 slots | List available delivery time slots |
checkers60 addresses | List saved delivery addresses |
Account commands
| Command | Description |
|---|
checkers60 orders | Show recent orders and their status |
checkers60 profile | Display the authenticated user's profile |
checkers60 cards | List saved payment cards |
Typical flow
checkers60 otp-trigger
checkers60 otp-verify <ref> <code>
checkers60 search "milk"
checkers60 add 12345 2
checkers60 cart
checkers60 slots
checkers60 addresses
checkers60 orders
Notes
- All commands require valid credentials in
~/.openclaw/credentials/checkers60.json. Run the OTP flow if checkers60 status shows an expired or missing token.
otp-trigger must only be invoked when the user explicitly asks to log in. Do not auto-trigger it in scripts or on credential errors.- The CLI exits non-zero on API errors and prints a human-readable error message to stderr.
