Cursor background agents invoked through the API with my personal API token appear along all my other agents. This is really annoying.
We are using Cursor API for code reviews, issue triaging, etc, imagining how many daily agents that would be and they all live along my personal agents I created manually.
They should appear in another category or even in a team account with a team API token. But at least not mixing them is a P0 IMO.
Thanks for the feedback! We haven’t yet considered treating API-triggered agents differently from other Cloud Agents, but as we continue investing in the API, that’s might be worth exploring!
In the meantime, you can toggle off Cloud Agents from your view in the Agents Window here. The downside is that if you’re using other Cloud Agents (not API-triggered) you wouldn’t see those either.
Yes, I noticed that automations work differently regarding authorship (e.g. also their PRs are authored by Cursor whereas the API agent’s appear as authored by me).
What I prefer in GitHub Actions + Cursor API over Automations though is the existing version control in the repo, observability along other CI/CD jobs, etc.
