Qwen Coder CLI Command Reference

# Interactive mode
qwen

# Non-interactive single prompt (recommended for delegation)
qwen -p "<english-prompt>"

# Non-interactive prompt
qwen -p "Analyze this codebase architecture"

# Continue previous session by ID
qwen -c <session-id> -p "Continue analysis and focus on auth module"

# Resume previous session by ID
qwen -r <session-id> -p "Continue analysis and focus on auth module"

# Code generation with production quality
# Best for: boilerplate, CRUD endpoints, standard patterns
qwen -p "Generate a production-ready REST API endpoint for CRUD operations on items. Include input validation, error handling, and unit tests. Use Express.js framework." -m qwen2.5-coder --approval-mode auto_edit

# Documentation generation
# Best for: JSDoc, README sections, API docs
qwen -p "Generate comprehensive documentation for the UserService class. Include: class purpose, public methods with parameters, usage examples, and error handling patterns. Format as markdown." -m qwen2.5-coder --approval-mode plan

# Structured JSON output for automation
# Best for: data extraction, code analysis, tooling integration
qwen -p "Analyze this codebase and return the top 5 refactoring opportunities as a JSON array. Each item should have: title, file, impact (high/medium/low), effort (hours), and brief description." -m qwen2.5-coder --output-format json

# Deep security analysis
# Best for: thorough security reviews, vulnerability assessment
qwen -p "Analyze the authentication module for security vulnerabilities. Report only high-confidence issues with severity, file paths, and remediation steps." -m qwq --approval-mode plan

# Architectural design reasoning
# Best for: system design, migration planning, complex refactoring
qwen -p "Analyze the current system architecture and propose a detailed migration strategy to microservices. Include component boundaries, communication patterns, data ownership, and estimated risks for each migration step." -m qwq --approval-mode plan

# Complex multi-file refactoring
# Best for: cross-module changes, architectural refactors, deep reasoning
qwen -p "Refactor the payment module for better error handling. Consider transaction boundaries, retry logic, and idempotency. Propose a detailed plan before implementing." -m qwq --approval-mode plan

# Default approval (recommended baseline)
qwen -p "<english-prompt>" --approval-mode default

# Auto-approve edits
qwen -p "<english-prompt>" --approval-mode auto_edit

# Read-only planning mode (preferred for analysis)
qwen -p "<english-prompt>" --approval-mode plan

# YOLO mode (only with explicit user consent)
qwen -p "<english-prompt>" --approval-mode yolo

# Plain text (default)
qwen -p "<english-prompt>"

# JSON output for automation
qwen -p "<english-prompt>" --output-format json

# Streaming JSON output
qwen -p "<english-prompt>" --output-format stream-json

# Security review in read-only mode
qwen -p "Analyze this codebase for high-confidence security vulnerabilities with file paths and fixes." --approval-mode plan

# Session continuation for ongoing work
qwen -c <session-id> -p "Continue from previous session. Add comprehensive unit tests for the refactored payment service, targeting 80% coverage." --approval-mode default

# Multi-model comparison for quality check
qwen -p "Refactor the string utility module for better maintainability." -m qwen2.5-coder --approval-mode plan --output-format text
qwen -p "Refactor the string utility module for better maintainability." -m qwq --approval-mode plan --output-format text

# Verify CLI availability
qwen --version

# Check authentication status
qwen auth status

# See help
qwen --help