Skip to content

fix: make account usage refresh resilient - #16

Merged
SilkageNet merged 1 commit into
mainfrom
fix/usage-refresh-reliability
Sep 28, 2026
Merged

SilkageNet merged 1 commit into
mainfrom
fix/usage-refresh-reliability

Conversation

@SilkageNet

Copy link
Copy Markdown
Owner

Summary

  • serialize per-account App Server requests and multi-account refreshes
  • retry transient usage failures up to three times while carrying forward rotated credentials
  • preserve complete per-account refresh failures in the usage cache and surface them in table/JSON output
  • extend the automatic cache freshness window from one to five minutes

Validation

  • go test -race ./...
  • golangci-lint run
  • real account list --refresh against two saved Pro accounts using Codex CLI 0.158.0-alpha.2.1

@SilkageNet
SilkageNet merged commit d7488ef into main Sep 28, 2026
5 checks passed
@SilkageNet
SilkageNet deleted the fix/usage-refresh-reliability branch September 28, 2026 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant