ackr CLI

Pre-release placeholder (v0.0.1). The package name is reserved on npm but the CLI is not functional yet — ackr ask exits with a non-zero status and a "pre-release" notice. Track progress at ackr.io.

The CLI hook for AI agent workflows. Distributed via npm so npx ackr ask … works without install.

Install

npm install -g @ackr/cli   # or use npx @ackr/cli

The package is @ackr/cli; the binary it installs is ackr.

Usage (target — not yet implemented)

ackr ask "Should I deploy to prod?" --yes-no
# { "answered": true, "response": true, "elapsed_ms": 4231 }

# Exit codes
# 0 = answered
# 1 = timeout
# 2 = rejected/cancelled
# 3 = error

Action flags

| Flag | Type | | --------------------- | ----------------------------------- | | --yes-no | boolean | | --text <label> | free-text response | | --number <label> | numeric response | | --choice <a,b,c> | radio (single choice) | | --multi <a,b,c> | select (multi-choice) | | --ttl <seconds> | expiry, default 300 | | --project <name> | project bucket | | --title <title> | optional, defaults to the prompt | | --body <markdown> | optional markdown body |

Auth

ACKR_API_KEY env var, or fallback to ~/.config/ackr/config.json.

Presence check

Before pushing, the CLI sniffs recent terminal activity. If the user is at the keyboard → prompt inline via stdin. Otherwise → push notification + long-poll /v1/notifications/{id}/wait.

Local dev

cd cli
npm install
npm run dev -- ask "test"
npm test

Versioning

Semver. The placeholder lives at 0.0.x until ackr ask works end-to-end; the first functional release jumps to 0.1.0 to match the repo VERSION. Published from cli/ via npm publish.