Skip to content

docs(cua-driver-rs): surface permissions status|grant in post-install hints#1767

Merged
f-trycua merged 1 commit into
mainfrom
docs/post-install-permissions-hint
May 30, 2026
Merged

docs(cua-driver-rs): surface permissions status|grant in post-install hints#1767
f-trycua merged 1 commit into
mainfrom
docs/post-install-permissions-hint

Conversation

@f-trycua
Copy link
Copy Markdown
Collaborator

@f-trycua f-trycua commented May 30, 2026

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 --autostart for 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

  • Documentation
    • Enhanced macOS setup instructions with new guidance for granting Accessibility and Screen Recording permissions, including steps to check current status and enable access as needed.

Review Change Stack

…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.
@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 30, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
docs Ignored Ignored Preview May 30, 2026 3:56am

Request Review

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 30, 2026

📝 Walkthrough

Walkthrough

Updated 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.

Changes

macOS Post-Install Permissions

Layer / File(s) Summary
macOS Accessibility and Screen Recording permissions guidance
libs/cua-driver/scripts/post-install-hints.txt
Added new step with instructions to check current permission status and grant Accessibility and Screen Recording permissions via LaunchServices-based flow. Subsequent "Agent skill pack (optional)" and "As an MCP server" steps are reordered after the new permissions guidance.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • trycua/cua#1368: Updates macOS post-install permissions flow with check_permissions command and LaunchServices guidance for same Accessibility and Screen Recording permissions.
  • trycua/cua#1681: Modifies the same post-install-hints.txt file, adjusting step flow and MCP setup instructions.
  • trycua/cua#1760: Related to check_permissions behavior and LaunchServices-based permission-grant flow for macOS Accessibility and Screen Recording.

Poem

🐰 A door opens wide, permissions aligned,
Screen Recording and Accessibility intertwined,
macOS needs consent, with commands so bright,
Now users can grant permissions just right!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly and specifically describes the main change: surfacing the permissions status/grant commands in post-install hints documentation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/post-install-permissions-hint

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

📥 Commits

Reviewing files that changed from the base of the PR and between be8ecec and 1a9b403.

📒 Files selected for processing (1)
  • libs/cua-driver/scripts/post-install-hints.txt

Comment on lines +14 to +15
# Tip: `--autostart` (above) keeps a launchd daemon
# running so you grant once and it persists.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

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.

@f-trycua f-trycua merged commit f31e720 into main May 30, 2026
7 checks passed
@f-trycua f-trycua deleted the docs/post-install-permissions-hint branch May 30, 2026 20:34
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.

1 participant