Droid CLI vs OpenHands

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.

OpenHands

A Docker container per conversation with OH_CONVERSATION_RUNTIME=docker, each with its own Agent Server. Confirmation mode is off by default in Agent Canvas, and the npm install gives the agent the host's whole filesystem.

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

OpenHands

1. Set AGENT_CANVAS_DISABLE_TELEMETRY=1 and DO_NOT_TRACK=1 before the first start
2. Start Canvas with OH_CONVERSATION_RUNTIME=docker or use the Docker image. The npm install runs the agent on the host
3. Turn on confirmation mode with a risk threshold. Canvas starts with it off
4. Use the SDK or the Agent Server API for headless runs. The openhands --headless CLI is no longer maintained
5. Set filter_tools_regex on the agent to keep unneeded MCP tool definitions out of the context