droid-cli
Background knowledge for droid-control workflows -- not invoked directly. Droid CLI target patterns, shortcuts, modes, and launch helpers.
How do I install this agent skill?
npx skills add https://github.com/factory-ai/factory-plugins --skill droid-cliIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill provides documentation and background knowledge for the Droid CLI tool. It contains no executable code, malicious instructions, or data exfiltration patterns.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Droid CLI Target
The orchestrator routed you here. Layer these target-specific patterns on top of the driver skill you already loaded.
Droid-specific shortcuts, modes, and launch patterns.
Shortcuts
| Action | Key chord | Result |
|---|---|---|
| Toggle Spec mode | shift tab | toggles Spec mode on/off |
| Cycle autonomy | ctrl l | Off > Low > Med > High > Off |
| Cycle models | ctrl n | cycles available models |
| Cycle reasoning | tab | High > none > Low > Medium > High |
| Cancel / close / stop | esc | stops streaming, closes overlays |
| Clear input | ctrl u | clears current line |
| Toggle bash mode | ! on empty input | switches prompt between > and $ |
| Help / shortcuts | ? | opens keybinding help |
| Multiline input | shift enter | inserts newline without submitting |
Dialogs
When a dialog shows Use up/down to navigate...: up/down moves the highlight, enter selects, esc closes.
Slash commands
| Command | Purpose |
|---|---|
/help | Show commands |
/settings | Open settings menu |
/model | Open model selector |
/clear or /new | Start a new session |
/sessions | Browse previous sessions |
/status | Show current config |
/cost | Show usage / cost |
/compress [prompt] | Summarize and move to fresh session |
File mentions
Type @ to open file suggestions, filter by typing, tab to accept, esc to cancel:
$TCTL -s demo type "review @"
$TCTL -s demo type "package.json"
$TCTL -s demo press tab
Visual cues
| State | What to look for |
|---|---|
| Spec mode on | input border shows Spec |
| Bash mode on | prompt is $ |
| Idle / ready | prompt is > with no spinner |
| Dialog open | boxed menu + navigation hint |
| File suggestions | dropdown under input |
| Thinking | Thinking... and stop hint |
Launching Droid
How droid-dev works
droid-dev is a thin bash shim at ~/.local/bin/droid-dev. It runs bun against whichever checkout DROID_DEV_REPO_ROOT points to — it does NOT use a pre-compiled binary. This means:
- No per-branch builds. One
npm run setup(in any checkout) installs the shim. Switching branches is instant via--repo-root. - Prerequisite: The target worktree must have
node_modulesinstalled (npm installat the repo root). If missing, the bun launch fails. tctl --repo-rootsetsDROID_DEV_REPO_ROOTautomatically and pins the session to that worktree.tctl --cwdis independent of--repo-root: run droid against one worktree's code while sitting in a different project directory (e.g., a scratch project with its own.factory/settings.jsonhooks). Defaults to--repo-rootwhen unset.
droid-dev
droid-dev launches require --repo-root (or --env DROID_DEV_REPO_ROOT=...). tctl enforces this — launches without it will fail:
# tuistory (default — virtual PTY)
$TCTL launch "droid-dev" -s demo --backend tuistory \
--repo-root /path/to/worktree \
--cols 120 --rows 36
# true-input (real terminal proof — headless Wayland compositor)
$TCTL launch "droid-dev" -s demo --backend true-input \
--repo-root /path/to/worktree
Feature branch / worktree
For comparisons, launch separate sessions pointing at different worktrees:
$TCTL launch "droid-dev" -s before --backend tuistory \
--repo-root /path/to/baseline-worktree \
--cols 120 --rows 36 --record /tmp/before.cast \
--env FORCE_COLOR=3 --env COLORTERM=truecolor
$TCTL launch "droid-dev" -s after --backend tuistory \
--repo-root /path/to/candidate-worktree \
--cols 120 --rows 36 --record /tmp/after.cast \
--env FORCE_COLOR=3 --env COLORTERM=truecolor
Comparison setup (before/after demos)
For before/after comparisons, you need two worktree paths — one for the baseline and one for the candidate.
- Find existing worktrees:
git worktree listin any checkout. The main clone (often ondevormain) is a valid baseline. - Create if needed:
git worktree add /tmp/baseline-worktree dev(or the relevant base branch). - Ensure
node_modules: Runnpm installin any worktree that lacks it. This is the only setup needed — nonpm run setupor CLI build per branch. - Launch with
--repo-root: Eachtctl launchpins to one worktree.
Environment safety
tctl's runner script launches droid-dev via bash -lc, which loads a clean login shell. Stale FACTORY_* env vars from parent processes are typically overridden by the runner. If you suspect env contamination, pass explicit overrides with --env.
Exec mode
Non-interactive single-shot execution:
droid exec "analyze this file"
droid exec --auto medium "run the tests"
Logging
Enable debug logging by passing the log file path via --env:
$TCTL launch "droid-dev" -s demo --backend tuistory \
--repo-root /path/to/worktree \
--env FACTORY_LOG_FILE=/tmp/droid-test.log
tail -f /tmp/droid-test.log
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/factory-ai/factory-plugins/droid-cli">View droid-cli on skillZs</a>