Repository navigation
Usage Pace 0.4.1 — live-check fixes
Patch release fixing all seven issues found during the 0.4.0 live check on bb 0.46.1 / SDK 0.6.49 with two Claude Accounts logins.
Fixes
- Healthy server accounts stay visible. Account usage errors, rejected resource reads, and failed source inventories no longer mark an entire host unavailable. Server-only filtering only treats host identity, availability, and host-list failures as server failures.
- Account errors stay on their rows. The dialog footer and CLI warning no longer repeat individual account errors. Discovery, host-list, and source-list failures still produce collection warnings.
- Card errors stay on the failed tab. Recognizes all three bb 0.46.1 notices, including “Couldn’t refresh. Showing last update.”, while retaining older wording. Healthy Codex, Claude Code, and All accounts tabs stay clear when the failed provider is known.
- Merged accounts show the right location. Strip descriptions and dialog locations use the server machine in server-only mode and all associated machines otherwise. Saved-reset details name the machine that actually supplied the verified inventory.
- No repeated provider labels. CLI, strip, and dialog omit fallback account labels that equal the provider display name, ignoring case. Meaningful account labels and aliases remain.
- Separate installation and upgrade instructions. Inspect the source before choosing an in-place update or a settings-destructive remove/reinstall.
- Transient keyless errors do not split known accounts. A resource that previously reported an account key keeps it when an error omits the key, so a sleeping laptop does not add a phantom pool member. Never-known identities remain separate; a successful login change replaces the key.
Minimum requirements remain BB 0.44.0 / SDK 0.5.29. Committed release artifacts were built with that toolchain. Saved resets remain read-only; CLI account/provider JSON aliases, nullable pace, token totals, and Codex-only --resets behavior are unchanged.
Verification
- 385 Vitest tests, 3 token-total tests, and TypeScript passed.
- Comment policy passed across 95 files with zero violations; all 13 policy regression tests passed. Staged secret scanning passed before the implementation commit.
- Production-only rebuilds and release checks passed, including BB's bundled npm 11.16.0, version/SDK metadata, host digest, and isolated backend/host smoke loading. No provider requests were made by release validation.
- Synthetic desktop/mobile browser checks covered current-view account labels, reset-reader provenance, nonduplicate headings, and compact/dialog overflow.
- PR, resulting-main, and release-tag Woodpecker CI passed. The release tag points to the merged main commit containing the tested tree.
- Not yet verified: live installation or upgrade of 0.4.1 on either bb server. The completed 0.4.0 live observations and synthetic regression evidence are recorded in multi-account verification.
New installations
bb plugin install 'git:https://github.com/scowalt/bb-plugin-usage-pace.git@v0.4.1'
bb plugin config usage-pace set showStrip trueThe second command enables the optional strip. Use @^0.4.1 instead of the exact tag to track compatible releases.
Upgrades
Inspect the requested and resolved source first:
bb plugin source usage-paceFor repository/branch-tracking installs whose branch contains 0.4.1, or a release-range install that admits this tag, update in place and keep settings:
bb plugin update usage-paceAn exact tag or commit does not advance to a newer tag with update. Moving a pinned install, or changing an existing install to a tag or range, requires removal first. Removal deletes the plugin's settings, secrets, and schedules. Record the current configuration and restore your desired settings after reinstalling:
bb plugin config usage-pace
bb plugin remove usage-pace
bb plugin install 'git:https://github.com/scowalt/bb-plugin-usage-pace.git@v0.4.1'Use @^0.4.1 in the final command for compatible-release tracking. Do not use plugin install as an in-place upgrade: bb 0.46.1 rejects the duplicate plugin ID.
Publishing this release does not install, update, reload, or reconfigure plugins on either live bb server.