docs(cli): cover desktop-control driver on the droid-control page#1215
Open
factory-ain3sh wants to merge 1 commit into
Open
docs(cli): cover desktop-control driver on the droid-control page#1215factory-ain3sh wants to merge 1 commit into
factory-ain3sh wants to merge 1 commit into
Conversation
…I-900) factory-plugins#27 adds a fourth automation backend (native desktop GUI apps via trycua/cua cua-driver) to the droid-control plugin. Update the feature page to match: fourth driver card, atom count 10 -> 11, install prerequisites accordion (incl. Windows install.ps1 and macOS permissions grant), and desktop/cua-driver keywords for search. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
Contributor
|
Droid finished @factory-ain3sh's task —— View job Docs update looks consistent with the new desktop-control driver addition, but the prerequisites section currently instructs running upstream install scripts via pipe-to-shell without a safety note or pinning guidance. |
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
factory-ain3sh
added
the
documentation
![factory-droid[bot]](https://avatars.githubusercontent.com/in/358017?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Factory-AI/factory-plugins#27 adds a fourth automation backend to the droid-control plugin: native desktop GUI apps via trycua/cua
cua-driver(macOS/Windows production tier, Linux pre-release). The feature page still described three backends; this PR brings it in line: a fourth driver card, atom count 10 -> 11, a prerequisites accordion with per-OS install notes (Windowsinstall.ps1, macOSpermissions grant), and desktop/cua-driver search keywords.Related Issue
Part of CLI-900 (closed by the plugin PR).
PR lineage: pairs with Factory-AI/factory-plugins#27 -- merge order independent, but docs should not ship long before the plugin lands.
Reviewer Guide
Read order:
docs/cli/features/droid-control.mdxonly -- the new driver card (Automation drivers), the new accordion (Prerequisites), then the one-word count/keyword touches.Review depth: Skim -- single-page docs update mirroring already-reviewed plugin content.
Open for pushback: the command tabs (
/qa-testetc.) deliberately do not claim native-desktop support, since the plugin's command docs don't enumerate that target yet.Risk & Impact
Low risk -- isolated to one MDX page.
docs/jp/mirror is intentionally untouched (auto-synced bysync-jp-docs.ymlon merge to main).Verification
Behavior verified. Page content mirrors the shipped plugin state in factory-plugins#27, where the underlying claims were smoke-tested (Windows VM end-to-end, local Linux) (verified @ c6a19d1).
Regression coverage. N/A -- prose-only change; no harness for docs content beyond link checking.
Not tested. Rendered preview (
mintlify dev) not run; component usage (Card/Accordion) matches existing patterns on the same page.Standard validators.
mintlify broken-links: no broken links found; no other validators configured fordocs/.