Skip to content

fix: handle Ultra accounts with no 5-hour limit - #76

Merged
catinspace-au merged 1 commit into
mainfrom
fix/ultra-no-session-limit
Oct 31, 2026
Merged

catinspace-au merged 1 commit into
mainfrom
fix/ultra-no-session-limit

Conversation

@catinspace-au

Copy link
Copy Markdown
Contributor

Anthropic is removing the 5-hour limit from Ultra (formerly Max 20x) accounts once they're verified. A payload with no five_hour meter used to come through as 0%, so Se would sit at 0% forever.

  • Se hides when the payload carries no 5-hour figure. Wk and Tk carry on, in both the multi-panel and compact layouts.
  • The tooltip says "Session - no 5-hour limit" instead of a percent and reset time.
  • The renamed plans show by their new names: Max 20x is Ultra, Max 5x is Max. A personal plan reads "Ultra (Personal)".
  • Simulate Session % accepts "none", so the no-limit state can be checked in F5 without an Ultra account.

We have no verified account to capture a real payload from, so the tests cover the likely shapes: five_hour null, five_hour missing, and utilization null. A zeroed five_hour block with no reset would still read as 0%, because it's indistinguishable from a fresh window.

Tested in F5. 974 unit tests pass and lint is clean.

Anthropic is dropping the 5-hour limit from verified Ultra accounts. A usage payload with no five_hour meter used to read as 0%, so Se sat at 0% forever. Now Se hides, Wk and Tk carry on, and the tooltip says "Session - no 5-hour limit".

The renamed plans show by their new names: Max 20x is Ultra, Max 5x is Max. Simulate Session % takes "none" to show the no-limit state in F5.
@catinspace-au
catinspace-au merged commit 76a3b93 into main Oct 31, 2026
7 checks passed
@catinspace-au
catinspace-au deleted the fix/ultra-no-session-limit branch October 31, 2026 03:09
hypersec-ci-bot Bot pushed a commit that referenced this pull request Oct 31, 2026
## [2.5.24](v2.5.23...v2.5.24) (2026-10-31)

### Bug Fixes

* handle Ultra accounts with no 5-hour limit ([#76](#76)) ([76a3b93](76a3b93))
@hypersec-ci-bot

Copy link
Copy Markdown

This issue has been resolved in version 2.5.24

The release is available on GitHub release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant