{"version":"2.1.322","anchor":"fast-mode-cooldown-can-now-be-a-refused-for-this-project-s","canonical_anchor":"fast-mode-cooldown-can-now-be-a-refused-for-this-project-s","heading":"Fast mode can now show that it was refused for your project","tier":"notice","area":"Models","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.322\/e\/fast-mode-cooldown-can-now-be-a-refused-for-this-project-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.322","markdown":"### Fast mode can now show that it was refused for your project\n\nFast mode can pause with the message \"Fast mode was refused for this project\", then shows \"Trying fast mode again\" when the pause ends\n\n**What**\n\nWhen fast mode is temporarily unavailable, Claude Code shows why. There was already a message for each of these two reasons:\n\n- Fast mode is overloaded\n\n- You have hit your fast limit\n\nThere is now a third reason, shown as \"Fast mode was refused for this project\". When that pause ends, the notice reads \"Trying fast mode again\" instead of \"Fast limit reset \u00b7 now using fast mode\". Claude Code remembers why fast mode was paused so it can choose the right notice.\n\n**Why**\n\nIf fast mode is refused for your project, you get a clear explanation and a notice when Claude Code tries again, instead of a misleading message about hitting your fast limit.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: no"}