docs: drop the manual cua-driver serve step from the first-app tutorial - #2087
Conversation
…rst-app tutorial The tutorial told users to start the daemon by hand (`cua-driver serve`, or on macOS `open -n -g -a CuaDriver --args serve`) in each install tab. That's not needed: the CLI (`doctor`/`call`) and the agent's MCP connection start the daemon automatically. Removed the daemon-start blocks from the macOS/Windows/Linux tabs; macOS keeps `permissions grant` (which launches CuaDriver itself for the TCC prompts). Section 2's verify step is unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011BJPGdRQxiBPTQhjwZsQ8G
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
📝 WalkthroughWalkthroughDocumentation update to the "Install Cua Driver" tutorial section. macOS instructions simplified to state that granting Accessibility and Screen Recording permissions launches CuaDriver. Windows and Linux tabs had follow-up manual daemon-start instructions (including ChangesTutorial install instructions update
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docs/content/docs/tutorials/drive-your-first-app.mdx (1)
31-46: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick winKeep the daemon startup step for Windows/Linux.
cua-driver doctorandcua-driver calldo not start the daemon, so the tutorial needs an explicitcua-driver serve/autostart step or users will hit a dead end on fresh installs.🤖 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 `@docs/content/docs/tutorials/drive-your-first-app.mdx` around lines 31 - 46, The platform-specific install sections for Windows/Linux are missing the daemon startup step, so update the tutorial in the drive-your-first-app doc to include an explicit `cua-driver serve` or autostart instruction after the install commands. Keep the existing Windows and Linux tabs, and add the startup guidance near the `cua-driver doctor`/`cua-driver call` workflow so users can get a running daemon on fresh installs.
🤖 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.
Outside diff comments:
In `@docs/content/docs/tutorials/drive-your-first-app.mdx`:
- Around line 31-46: The platform-specific install sections for Windows/Linux
are missing the daemon startup step, so update the tutorial in the
drive-your-first-app doc to include an explicit `cua-driver serve` or autostart
instruction after the install commands. Keep the existing Windows and Linux
tabs, and add the startup guidance near the `cua-driver doctor`/`cua-driver
call` workflow so users can get a running daemon on fresh installs.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 77102464-ea7a-4784-bdd3-e642670030fa
📒 Files selected for processing (1)
docs/content/docs/tutorials/drive-your-first-app.mdx
…d pnpm 9) The docs slimming's pnpm 11 install dropped the `overrides:` block from docs/pnpm-lock.yaml, so CI's pinned pnpm 9 (`packageManager: pnpm@9.0.4`) failed `pnpm install --frozen-lockfile` with ERR_PNPM_LOCKFILE_CONFIG_MISMATCH (breaking the docs link-check + Vercel builds on main). Regenerated the lockfile with pnpm 9 (`install --lockfile-only`) so package.json's overrides match; frozen install now passes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011BJPGdRQxiBPTQhjwZsQ8G
…n-start step (#2097) #2087 removed the manual `open -n -g -a CuaDriver --args serve` step from the macOS install tab on the theory that `cua-driver permissions grant` performs the same LaunchServices launch. In practice, 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 — so the step is load-bearing on macOS and is restored. Windows/Linux stay as-is (no TCC). Claude-Session: https://claude.ai/code/session_011BJPGdRQxiBPTQhjwZsQ8G Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
1 participant
The first-app tutorial told users to run
cua-driver serve(macOS:open -n -g -a CuaDriver --args serve) by hand in each install tab. That's unnecessary — the CLI (doctor/call) and the agent's MCP connection start the daemon automatically. Removed the daemon-start blocks from all three tabs; macOS keepspermissions grant(which launches CuaDriver itself).pnpm build+ link-check pass.Publishing: goes live on cua.ai/docs once the website docs-source ref is bumped to include this commit (see trycua/cloud #5308).
Summary by CodeRabbit