At a glance
An Apache-2.0 terminal coding agent with persistent auto-memory, headless execution, hosted and local providers, MCP, specialized subagents, built-in desktop Computer Use, IDE integrations, checkpoints, and opt-in macOS or container isolation.
Good choice if
- Terminal and CI workflows that can explicitly enable a first-party sandbox path
- Teams switching among Qwen, OpenAI-compatible, Anthropic, Gemini, and local endpoints
- Delegated coding tasks that benefit from constrained fork profiles, background workflows, MCP, skills, and IDE integrations
- Long-running Goals that need resumable continuation and durable evidence checkpoints rather than a fixed turn ceiling
Check before choosing
- The sandbox is off by default; `--yolo` does not enable it, and the default macOS profile allows network access while mainly restricting writes
- Checkpointing is also opt-in and restores tracked project state and conversation, not shell-created external side effects
- Auto-memory is enabled by default and can persist user or project knowledge; managed project memory in qwen serve remains Git-root-scoped by default, while exact-workspace isolation is opt-in
See 2 more considerations
- Opt-in background workflow runs are limited to interactive TUI sessions, remain blocked on parent approval, are cancelled when the owning process exits, and now support cooperative pause and resume but not restart recovery, remote workflows, or tracing
- The qwen serve daemon is an alpha local API: loopback starts without authentication, non-loopback binding fails closed without a bearer token, and the docs do not yet claim production-grade multi-client or network-failure guarantees