Skip to content

v0.5.0

Choose a tag to compare

@henchiyb henchiyb released this 05 Sep 13:33

Kibble 0.5.0 adds explicitly authorized team reporting and opt-in automatic CLI updates, with fixes for collection configuration and usage labels.

  • Run kibble login --reporting to approve role-scoped reads, then use kibble usage --scope team|org, --team and --list-scopes. Personal reads remain the default; the server checks current roles and assignments on every request.
  • Interactive login asks once about automatic updates. Headless setup requires --auto-update. Verified managed releases, health probes, recovery and rollback preserve collection and credentials. Help and version commands do not check for updates.
  • Keep CLI output in English. Refresh the agent instructions with kibble skill install to use scope discovery and the corrected estimate labels.
  • Resolve Claude cloud/API configuration before stale subscription metadata, and respect the same custom Codex home for billing plans and collection.
  • Correct usage language: Claude Analytics supplies vendor estimates, not invoice charges. Vendor source priority and actual billing certainty are distinct.
  • Retain Windows lock safety and register scheduled tasks through XML to support managed paths with spaces and long command lines. Node 20, 22 and 24 are supported.

Self-hosted servers must deploy the matching server and migrations through 0020_reset_unverified_reporting before using the new reporting grant. Existing reporting devices must approve kibble login --reporting again; collection and personal reads continue. Existing CLI installations need one manual upgrade to acquire the updater: npm install -g @usekibble/cli@0.5.0.

Validation: all nine Windows/Linux/macOS and Node 20/22/24 CI jobs passed, including native loading, managed installation and real scheduler execution. Local raw Claude accuracy had 0% token delta for September 4. Server regression checks, HTTP auth/ingest/reporting checks, typecheck, lint, build and bilingual validation passed.

Automatic updates use the separately approved npm auto tag. Publishing to latest alone does not approve a release for automatic installation.