Feature request for product/service
Cloud Agent (GitHub, Slack, Linear,…)
Describe the request
Our whole team uses Cursor Cloud Agents for our AI-driven SDLC - kicking off tasks, getting PRs back, running work in parallel. It’s become a core part of how we ship, and we love it.
At the same time, we have a significant amount of Anthropic API credits that we can’t use with Cloud Agents. Today our Anthropic key works for chat in the editor, but Cloud Agents ignore it and always bill through Cursor usage. So we end up paying twice for the same Claude models while our API credits sit unused.
Request: Let Cloud Agents use a team’s own Anthropic API key (BYOK), the same way in-editor chat models do.
What would work well for us:
- A setting (team/admin level) to route Cloud Agent model calls to our Anthropic key
- Cursor can still charge its platform/VM fee for the agent infrastructure — we’re happy to pay for that
- Clear usage visibility showing which runs went to our key vs. Cursor billing
This would let us keep Cursor Cloud Agents as our main workflow instead of moving those tasks to other tools just to use the credits we already have.
Related threads:
Thanks!