Cline vs Qwen Code

Cline

Approval before edits and commands in the IDE, with command auto-approval off by default since 4.0.0. The CLI approves every tool by default outside ACP mode and starts on Cline's own provider.

Qwen Code

Apache-2.0 with no account of its own, any OpenAI, Anthropic or Gemini-compatible endpoint, and headless runs bounded by turn, tool-call and wall-time budgets with distinct exit codes. Out of the box, Auto mode lets an LLM classifier approve tool calls, with the sandbox and folder trust both off. Usage statistics are on by default.

Cline

1. Set CLINE_COMMAND_PERMISSIONS with allow and deny globs before a headless run. The CLI approves every tool by default
2. Pick a provider with -P and a key, or run cline auth. The default provider needs a Cline sign-in
3. Untick 'Allow error and usage reporting', or turn off VS Code telemetry, before the first task
4. Pin the CLI version. 2.3.0 was a malicious publish
5. Keep the hub on 127.0.0.1 or set ROOM_SECRET, and run 3.0.30 or later

Qwen Code

1. Pass --approval-mode on every run. The settings default is auto, and one docs page says headless runs default to asking, so don't rely on either
2. Add --max-session-turns, --max-wall-time and --max-tool-calls. All three are unlimited by default. Exit 53 is the turn limit and 55 a budget
3. --yolo doesn't turn on a sandbox. Add --sandbox, or on Linux set tools.executionSandbox with network set to closed
4. Set QWEN_USAGE_STATISTICS_ENABLED=false to stop usage statistics
5. Authenticate with OPENAI_API_KEY, OPENAI_BASE_URL and OPENAI_MODEL in CI. The browser sign-in is discontinued