Cursor Permanently Raises Grok Model Usage Limits
Lee Robinson of Cursor announces permanent increase to included Grok model usage for all users.
Lee Robinson, a developer educator at Cursor, stated that the company permanently increased included usage limits for all first-party Grok models, including Composer 2.5 and future versions. The announcement noted rising demand as the reason. Robinson added that the team is also working to extend Grok Bot runtime. Eric Zakariasson, an engineer at Cursor, replied with a link to the post and shared six tips for making Grok Bot usage last longer, such as using event triggers instead of cron jobs and prompting the bot to report status.
Note this applies to all first-party models in Cursor, including Composer 2.5 and future Grok models. We’re also working hard at making your Grok Bot usage last longer! More on that soon.
Combined views
Cursor Permanently Raises Grok Model Usage Limits
Lee Robinson of Cursor announces permanent increase to included Grok model usage for all users.
Lee Robinson, a developer educator at Cursor, stated that the company permanently increased included usage limits for all first-party Grok models, including Composer 2.5 and future versions. The announcement noted rising demand as the reason. Robinson added that the team is also working to extend Grok Bot runtime. Eric Zakariasson, an engineer at Cursor, replied with a link to the post and shared six tips for making Grok Bot usage last longer, such as using event triggers instead of cron jobs and prompting the bot to report status.
