docs: restore the macOS open -a CuaDriver … serve step in the first-app tutorial

[f-trycua]

Partially reverts #2087 for macOS only. That PR dropped the manual open -n -g -a CuaDriver --args serve step, but on macOS launching the daemon through the app bundle is what makes the TCC grant attribute to CuaDriver.app (com.trycua.driver) and register in System Settings — permissions grant alone isn't a reliable substitute in practice. Restored the step (with a note on why); Windows/Linux tabs stay as #2087 left them (no TCC). Content-only.

Summary by CodeRabbit

• Documentation
  • Updated the macOS setup guide with an additional step to start the driver daemon before granting permissions.
  • Clarified the flow for enabling Accessibility and Screen Recording permissions so prompts appear correctly during installation.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Jul 1, 2026 3:51pm

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ca2a5d65-388d-4311-89e7-7d3f078dabab

📥 Commits

Reviewing files that changed from the base of the PR and between 0a2c231 and 5257d5f.

📒 Files selected for processing (1)

• docs/content/docs/tutorials/drive-your-first-app.mdx

---

📝 Walkthrough

Walkthrough

Updates the macOS installation instructions in the "drive-your-first-app" tutorial to add a step launching the Cua Driver daemon via CuaDriver.app bundle, ensuring correct attribution of macOS permission prompts, followed by the Accessibility and Screen Recording permission grant step.

Changes

Tutorial Documentation Update

Layer / File(s)	Summary
Add CuaDriver launch step docs/content/docs/tutorials/drive-your-first-app.mdx	Adds a macOS-specific command (open -n -g -a CuaDriver --args serve) to start the driver daemon via the CuaDriver.app bundle and updates surrounding text to transition into the Accessibility and Screen Recording permission step.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• trycua/cua#1368: Both PRs update the macOS driver launch flow to use open -n -g -a CuaDriver --args serve for correct TCC permission attribution.
• trycua/cua#1760: Adds the same launch command referenced in this tutorial update, aligning docs with the underlying check_permissions behavior.
• trycua/cua#1767: Updates the same tutorial docs area around Accessibility and Screen Recording permission guidance following driver launch.

Poem

A hop, a skip, a driver's start,
One command to play its part—
"serve" the daemon, then grant with care,
Screen and Access, permissions aware. 🐰
Docs now hop in step so true!

🚥 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 accurately summarizes the main change: restoring the macOS CuaDriver daemon launch step in the first-app tutorial.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/restore-macos-serve-step

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}