Thariq (@trq212) on X

X (formerly Twitter) ·

2 min read Original article ↗

Thariq on X: "To manage growing demand for Claude we're adjusting our 5 hour session limits for free/Pro/Max subs during peak hours. Your weekly limits remain unchanged. During weekdays between 5am–11am PT / 1pm–7pm GMT, you'll move through your 5-hour session limits faster than before."

  • user avatar

    To manage growing demand for Claude we're adjusting our 5 hour session limits for free/Pro/Max subs during peak hours. Your weekly limits remain unchanged. During weekdays between 5am–11am PT / 1pm–7pm GMT, you'll move through your 5-hour session limits faster than before.

  • user avatar

    We've landed a lot of efficiency wins to offset this, but ~7% of users will hit session limits they wouldn't have before, particularly for pro tiers. If you run token-intensive background jobs, shifting them to off-peak hours will stretch your session limits further.

    user avatar

    Overall weekly limits stay the same, just how they're distributed across the week is changing. I know this was frustrating. We’re continuing to invest in scaling efficiently. I'll keep you posted on progress.

  • user avatar

    Too late. I canceled. Trust gone. Dangerous rug pull, and the company didn’t respond for a week. The company can easily do this to people using Claude Computer and hold critical workflows and data hostage in the account unless the user switches to ultra-expensive API billing. 🤮