Linux Ubuntu Cursor-agent CLI Error: Unable to reach the model provider

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Hi I am unable to use Cusor CLI with loop command and with the model Grok 4.6 Extra High, and it said Error: Unable to reach the model provider. Weโ€™re having trouble connecting to the model provider. This might be temporary - please try again in a moment.

Steps to Reproduce

Using /loop 2m

Expected Behavior

the loop should be continue like Grok Build one, but currently all loop with all models cannot do it, it could not run more than 1 hour

Operating System

Linux

Version Information

โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ
โ”‚ โ”‚
โ”‚ About Cursor CLI โ”‚
โ”‚ โ”‚
โ”‚ CLI Version 2026.08.11-e8db854 โ”‚
โ”‚ Model Cursor Grok 4.6 Extra High โ”‚
โ”‚ OS linux (x64) โ”‚
โ”‚ Terminal tmux โ”‚
โ”‚ Shell bash โ”‚
โ”‚ Last Request ID ff6d2094-6fcc-4ab6-9dc3-97b1e1d9c4b0 โ”‚
โ”‚ User Email [email protected] โ”‚
โ”‚ โ”‚
โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ

For AI issues: which model did you use?

Grok 4.6 xhigh ( Unable to reach the model provider. Weโ€™re having trouble connecting to the model provider. This might be temporary - please try again in a moment.)
GPT 5.6 Sol Max/GPT 5.6 Terra Max (both cannot loop like Grok build one)

For AI issues: add Request ID with privacy disabled

62c3ea9f-4b7f-494a-a15e-87e8c3d70a86

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey there!

This is a temporary capacity issue with the provider serving Grok 4.6 Extra High (itโ€™s hit a few other models too, which is why GPT was affected). Itโ€™s not on your end or specific to /loop - when a run catches one of these โ€œoverloadedโ€ errors mid-session it ends, so long loops cut out early on any model.

Itโ€™s an issue weโ€™re tracking and the team is actively working on the capacity side. Once it clears, retrying /loop should work normally - if it still stops early after that, reply here and weโ€™ll dig into the loop side.

Hi Mohit, it is still didnโ€™t work in Cursor GUI one in Linux. Yesterday I need to fire twice, the first session ran around 1 hour, and the second session ran longer around 4-5h. But today it only ran under 30 mins with first fire loop command. Could you help me have a look?