@robbeverhelst/do
v1.105.0
Published
do — the agent-drivable CLI over the public /api/v1 surface
Readme
@robbeverhelst/do
do — an agent-drivable command-line client over the do public API
(/api/v1). A thin HTTP client: per-tenant API-key auth, the same validation and
RLS wall as the web app, no direct database access.
Published to npm as
@robbeverhelst/do(the@doscope is taken); the installed command isdo. The workspace package is named@do/cliinternally.
bunx @robbeverhelst/do help
bunx @robbeverhelst/do todayScope (v1)
The daily loop, all over /api/v1 with an API key — no destructive verbs:
capture "<text> #tag ! ~area"— quick-add a task to the inbox (!stars it)today— actionable tasks (overdue / scheduled / due / in-progress)task done <id>— complete (idempotent)task snooze <id> [--days N | --until <date>]— reschedulehabit log <id> [--value N] [--at <iso>]— record a check-in<entity> list/<entity> get <id>— read tasks, habits, occurrences, shopping-lists, inventory-items, recipes, meal-plans, notes, contacts, webhookslogin,config,whoami,help,version
Auth & config
Resolution order: --api-key/--url flags → DO_API_KEY/DO_API_URL env →
~/.config/do/config.json (written by do login / do config set).
Output
--json everywhere, and automatic JSON when stdout is piped (non-TTY). Failures
print { "error": { code, message } } and exit non-zero (see do help --json).
Develop
bun run --filter '@do/cli' dev -- today # run from source
bun run --filter '@do/cli' test # bun:test suite
bun run --filter '@do/cli' compile # standalone ./do binaryThe full agent skill lives at docs/agents/do-cli.md;
the authoritative surface is always do help --json.
