Add Cursor Cloud Agent usage attribution#2030
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 785a9c6691
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: Add Cursor Cloud Agent usage attribution This is item 1/1 in the current shard. Shard 0/1. This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
Summary
Cursor's iOS rollout makes Cloud Agents much more practical to start away from a development machine. This gives those workflows the same at-a-glance cost visibility that CodexBar already provides for Cursor's other usage lanes.
Details
POST /api/dashboard/get-filtered-usage-eventsusing the existing Cursor session cookie and required first-partyOriginheader.cloudAgentIdorisHeadlessand aggregates only chargeable positive-cost events.Validation
swift test --filter CursorCloudAgentUsageTests— 6 passedswift test --filter CursorStatusProbeTests— 38 passedswift test --filter CursorMenuCardModelTests— 5 passedmake check— passed, including SwiftFormat and strict SwiftLintgit diff --check— passedmake test— blocked in an unrelated existing suite:AdaptiveRefreshTimerTestsintermittently fails refresh-count timing expectations. The sharded retry and an isolated rerun reproduced failures only in that suite; this PR does not touch adaptive refresh code.No live provider probe or real account read was run, following the repository's no-Keychain-prompt validation guidance. Network behavior is covered with stubbed URL sessions.