Why is Cursor suddenly forcing Max Mode for Claude Fable models?

[Fessde]

I am asking for an official explanation about the sudden Max Mode requirement for Claude Fable models.

Today I started seeing this error:

The model “claude-fable-5-high” requires Max Mode to be enabled. Please enable Max Mode and try again.

This is unexpected because my usage history shows that I was previously able to use claude-fable-5-xhigh normally under included requests. For example, on July 6 UTC, my history shows multiple Included entries for claude-fable-5-xhigh, each counted as 1 request, with large token usage. Now, on July 7 UTC, claude-fable-5-high appears with a MAX label and fractional request counts such as 30.7 and 47.3.

Please clarify:

1. Did Cursor change the policy for Claude Fable high/xhigh models?
2. What exact date and time did this change take effect?
3. Why was claude-fable-5-xhigh previously available as included request usage, while claude-fable-5-high now requires Max Mode?
4. How are existing included request allowances supposed to work after this change?
5. Will Cursor restore included-request access for these models, or publish a clear migration notice explaining the new rules?

This affects paid usage expectations. A model access policy should not silently change from included requests to Max Mode without a clear notice in the product and billing documentation.

Screenshot attached showing the usage history before and after the change.