Notion Cloud Agent requires prepaid credits even when Grok 4.7 is set and weekly pool has plenty left

Support Bug Reports
, ,
1

Hi,

I’m on The X Subscription Premium plan. My weekly included usage is only about 6% used (resets Oct 24). I set the default model for Cloud Agents to Grok 4.7 (256K, High, Fast).

When I try to trigger a Cursor agent from Notion (via @Cursor in a comment or by moving a task to “Ready for agent”), I consistently get this error:

“The connected Cursor account is out of included usage or needs a paid plan. Check the plan and spend limit in the Cursor dashboard at cursor.com/dashboard, then try again.”

The agent only started working after I bought $10 of prepaid credits. Once credits were added, the same Notion trigger succeeded.

According to the docs, the weekly included pool should cover Grok models, including Cloud Agents. Third-party models are the ones that require prepaid credits. I had Grok 4.7 explicitly selected, so this shouldn’t have required credits.

Is this expected behavior for the Notion Cloud Agent integration, or is it a bug? Happy to provide screenshots of the billing dashboard, the Cloud Agent model settings, and the Notion error if useful.

Thanks.

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
  • Terminal & commands
  • Models, pricing & API keys (availability, Auto/Max, BYOK/Bedrock)
  • MCP & tools
  • Cloud Agents & Automations (cursor.com/agents, scheduled/event)
  • BugBot & Code Review
  • Cursor CLI
  • Cursor Mobile
  • Remote (SSH / Dev Containers / WSL)
  • Account, billing & login
  • Something else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

13

Hey @SorenAC, thanks for the report, and glad the Notion trigger is working for you now.

You’re right that with Grok 4.7 selected and most of your weekly included usage left, a Cloud Agent started from Notion shouldn’t need prepaid credits. Agents started through the Cursor API (which is how the Notion integration launches them) are currently being checked against your credit balance at launch instead of your weekly included usage. That’s why it only went through once you added credits. I’ve flagged this to the team.

In the meantime, keeping the credits in place should keep the Notion trigger working. Agents you start directly from Cursor (cursor.com/agents or the app) shouldn’t hit this check.

If your credit balance goes down from Grok 4.7 runs, let us know and we’ll take a look.