Repository navigation
Tags
Tags
fix(collector): take the write lock at the start of every state trans… …action (#71) * fix(collector): take the write lock at the start of every state transaction * test(collector): move Antigravity quota fixture resets past the present * chore(release): prepare 0.16.3
feat(plan): let Google accounts pick Plus or Pro when no plan is repo… …rted (#70) * feat(plan): let Google accounts pick Plus or Pro when no plan is reported Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore(release): prepare 0.16.2 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
feat(collector): read omp sessions and refresh Antigravity quota on d… …emand (#67) * feat(collector): read omp sessions and refresh Antigravity quota on demand Read omp (oh-my-pi) session files incrementally. Completed assistant messages become requests: opencode-go goes to the OpenCode Go account and google-antigravity joins the active Antigravity account. Requests are deduplicated by message id, time, channel, model and token counts, so moved files and branched sessions do not bill twice. When sync finds new Antigravity usage from agy or omp, run `agy -p /usage` at most once every 5 minutes, merge the four quota windows into quota-<label>.tsv (keeping the plan row) and upload them in the same round. scan never triggers the refresh. Co-Authored-By: Claude Sonnet 697E 5.5 <noreply@anthropic.com> * chore(release): prepare 0.16.0 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
feat(agy): show both Antigravity quota pools on one account (#65) * docs(design): record visual tokens and conventions in DESIGN.md Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(agy): show both Antigravity quota pools on one account The collector now reports one account per Google login, with the Claude/GPT pool on five-hour-3p and seven-day-3p windows. The legacy per-pool accounts are sent with parentExternalId so their history resolves to the merged account. The server must deploy before the collector because the ingest schema is strict. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore(release): prepare 0.15.0 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
PreviousNext