You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Android subscription widgets cannot currently select the accounts or quota windows they show. With two Codex accounts, the widget pools them under “Codex”, loses their configured names, and truncates additional quotas behind “more in T3”.
I propose one device-local configuration flow for each Android home screen widget, reachable through the launcher's Edit action, Settings, and Usage → Limits. A persistent, collapsible preview shows changes while scrolling the settings. Each widget can inherit default settings or keep its own selection of providers, accounts, environments, quota periods, grouping, ordering, density, percentages, theme, progress bars, and update/environment labels. Each displayed quota can show the next reset time, a countdown, or both. Additional quotas remain accessible by scrolling the widget.
The proposed defaults show separate named accounts and all quota rows, and hide environment names when only one environment is connected. Combined provider totals and explicit environment visibility remain available. These defaults and the new settings workflow need maintainer product-direction/scope approval under CONTRIBUTING.md; that approval is pending. This discussion requests that direction rather than asserting a configuration or triage exemption.
The implementation is Android-specific, uses existing account deduplication (including separate workspace subscriptions for one email), and preserves the iOS widget behavior. It does not change usage-provider APIs or provider authentication, add automatic background quota fetches, or address the separate Android picker-preview and resize-floor reports.
A PR with matching before/after screenshots, short guided native recordings, focused tests, and verification limits will accompany this proposal. Is this configuration scope and default presentation acceptable for upstream?
Implementation submitted for review: PR #17890, including native before/after screenshots and short guided recordings. Product-direction and scope approval remains pending.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Android subscription widgets cannot currently select the accounts or quota windows they show. With two Codex accounts, the widget pools them under “Codex”, loses their configured names, and truncates additional quotas behind “more in T3”.
I propose one device-local configuration flow for each Android home screen widget, reachable through the launcher's Edit action, Settings, and Usage → Limits. A persistent, collapsible preview shows changes while scrolling the settings. Each widget can inherit default settings or keep its own selection of providers, accounts, environments, quota periods, grouping, ordering, density, percentages, theme, progress bars, and update/environment labels. Each displayed quota can show the next reset time, a countdown, or both. Additional quotas remain accessible by scrolling the widget.
The proposed defaults show separate named accounts and all quota rows, and hide environment names when only one environment is connected. Combined provider totals and explicit environment visibility remain available. These defaults and the new settings workflow need maintainer product-direction/scope approval under CONTRIBUTING.md; that approval is pending. This discussion requests that direction rather than asserting a configuration or triage exemption.
The implementation is Android-specific, uses existing account deduplication (including separate workspace subscriptions for one email), and preserves the iOS widget behavior. It does not change usage-provider APIs or provider authentication, add automatic background quota fetches, or address the separate Android picker-preview and resize-floor reports.
A PR with matching before/after screenshots, short guided native recordings, focused tests, and verification limits will accompany this proposal. Is this configuration scope and default presentation acceptable for upstream?
Implementation submitted for review: PR #17890, including native before/after screenshots and short guided recordings. Product-direction and scope approval remains pending.
All reactions