Port upstream 0.55.0: Cursor Grok Bot usage - #373
Merged
Conversation
Collaborator
Author
Thermo-nuclear re-reviewPrevious finding is closed: the positional six/seven-element Cursor tuples were replaced by a named CursorUsageResult boundary. 11/11 focused API tests and strict Clippy pass. Verdict: APPROVED. |
Finesssee
force-pushed
the
port/055-cursor-grok-bot
branch
from
August 24, 2026 20:59
3cfe76d to
ac14ccb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/api/dashboard/get-sand-usage-statusbest-effort with a 5-second timeoutUpstream evidence
v0.55.0c87c35bec/ Add Grok Bot Support to Cursor Card steipete/CodexBar#3127Validation
C:/Users/mac/.cargo/bin/cargo.exe test -p codexbar cursor-> 24 passedgit diff --check-> passScope
Isolated Cursor provider enhancement. No separate Grok provider state, version bump, or unrelated UI changes.