droid-control — Claude Code skill: control apps and terminals
droid-control is a skill for automating terminal TUIs, browsers, and desktop apps. Record demos, run tests in real environments, and capture QA proof.
no license 118 installs ★ 129 updated 2026-10-25
npx skills add Factory-AI/factory-plugins --skill droid-control -a claude-codeWhat droid-control does
droid-control routes commands to the right driver: tuistory for terminal sessions, browser-use for web pages and Electron apps, cua for native GUI applications. The skill handles non-deterministic behavior — network latency, variable output, LLM responses — by waiting or pausing between actions. When an action fails or feels uncertain, it observes the current state and retries without switching drivers or escalating permissions.
Each component (terminal-use, browser-use, desktop-use, capture, compose, verify) is a separate file at ${DROID_PLUGIN_ROOT}/skills/droid-control/atoms/. The skill reads them in order: identify the target app, choose which stages to load (record, assemble, verify). Terminal sessions use tctl, which wraps asciinema rec and isolates each run with a RUN_ID and temp directory so concurrent sessions don't collide.
When building demo or QA artifacts, compose assembles video via fframes: title cards, layouts, transitions, effects. Verify checks the result against stated goals. The default is single-clip layout (one scene); side-by-side is not created automatically unless the deliverable is explicitly a comparison.
What it helps with
- Record terminal or browser screen with proof of feature behavior
- Automate clicks and input in a native desktop application
- Build a video demo with title cards, transitions, and visual effects
- Run tests in real environments instead of mocks
- Capture GUI application behavior for QA reporting
Example prompts for the agent
- Record me typing in the terminal and running
npm teston a real project - Open a browser, navigate to the site, and click the payment button—record the screen as video
- Automate clicks in a macOS app and build a video demo with a branded title card
How to install droid-control
1Skills CLI (Vercel)
npx skills add Factory-AI/factory-plugins --skill droid-control -a claude-code2Manually: put the files in place
~/.claude/skills/droid-control/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/droid-control/
1Skills CLI (Vercel)
npx skills add Factory-AI/factory-plugins --skill droid-control -a codex2Manually: put the files in place
.agents/skills/droid-control/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Factory-AI/factory-plugins --skill droid-control -a cursor2Manually: put the files in place
.cursor/skills/droid-control/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Factory-AI/factory-plugins plugins/droid-control/skills/droid-control2Manually: put the files in place
.github/skills/droid-control/SKILL.md1Skills CLI (Vercel)
npx skills add Factory-AI/factory-plugins --skill droid-control -a gemini-cli2Platform CLI
gemini skills install https://github.com/Factory-AI/factory-plugins --path plugins/droid-control/skills/droid-controlManually: put the files in place
.devin/skills/droid-control/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Factory-AI/factory-plugins --skill droid-control -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about droid-control
How do I install droid-control in Claude Code?
Run npx skills add Factory-AI/factory-plugins --skill droid-control -a claude-code, then open ~/.claude/skills/droid-control/SKILL.md to confirm.
What does droid-control do?
It drives terminals, browsers, and applications for testing, demos, and QA. Records sessions, composes them into video with effects, and verifies results against goals.
Which apps and platforms does it support?
Terminal TUIs via tuistory, web pages and Electron apps via browser-use, native GUI apps via cua on the desktop. Real terminal proof uses true-input with a Wayland compositor or VM.