Summary
In paseo-omp v0.4.0, the Quota popover continues to display usage for providers whose accounts have already been logged out. The entries look like current quota information, with no indication that they are historical snapshots.
Steps to reproduce
- Sign in to multiple OMP providers (for example, OpenAI/ChatGPT Plus, xAI, Google, and OpenCode Go), and let OMP record their quota usage.
- Log out of xAI, Google, and OpenCode Go, leaving only the OpenAI/ChatGPT Plus account signed in.
- Open the
paseo-omp Quota popover in Paseo.
Actual behavior
The Quota popover still lists usage for xAI, Google, and OpenCode Go alongside OpenAI, even though the former accounts have been logged out. Without freshness or login-status indicators, historical values can be mistaken for currently valid quota readings.
Expected behavior
Ideally, the default Quota view should display only currently authenticated accounts. If showing historical accounts is intentional (e.g. to compare providers before switching), expired/logged-out entries should be clearly identified as historical and include their last-recorded timestamp, or be accessible via a separate "Show historical quotas" toggle.
Likely cause (based on v0.4.0 source)
server/quota.ts retrieves the latest row for every (provider, account_key, limit_id) in usage_history, without checking whether the corresponding account is still signed in and without a freshness cutoff.
client/quota-state.ts explicitly groups every recorded provider, not only the active session's provider.
- The popover does not render the
recordedAt timestamp or distinguish logged-out providers from active accounts.
Relevant sources:
Environment
paseo-omp: v0.4.0
- Paseo: v0.9.1
- OMP: v18.2.10
Related but distinct from #72 (profile-specific quota/data-directory selection); this report concerns logged-out accounts within quota history.
Summary
In
paseo-ompv0.4.0, the Quota popover continues to display usage for providers whose accounts have already been logged out. The entries look like current quota information, with no indication that they are historical snapshots.Steps to reproduce
paseo-ompQuota popover in Paseo.Actual behavior
The Quota popover still lists usage for xAI, Google, and OpenCode Go alongside OpenAI, even though the former accounts have been logged out. Without freshness or login-status indicators, historical values can be mistaken for currently valid quota readings.
Expected behavior
Ideally, the default Quota view should display only currently authenticated accounts. If showing historical accounts is intentional (e.g. to compare providers before switching), expired/logged-out entries should be clearly identified as historical and include their last-recorded timestamp, or be accessible via a separate "Show historical quotas" toggle.
Likely cause (based on v0.4.0 source)
server/quota.tsretrieves the latest row for every(provider, account_key, limit_id)inusage_history, without checking whether the corresponding account is still signed in and without a freshness cutoff.client/quota-state.tsexplicitly groups every recorded provider, not only the active session's provider.recordedAttimestamp or distinguish logged-out providers from active accounts.Relevant sources:
Environment
paseo-omp: v0.4.0Related but distinct from #72 (profile-specific quota/data-directory selection); this report concerns logged-out accounts within quota history.