docs: add macOS native cursor capture test pipeline#673
Conversation
Documents the cursor helper binary, permissions, manual test checklist, expected sidecar shape, and known limitations for the darwin native cursor path.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughAdds a new macOS native cursor helper testing and diagnostics document describing helper behavior, build/run and override steps, permissions, a prioritized manual test checklist, expected cursor sidecar JSON, integration routing, and platform-specific limitations. ChangesmacOS Native Cursor Helper Testing & Diagnostics Documentation
Estimated Code Review Effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly Related PRs
Suggested Reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 53be8df129
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/testing/macos-native-cursor.md`:
- Line 113: The doc uses two different sidecar key names
("cursor-recording-data" and "cursorRecordingData"); pick one canonical key
(prefer the project’s canonical JSON/key naming convention — e.g.,
cursorRecordingData if code uses camelCase or cursor-recording-data if
kebab-case) and update all occurrences (including the references near the
interactionType: "click" and "mouseup" guidance and the duplicate at the later
occurrence) so the test steps consistently reference that single key; ensure any
example JSON, text references, and the phrase "recording session sidecar" all
show the chosen key.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 77e53d8e-aea3-404c-a678-f4d37571c0e6
📒 Files selected for processing (1)
docs/testing/macos-native-cursor.md
- Unify sidecar key name to camelCase cursorRecordingData (was mixing cursor-recording-data and cursorRecordingData in the same checklist) - Graceful-degradation test now removes both binary copies so the missing-helper fallback is actually exercised (build/ and bin/darwin-*) - Healthy recording section points to <videoPath>.cursor.json sidecar instead of the .openscreen project file, which does not embed cursor data
Summary
docs/testing/macos-native-cursor.mddocumenting the macOS native cursor capture featureSummary by CodeRabbit