Droid CLI vs MiniMax Code

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.

MiniMax Code

An MIT-licensed terminal coding agent with a headless mode that returns versioned JSON, documented exit codes and an ACP server, and telemetry off by default. It's pre-1.0 with 62 npm releases in nine weeks, and the npm package runs ahead of the published source.

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

MiniMax Code

1. Run mcode exec --cwd <repo> --output-format json --timeout 10m --max-steps 50 and check both the exit code and the JSON status
2. Keep --permission full and off for a container or throwaway workspace. The default smart fails when it would need a person
3. Set MCODE_PROVIDER_API_KEY and add a provider for BYOK. M Plan models need a browser sign-in with mcode login --region global
4. Set MINIMAX_DATA_DIR per CI runner. Keys and sessions live in ~/.minimax by default
5. Pin a version. npm published 62 releases in nine weeks and the public source trails it