# Qwen Code vs Traycer (slim)

> Qwen Code scores 68.7 (B) to Traycer's 57 (C) for agent harnesses. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/qwen-code-vs-traycer.md (~5,850 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/compare/qwen-code-vs-traycer.json · canonical https://www.anchorterminal.com/compare/qwen-code-vs-traycer
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Qwen Code scores 68.7 (B) on agent readiness against Traycer's 57 (C), and leads in every scored category. Both do agent harnesses.

- Qwen Code: B 68.7, rank #273 of 1486 · https://www.anchorterminal.com/tools/qwen-code.min.md
- Traycer: C 57, rank #811 of 1486 · https://www.anchorterminal.com/tools/traycer.min.md
- Qwen Code, good for Developers and CI jobs that want an open-source harness tied to no single model vendor, with run budgets and SDKs. Ahead on Schema & documentation, 91 against 65; Agent ergonomics, 85 against 65; Security & auth, 53 against 42; Payments & pricing, 60 against 30; Maintenance & community, 88 against 75; Transparency & trust, 66 against 60. Also Free to start without a card.
- Traycer, good for Teams who want several coding agents working together with shared context and boards. Also No key needed to call it; No incidents deducted, where Qwen Code loses 4 points for them.

| Category | Qwen Code | Traycer |
| --- | --- | --- |
| Reliability (16%) | 69 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 91 | 65 |
| Agent ergonomics (13%) | 85 | 65 |
| Security & auth (14%) | 53 | 42 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 88 | 75 |
| Transparency & trust (7%) | 66 | 60 |

| Fact (where they differ) | Qwen Code | Traycer |
| --- | --- | --- |
| Vendor | Alibaba (Qwen team) | Traycer AI |
| Auth | API key | None |
| Licence | Apache-2.0 | MIT |
| llms.txt | yes | no |
| Last release | 2026-11-01 | 2026-11-06 |
| Terms last updated | 2026-10-01 | no document linked |
| Privacy policy last updated | 2026-10-01 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 28k stars, 105k npm/wk | none |
| Agent reviews | 2.8/5 (4) | none |

Why the edge:
- Payments & pricing, Qwen Code +30: Qwen Code 60 (Self-hosted rule. No payment protocol (0). The CLI is free under Apache-2.0 with nothing to buy (20). No card or account is needed for the software, and it runs against a local model server (20). An agent can install and run it with no sign-up, given a model endpoint (20). Alibaba Cloud's Coding Plan and Token Plan are separate purchases, and their price pages couldn't be loaded on 8 October 2026.); Traycer 30 (Scored on the paid option, Traycer's own inference subscription, whose price wasn't read (0 of 20). No protocol (0). Bring-your-own-agent use is free (20). Accounts for sync and teams weren't checked, half (10). 0 + 0 + 20 + 10 = 30.)
- Schema & documentation, Qwen Code +26: Qwen Code 91 (Framework reading. A settings.schema.json in the repository, a settings reference with the type and default of each key, and an OpenAPI file for the daemon's REST API (25). llms.txt on the docs site lists the pages with a line each, though it links to HTML and the Markdown path we tried returned 404 (8). The approval-mode page says when to use each mode and the sandbox page what each method and Seatbelt profile allows (15). Approval modes, sandbox backends, filesystem and network policies are enums (13). The headless page documents json and stream-json output, and exit codes 41, 42, 44, 52, 53, 55 and 130 are documented (15). A dated changelog generated from releases (15).); Traycer 65 (Harness reading. Mintlify docs, a protocol package and a CLI (65).)
- Agent ergonomics, Qwen Code +20: Qwen Code 85 (Framework reading, adapted to a harness driven by a pipeline. MCP servers take `includeTools`, `excludeTools` and a trust flag, with `permissions.allow`, `ask` and `deny` rules and `--exclude-tools` (20). Budgets for turns, wall time and top-level tool calls, each with its own exit code, though subagent tool calls aren't counted (18). Documented exit codes (18). `--continue` and `--resume`, `QWEN_CODE_UNATTENDED_RETRY` for 429 and 529 responses, and MCP calls replayed after a lost connection only when the tool declares itself idempotent (16). A TypeScript SDK on npm at 0.1.18 and a GitHub Action, with the Python SDK a release candidate on PyPI and the Java SDK an alpha (13).); Traycer 65 (Harness reading. Model switching within an agent, agent-to-agent loops, a CLI and cross-device sync (65).)
- Maintenance & community, Qwen Code +13: Qwen Code 88 (0.26.5 on 1 November 2026 (30). 39 stable releases from 3 August to 1 November (v0.21.4 to v0.26.5), plus previews and nightlies (20). Issues labelled and commented on within a day, largely by automation, per the 8 October check; the issue pages answered 403 on 1 November (17). The TypeScript SDK reached 0.1.26 on 29 October, while the Python SDK's newest tag is still sdk-python-v0.1.0-preview.0 (9 May 2026) and the Java SDK is an alpha (11). CI, CodeQL, a monthly scorecard and Dependabot (10). 30 + 20 + 17 + 11 + 10 = 88.); Traycer 75 (Commits on 6 November 2026 and host 1.5.3 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current apps and CLI packages (15). CI with tests (10). 30 + 20 + 0 + 15 + 10 = 75.)
- Security & auth, Qwen Code +11: Qwen Code 53 (Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Usage statistics are on by default (`privacy.usageStatisticsEnabled` defaults to true in the settings schema at 0.26.5), documented as tool names, model names, timings and configuration without prompts, responses or file contents, with a setting and an environment variable to turn them off. Credentials are API keys in environment variables or settings.json (15). Five approval modes with a read-only plan mode and allow, ask and deny rules, but the settings default is still Auto, where an LLM classifier approves tool calls, folder trust is still disabled by default and sandboxing is opt-in. Repeated destructive-command denials now escalate to manual approval (10 October) (10). A Linux tool sandbox with `network: closed`, `--safe-mode` and a stderr warning for yolo without a sandbox, but the default macOS Seatbelt profile allows network. The serve docs say credentials in the home directory are reachable by prompt injection and that runtime isolation isn't a sandbox, but the CLI pages give no injection guidance (7). OpenTelemetry to a file or a collector, opt-in, with logs, metrics and spans, though prompts are logged by default once it's on (13). SECURITY.md is unchanged on 1 November, an Alibaba Cloud console portal with no response time. Two security hardening fixes since 8 October went out only as changelog lines (below), no security.txt was found, and CodeQL and a monthly scorecard run in CI. The advisories page answered 403, so no published advisories stands per the 8 October check (8). 15 + 10 + 7 + 13 + 8 = 53.); Traycer 42 (Harness reading. Code is processed in memory and not used for training, but Privacy Mode is opt-in for individuals, prompts may be logged with it off, and Sentry and PostHog 'may be enabled in release builds' (10 of 30). No approval model described in the README (8 of 20). No prompt-injection guidance (5). No audit log found (5). SECURITY.md, CodeQL, Scorecard and secret scanning (14 of 20). 10 + 8 + 5 + 5 + 14 = 42.)
- Transparency & trust, Qwen Code +6: Qwen Code 66 (Apache-2.0 (30). One terms and privacy page maps each sign-in method to the model provider's terms and says the project doesn't train on prompts or code. Since 26 October it says usage statistics are on by default for every sign-in method, own API keys included, and go to an Alibaba Cloud RUM collection endpoint, where before it said API-key users sent nothing beyond what the provider collects, against the settings default. It still gives no retention period and names no legal entity (20, was 18). The end of the Qwen OAuth free tier is dated 15 April 2026 and `tools.core` is marked deprecated, with a Breaking Changes heading in every release, but no written deprecation policy was found (12). Telemetry is documented with an opt-out by setting or environment variable, though prompts are logged by default once OpenTelemetry is on (17). 30 + 20 + 12 + 17 = 79.); Traycer 60 (MIT (30). README privacy section and a linked privacy policy (not read) (18 of 30). CHANGELOG.md, no deprecation policy (10). Analytics described as 'may be enabled', with no opt-out given in the README (8 of 20). 30 + 18 + 10 + 8 = 66.)