A generic Bot failed reply can mean your trial usage is gone

Before you Reset Grok Bot's computer over a flood of "Something went wrong while generating the reply," check usage. On Oct 12 at 9:30 AM ET, Cursor staff member Colin told a user whose bug report had a version field showing 0.70.2 that replies were stopped "because your team's trial usage limit has been reached," and that Grok Bot "currently shows that as the generic 'Something went wrong' message instead of a clear notice." Reset and a new Bot did not help. The Cursor IDE still worked "because it can still use Cursor's own models after the limit."

How to use it#

1. If every Bot fails the same way, including a new one, stop troubleshooting the computer first.
2. On a team, Colin's advice is to reach out to your team admin or account contact about extending or converting the trial.
3. Keep using Cursor IDE on Cursor models if you only need the editor while Grok Bot is blocked.

If Grok Bot replies are blocked by a usage or trial limit, say so in plain language and list who on my team can extend or convert the trial. Do not Reset the computer.

Good to know#

• Colin said he passed the unclear message to the team. Until that ships, the generic error can hide a billing limit.
• Overnight on Oct 12, status.cursor.com also logged a short widespread Cursor outage that included Grok Bot. If your trial is not the issue and many people are failing at once, check the status page too.