docs(cua-driver-rs): surface permissions status|grant in post-install hints#1767
Conversation
…ll hints The post-install "Next steps" jumped from "try it" straight to skills + MCP wiring, never mentioning permissions — yet on macOS nothing works until Accessibility + Screen Recording are granted, and granting from a terminal silently attributes to the terminal (not the driver). Add a "Grant permissions (macOS)" step (new #2, ahead of skills/MCP since it's foundational) pointing at the new `cua-driver permissions status|grant` verbs, with a tip toward `--autostart` for grant-once persistence. Shared template (post-install-hints.txt) so it shows on both the curl-pipe-bash install and install-local. macOS-scoped wording; harmless noise on Linux/Windows (which have no TCC). Renumbered the later steps.
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
📝 WalkthroughWalkthroughUpdated post-install instructions to add macOS-specific guidance for granting Accessibility and Screen Recording permissions, with command examples and correct launch-based flow, and reordered subsequent setup steps accordingly. ChangesmacOS Post-Install Permissions
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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.
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 `@libs/cua-driver/scripts/post-install-hints.txt`:
- Around line 14-15: Revise the tip to remove ambiguity about the "--autostart"
flag: either insert the missing command example above or change this line to a
self-contained sentence that shows the full command (e.g., "{{BINARY}}
permissions grant --autostart") and a brief note that the launchd daemon started
by "--autostart" keeps the helper running so macOS grants remain active across
reboots; reference the "--autostart" flag, the "{{BINARY}} permissions grant"
command, and "launchd daemon" in the updated text so readers know the exact
usage and why permission persistence occurs.
🪄 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: 6601101a-a254-42b9-9213-018e0cb0e2cf
📒 Files selected for processing (1)
libs/cua-driver/scripts/post-install-hints.txt
| # Tip: `--autostart` (above) keeps a launchd daemon | ||
| # running so you grant once and it persists. |
There was a problem hiding this comment.
Clarify the --autostart reference and usage.
Line 14 mentions "--autostart (above)" but --autostart is not mentioned anywhere above in the visible context. This creates confusion about:
- Where/how to use this flag (is it
{{BINARY}} permissions grant --autostart?) - Why a running daemon makes permission grants persist
- Whether this was intended to reference an installation step that should appear earlier
Either add the missing context above, or revise this tip to show the complete command syntax and explain the relationship between the daemon and permission persistence more clearly.
🤖 Prompt for 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.
In `@libs/cua-driver/scripts/post-install-hints.txt` around lines 14 - 15, Revise
the tip to remove ambiguity about the "--autostart" flag: either insert the
missing command example above or change this line to a self-contained sentence
that shows the full command (e.g., "{{BINARY}} permissions grant --autostart")
and a brief note that the launchd daemon started by "--autostart" keeps the
helper running so macOS grants remain active across reboots; reference the
"--autostart" flag, the "{{BINARY}} permissions grant" command, and "launchd
daemon" in the updated text so readers know the exact usage and why permission
persistence occurs.
Post-install "Next steps" went straight from try it to skills + MCP, never mentioning permissions — yet on macOS nothing works until Accessibility + Screen Recording are granted, and granting from a terminal silently attributes to the terminal, not the driver.
Adds a Grant permissions (macOS) step (new #2, ahead of skills/MCP since it's foundational) pointing at
cua-driver permissions status|grant(from #1765), with a tip toward--autostartfor grant-once persistence.Shared template so it shows on both the curl-pipe-bash install and install-local. macOS-scoped wording; harmless on Linux/Windows (no TCC).
🤖 Generated with Claude Code
Summary by CodeRabbit