Skip to content

Add Cursor to the agents usage panel - #11050

Closed
Ruegen wants to merge 2 commits into
omacom:quattrofrom
Ruegen:add-cursor-agent-usage
Closed

Ruegen wants to merge 2 commits into
omacom:quattrofrom
Ruegen:add-cursor-agent-usage

Conversation

@Ruegen

@Ruegen Ruegen commented Sep 9, 2026 •

Copy link
Copy Markdown

Summary

  • Adds omarchy-agent-usage-cursor so Cursor shows up in the agents usage panel with Claude, Codex, and Fireworks. Each agent is still opt-in via widget settings.
  • Limits come from Cursor dashboard RPCs (included monthly plan). Unused Grok Bot weekly (a separate chat quota, not Agent weekly) is omitted so it is not drawn as a missing week window.
  • The collector reads the CLI session / ~/.config/cursor/auth.json / IDE login for the request and never prints tokens, dashboard URLs, or account identifiers. Tests use synthetic fixtures only.

Test plan

  • ./test/shell.d/agent-usage-cursor-limits-test.sh
  • With Cursor signed in, omarchy agent usage-update cursor writes ~/.local/state/omarchy/agents/usage/cursor.json with id: cursor and no access token in the file
  • With Cursor usage present, the panel shows a Cursor tab
  • With Cursor disabled in widget settings (providers.cursor.enabled: false), the Cursor tab stays hidden

Cursor is a fourth tab alongside Claude, Codex, and Fireworks. The collector never prints tokens, and unused Grok Bot weekly is omitted so it is not drawn as an Agent week window.

Co-authored-by: Cursor <cursoragent@cursor.com>
Cursor is listed as one of the covered agents; the copy no longer
explains that it sits alongside Claude, Codex, and Fireworks.

Co-authored-by: Cursor <cursoragent@cursor.com>
@Ruegen Ruegen changed the title Add Cursor as an additional agents usage tab Add Cursor to the agents usage panel Sep 9, 2026
@bjarneo

bjarneo commented Sep 21, 2026

Copy link
Copy Markdown
Member

Automated duplication check: this pull request looks similar to #7087, which covers the same Cursor usage collector. I keep that one open and close this one to consolidate review.

If you feel this is the wrong decision, please open the PR again with a note on the difference.

@bjarneo bjarneo closed this Sep 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants