docs(cua-driver): Windows SSH workflow + autostart concept page - #1583
Conversation
Adds two sibling pages under guide/getting-started/ to close gaps in the cua-driver fumadocs that are heavily macOS-focused today: - windows-ssh.mdx: the "daemon in user's interactive Session 1+ → SSH or remote shell → cua-driver mcp/call proxies through the daemon → real GUI apps respond" workflow that just shipped in cua-driver-rs v0.2.7 (PR #1580). Covers the Session 0 problem, the canonical `autostart enable && kick` recipe, prerequisite (active interactive session — Active or Disc), opt-outs, and the v0.2.7 reason `mcp` now proxies the same way `call` always did. - autostart.mdx: concept page for the `cua-driver autostart` {enable,disable,kick,status} verb family. Documents what each verb does per platform (Windows = Scheduled Task with LogonType:Interactive, macOS/Linux still manual via install-local.sh --autostart), the daemon-survives-RDP-disconnect property, and the worked example. Also adds cross-link callouts in installation.mdx so the existing "Auto-start at logon (Windows)" and "TCC auto-delegation" sections point at the new pages, plus a sibling daemon-proxy callout for Windows/Linux. Docs-only; no code touched. Behaviour shipped in cua-driver-rs v0.2.7. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedPull request was closed or merged during review 📝 WalkthroughWalkthroughThis PR adds comprehensive documentation for Windows autostart and SSH-over-daemon-proxy workflows. It introduces a new ChangesWindows Autostart and SSH Daemon Proxy Documentation
🎯 2 (Simple) | ⏱️ ~12 minutes
🚥 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)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add 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 |
Summary
Adds two sibling pages under
docs/content/docs/cua-driver/guide/getting-started/to close two gaps in the cua-driver fumadocs, which today is heavily macOS-focused:windows-ssh.mdx— the "daemon in user's interactive Session 1+ → SSH (Session 0) →cua-driver mcp/callproxies through the daemon → real GUI apps respond" workflow. This is the actual ergonomic story for headless / remote Windows automation and nothing in the docs covered it before. Covers the Session 0 problem, the canonicalautostart enable && kickrecipe, the active-interactive-session prerequisite, opt-outs, and whymcpnow proxies the same waycallalways did (PR fix(cua-driver-rs): proxy MCP through daemon on Windows/Linux when one is up #1580, shipped in v0.2.7).autostart.mdx— concept page for thecua-driver autostart {enable, disable, kick, status}verb family. Documents per-platform mechanics (Windows = Scheduled Task withLogonType: Interactive; macOS/Linux Rust port still TBD — manual recipe viainstall-local.sh --autostart), the daemon-survives-RDP-disconnect property, and theenable && kickworked example.Both pages are linked from the existing Windows section of
installation.mdx(in the "common fixes for empty arrays" list and as a callout on the manual Scheduled Task block). A small sibling callout was also added under "TCC auto-delegation" to surface that the daemon-proxy mechanism now works on Windows / Linux too, addressing Session 0 rather than TCC.Decision on placement: new sibling pages under
getting-started/, not inline ininstallation.mdx. The installation page is already 619 lines, the SSH workflow needs its own discoverability (people searching "cua-driver ssh windows" need a page title that matches), and the autostart verb family deserves its own conceptual home as a sibling to the SSH workflow.Total new content: 292 lines across the two new MDX files + ~25 lines of cross-link edits in
installation.mdx. Inside the 300-500 line target.Scope
Docs-only PR. No code changes. The behaviours described shipped in
cua-driver-rsv0.2.7 (PR #1580 —should_use_daemon_proxyon Windows/Linux) and theautostartverb family already in the Rust port.Files changed
docs/content/docs/cua-driver/guide/getting-started/windows-ssh.mdx(new)docs/content/docs/cua-driver/guide/getting-started/autostart.mdx(new)docs/content/docs/cua-driver/guide/getting-started/meta.json(added the two new page slugs to the ordered list)docs/content/docs/cua-driver/guide/getting-started/installation.mdx(cross-link callouts in 3 places; no content moved out)Test plan
pnpm devindocs/renders both new pages with working internal links to each other and to existing installation.mdx anchorswindows-sshandautostartbetweenquickstartandintegrations(sidebar reads top-to-bottom in workflow order)#auto-start-at-logon-windows,#windows-interactive-session-requirements,#install-cua-driver-rs-directly-linux--windows--macos,#uninstall) resolve against the currentinstallation.mdx<Callout>components render in both new pages (already imported fromfumadocs-ui/components/callout)🤖 Generated with Claude Code
Summary by CodeRabbit