Aider vs Droid CLI

Aider

Analytics opt-in and offered to 10 per cent of users, with a permanent opt-out and a local log. No release since 0.86.2 on 12 February 2026 and no commit since 22 May 2026.

Droid CLI

droid exec is read-only unless --auto raises the autonomy level, with command rules, an optional kernel-enforced sandbox, JSON output and documented exit codes. No free tier, status page or security.txt was found, the source is closed, and usage metrics go to Factory by default.

Aider

1. Read .aider.conf.yml in any cloned repository before starting aider. Its test-cmd and lint-cmd run without asking
2. Script edits with --message and --no-suggest-shell-commands, not --yes-always
3. Use Python 3.12 or earlier for the PyPI release
4. Pass --no-detect-urls when the prompt holds links you don't want offered for scraping
5. Check git log after a run. Each edit is its own commit

Droid CLI

1. Set FACTORY_API_KEY (starts fk-) from the API keys page in Factory settings for headless runs. Interactive use signs in through a browser
2. Start with droid exec and no flags for analysis. Add --auto low for edits and --auto medium for installs, tests and local commits
3. Use --output-format json and read is_error, num_turns and session_id. Treat a non-zero exit code as failure
4. Set sandbox.enabled to true before running on untrusted code. In droid exec a sandbox violation is denied without a prompt
5. Pin the version in CI with npm install -g droid@<version>, or set FACTORY_DROID_AUTO_UPDATE_ENABLED=false on standalone installs, which update themselves