callkaro-cli-unofficial 0.1.0 → 0.1.1

package/README.md

@@ -2,11 +2,12 @@
 
 An unofficial fork of the [CallKaro CLI](https://www.npmjs.com/package/@callkaro-official/cli). It installs as `cku`, so it sits alongside the official `ck` without either one overwriting the other.
 
-Manage voice agents, calls, phone numbers, batch campaigns, simulations and analytics from the terminal.
+Manage voice agents, calls, phone numbers, batch campaigns, simulations and analytics from the terminal — plus the dashboard side, which the official CLI doesn't reach at all.
 
 ```
 cku agents list
 cku calls make --agent <id> --to <number> --test
+cku kpi tasks --severity "Very High" --column action_items
 cku accounts use tejas@acme.com
 ```
 
@@ -14,12 +15,12 @@ cku accounts use tejas@acme.com
 
 ## Why this exists
 
-Three reasons, all of them things the official CLI can't do.
-
 **It doesn't fight the official CLI for a name.** Both packages write to the same global `node_modules/.bin`. If both were called `ck`, whichever npm install ran last would silently take over. You'd type `ck`, get official behaviour, and get no signal anything had changed. `cku` cannot collide.
 
 **It holds several accounts at once.** The official CLI keeps one session. This one keeps a file per account, and can pin an account to a folder, so two agents working in two directories can't switch each other out from under themselves.
 
+**It reaches the dashboard API.** The official CLI only talks to `/cli/*`. That leaves the KPI board, the call analyzers, and the server's own model catalogue unreachable from a terminal — [`cku kpi`](#only-in-cku) is the whole of that surface.
+
 **It fixes three upstream bugs.** Details and evidence in [`docs/BUG-REPORT.md`](docs/BUG-REPORT.md).
 
 ---
@@ -120,6 +121,69 @@ My own first port of this fix had a worse version of the same bug: I merged agai
 
 ---
 
+## Only in `cku`
+
+Commands and capabilities the official CLI does not have at all. Not bug fixes — surface area.
+
+### The KPI manager and the pending-task board
+
+The official `ck` has **no KPI commands whatsoever**. This is the only way to reach the board from a terminal.
+
+```bash
+cku kpi tasks --severity "Very High" --column action_items --since 7d
+cku kpi show "<taskId>"                 # cause, recommended fix, metric impact
+cku kpi create --cause "…" --fix "…" --severity High
+cku kpi move "<taskId>" in_progress
+cku kpi comment "<taskId>" "Fixed in v3"
+cku kpi assign "<taskId>" --to "Name"   # or --to ai_fde
+cku kpi target --agent <id> --value 25
+cku kpi rca --agent <id> --since 2026-09-01 --until 2026-09-30
+```
+
+There is **no delete** for a card — the board retires one by moving it to `rejected`, which is reversible. Only `description` is editable after creation; `cause`, fix and severity are fixed at create, so correcting one means creating a replacement.
+
+`GET /pending-tasks` returns every column including `done` and `rejected`, so a closed card is not a gone card. The list prints a **COLUMN** column for exactly that reason, and `--column` filters on it.
+
+### The dashboard credential
+
+```bash
+cku dashboard login     # separate from `cku login`, and expires after 24h
+cku dashboard whoami
+cku dashboard probe     # which dashboard routes this token reaches
+```
+
+The dashboard API needs a *different* token from `/cli/*` — they're not interchangeable, and each rejects the other with an opaque 401. This also unlocks `cku analyzers` and `cku models`. Passwords are never written to disk.
+
+### Knowing which models are actually valid
+
+```bash
+cku models               # per slot, and which field each governs
+cku models --slot agent
+```
+
+Models are scoped per slot and **the slots disagree**: `agent` has 44, `post-call` has 9 and excludes `gpt-4o` and `o4-mini`. So the same value is valid in `model` and refused in `postcallmodel`. Works with or without a dashboard session, and says which source it read.
+
+### A catalogue that can't silently rot
+
+The provider tables, and now the model lists, are regenerated from the server rather than hand-copied:
+
+```bash
+npm run catalog:sync     # refresh from the bundle + the live server
+npm run catalog:check    # fail if catalog.json disagrees with the snapshot
+```
+
+`catalog:check` runs offline against a committed snapshot, so it works in CI with no credentials. On 1 October 2026 it caught shipped tables that listed withdrawn models *and* missed live ones in both directions. A wrong voice model otherwise persists silently and only surfaces as a broken call.
+
+### Smaller things
+
+- `cku calls logs` — grep/awk/sed over the raw call log, in-process, no subprocess and no shell
+- `cku accounts status` — reports which account is in effect **and where that choice came from**
+- Per-project binding, so parallel agents can't redirect each other
+- `secrets set` without the value on the command line
+- `--json` that stays unpaged for scripting, with human tables paged
+
+---
+
 ## Staying current
 
 A daily workflow checks npm for a newer `@callkaro-official/cli` and, when it finds one, regenerates the provider catalogue and opens a PR onto the `official` branch. It never merges anything itself.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "callkaro-cli-unofficial",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "license": "Apache-2.0",
   "description": "Unofficial fork of the CallKaro CLI \u2014 manage your voice AI agents from the terminal",
   "bin": {