Claude-4.6-opus-high-thinking is not available in the slow pool

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Cursor CLI no longer generates responses.

In Cursor UI, I get “claude-4.6-opus-high-thinking is not available in the slow pool. Please switch to auto or Auto.”

Since about 2-3 hours.

I’m trying claude code cli in the meantime, but really dislike it. Cursor is way better. How to get cursor cli working again? :folded_hands:

Steps to Reproduce

cli:

  • open cli
  • say ‘hello’
  • it will say ‘generating’, then return you to the edit question prompt

gui:

  • open cursor
  • type hello
  • it will say ‘claude-4.6-opus-high-thinking is not available in the slow pool. Please switch to auto or Auto.’

Operating System

MacOS

Version Information

CLI v2026.02.27-e7d2ef6

For AI issues: which model did you use?

opus 4.6, codex 5.3

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, a couple things to check here:

  1. Can you try switching your model to auto in the model dropdown? That should route you to an available model as a quick workaround.

  2. Check your team’s usage on the dashboard. This error sometimes shows up when the team’s pooled usage limit has been hit, even if it’s not obvious in the UI.

For the CLI specifically, if the model isn’t available, the CLI silently falls back to the prompt instead of showing the error message. It’s the same root cause.

Let me know how it goes with auto mode and the usage check.

Seems opus 4.6 is working again this morning. I think the error message could/should be a lot clearer, so I could then ask our admins to increase spend quota. Question: are you a member of Cursor, who could escalate such a request? Or are we both community members, who are both doing our best to use Cursor in as productive way as possible?

Glad opus is working now.

About the error message, I agree it isn’t very informative right now. This is especially true for team users who need to understand that the team limit has been reached and contact their admin. I’ve shared the feedback with the team. It’s on our radar, but we don’t have a specific timeline yet.

And yeah, I’m on the Cursor team, so if you need anything, just reach out.

It turns out it was actually the models themselves that were broken somehow. Learned this from support. The problem resolved itself a few hours later.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.