mirror of https://github.com/QwenLM/qwen-code.git synced 2026-08-22 07:04:58 +00:00

docs: add vertex-ai auth, missing commands, and qc-helper index entries (#5727 )

* docs: add CLI subcommands section with qwen sessions list

- Add section 5 to commands.md for CLI-level subcommands
- Document qwen sessions list with --json and --limit flags
- Include output format, examples, and usage patterns

The sessions list command was added in commit 14e6ae8c2 but not documented.

* docs: add vertex-ai auth, missing commands, and qc-helper index entries

Audit docs/ against current codebase and fix high-impact drift:

- Add vertex-ai to auth.md, model-providers.md, and tos-privacy.md supported
  auth type tables (was missing from all three)
- Add missing slash commands to commands.md: /cd, /import-config, /workflows
- Add /doctor subcommands (memory, cpu-profile, rollback) and /extensions
  subcommands (list, manage, explore, install) to commands.md
- Add undocumented altNames: /clear→/reset,/new; /stats→/usage;
  /auth→/connect,/login; /resume→/continue; /compress→/summarize
- Add 8 missing feature entries to qc-helper SKILL.md topic index:
  code-review, followup-suggestions, tool-use-summaries, markdown-rendering,
  structured-output, dual-output, channels, tips
- Fix CLI binary name in contributing.md (qwen-code → qwen)

* docs: resolve review feedback on auth count, /workflows usage, GOOGLE_MODEL example

- auth.md: correct intro count from 'four' to 'three' methods (3 bullets + 3 Options; Vertex AI is a provider under API Key)
- commands.md: add '/workflows <runId>' to usage column to match argumentHint '[runId]'
- model-providers.md: add required GOOGLE_MODEL to the Vertex AI env example so it matches the prose and modelConfigUtils requirement

* docs: remove duplicate /workflows row introduced by main merge

main already documents /workflows (with the <runId> usage); the branch
merge kept both rows, leaving a duplicate in the Tool and Model
Management table. Drop the redundant row added by this PR.

* docs: resolve review feedback — /extensions explore source arg, CLI-name remnants

- commands.md: /extensions explore requires a <source> (exploreAction errors 'Unknown extensions source' without it)
- contributing.md: finish the qwen-code -> qwen CLI rename on the debug note (binary + .qwen config dir); repo-name references left intact

* docs: resolve review feedback — Vertex AI in tos-privacy, /doctor rollback clarity

- tos-privacy.md: propagate Vertex AI (which the header already counts as the 4th method) into the Data Collection list, FAQ Q1 and Q3, and add a '4. If you are using Vertex AI' section pointing to Google Cloud terms — fixes the four-vs-three internal inconsistency
- commands.md: clarify /doctor rollback rolls back the standalone CLI binary (standalone installs only) and disambiguate from /rewind's rollback alias (doctorCommand.ts gates on isStandalone)

* docs: resolve review feedback — clear semantics, doctor argHints, arrow spacing

- /clear: fix description to 'Clear conversation history and free up context' and drop the misleading '(shortcut: Ctrl+L)' grouping; Ctrl+L only clears the screen (clearScreen), it does not reset the session like /clear (clearCommand.ts)
- Ctrl/cmd+L keyboard row: clarify it clears the visible screen only, not 'Equivalent to /clear'
- /doctor memory and /doctor cpu-profile: surface the full argumentHints ([--sample] [--snapshot], [--duration <seconds>]) from doctorCommand.ts
- normalize section 1.4 arrow subcommands to spaced '→ ' style (approval-mode rows were the lone outliers)

* docs: resolve review feedback — enumerate /extensions explore sources

List the two valid sources (Gemini, ClaudeCode) from EXTENSION_EXPLORE_URL in extensionsCommand.ts so users can discover them without trial and error.

* docs: resolve review feedback — add extensions install security warning

/extensions install (extensionsCommand.ts) installs arbitrary git repos/paths with no confirmation prompt; add a warning that extensions run with full Qwen Code permissions and should only come from trusted sources.

* docs: resolve review feedback — add /stats subcommands, /auth aliases in 1.11

- commands.md: add /stats daily, /stats monthly, /stats export rows (registered in statsCommand.ts with day/month aliases and --format csv|json)
- section 1.11: note /auth's /connect and /login aliases (parallel to section 1.4)

* docs: resolve review feedback — /stats export full args, /summarize note

- /stats export: show the full argumentHint ([date|month] and [--output path]) from statsCommand.ts
- add a note disambiguating /summarize (alias of /compress, destructive) from /summary (project summary)

* docs: resolve review feedback — complete /arena /ide /directory /voice /mcp usage

Add the missing subcommands/arguments shown in the command sources:
- /arena: stop, select (arenaCommand.ts)
- /ide: enable, disable (ideCommand.ts)
- /directory: show (directoryCommand.tsx)
- /voice: hold, tap, off (voice-command.ts argumentHint)
- /mcp: nodesc, schema, auth, noauth (mcpCommand.ts argumentHint)

* docs: resolve review feedback — arena/stats aliases, trim /stats description

- /arena select: note alias 'choose' (arenaCommand.ts)
- /stats daily, /stats monthly: label day/month as aliases (statsCommand.ts)
- /stats: trim the description to a terse behavior-focused line (drop volatile tab names/keyboard shortcuts that belong in the dashboard help)

* docs: resolve review feedback — /copy args, /doctor memory --snapshot warning

- /copy: document language/latex/mermaid/index selection (copyCommand.ts argumentHint)
- add a warning that /doctor memory --snapshot writes a heap snapshot with sensitive data (matches doctorCommand.ts runtime warning)

* docs: resolve review feedback — mcp/approval-mode/copy accuracy, qwen privacy URL

- /mcp: drop deprecated auth/noauth (mcpCommand.ts argumentHint is now desc|nodesc|schema; auth/noauth are stubs)
- /approval-mode: drop nonexistent --project (mode is session-only), show actual invocations, add a safety warning for auto-edit/auto/yolo
- /copy: note N = Nth-last reply (copyCommand.ts)
- tos-privacy: unify Qwen Privacy Policy URL to qwen.ai/privacypolicy

* docs: resolve review feedback — import-config args + feature-gated commands note

- /import-config: show 'all' (default source) and enumerate --scope user|project (importConfigCommand.ts)
- add a note that /workflows, /lsp, /trust register only when their feature setting is enabled (BuiltinCommandLoader.ts gates them, default off)

* docs: fix feature-gating mechanisms + restore /stats tab names

- Correct the /workflows/lsp/trust note: actual gates are QWEN_CODE_ENABLE_WORKFLOWS=1 (env),
  --experimental-lsp (CLI flag), and security.folderTrust.enabled (setting) — the prior
  workflowsEnabled/lsp.enabled/folderTrust keys did not exist
- /stats: restore the Session/Activity/Efficiency tab names (dashboard contents are not
  documented elsewhere); keep volatile keyboard hints out per the earlier review

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>

2026-06-25 06:58:10 +00:00

7.9 KiB

Raw Permalink Blame History

Qwen Code: Terms of Service and Privacy Notice

Qwen Code is an open-source AI coding assistant tool maintained by the Qwen Code team. This document outlines the terms of service and privacy policies that apply when using Qwen Code's authentication methods and AI model services.

How to determine your authentication method

Qwen Code supports four authentication methods to access AI models. Your authentication method determines which terms of service and privacy policies apply to your usage:

Qwen OAuth — Log in with your qwen.ai account (free tier discontinued 2026-04-15)
Alibaba Cloud Coding Plan — Use an API key from Alibaba Cloud
API Key — Bring your own API key
Vertex AI — Use Google Cloud Vertex AI

For each authentication method, different Terms of Service and Privacy Notices may apply depending on the underlying service provider.

Authentication Method	Provider	Terms of Service	Privacy Notice
Qwen OAuth	Qwen AI	Qwen Terms of Service	Qwen Privacy Policy
Alibaba Cloud Coding Plan	Alibaba Cloud	See details below	See details below
API Key	Various Providers	Depends on your chosen API provider (OpenAI, Anthropic, etc.)	Depends on your chosen API provider
Vertex AI	Google Cloud	Google Cloud Terms	Google Cloud Privacy

1. If you are using Qwen OAuth Authentication

When you authenticate using your qwen.ai account, these Terms of Service and Privacy Notice documents apply:

Terms of Service: Your use is governed by the Qwen Terms of Service.
Privacy Notice: The collection and use of your data is described in the Qwen Privacy Policy.

For details about authentication setup, quotas, and supported features, see Authentication Setup.

2. If you are using Alibaba Cloud Coding Plan

When you authenticate using an API key from Alibaba Cloud, the applicable Terms of Service and Privacy Notice from Alibaba Cloud apply.

Alibaba Cloud Coding Plan is available in two regions:

阿里云百炼 (aliyun.com) — bailian.console.aliyun.com
Alibaba Cloud (alibabacloud.com) — bailian.console.alibabacloud.com

Important

When using Alibaba Cloud Coding Plan, you are subject to Alibaba Cloud's terms and privacy policies. Please review their documentation for specific details about data usage, retention, and privacy practices.

3. If you are using your own API Key

When you authenticate using API keys from other providers, the applicable Terms of Service and Privacy Notice depend on your chosen provider.

Important

When using your own API key, you are subject to the terms and privacy policies of your chosen API provider, not Qwen Code's terms. Please review your provider's documentation for specific details about data usage, retention, and privacy practices.

Qwen Code supports various OpenAI-compatible providers. Please refer to your specific provider's terms of service and privacy policy for detailed information.

4. If you are using Vertex AI

When you authenticate with Google Cloud Vertex AI, the applicable Terms of Service and Privacy Notice are Google Cloud's.

Important

When using Vertex AI, you are subject to Google Cloud's Terms of Service and Google Cloud Privacy Notice, not Qwen Code's terms. Please review Google Cloud's documentation for specific details about data usage, retention, and privacy practices.

Usage Statistics and Telemetry

Qwen Code may collect anonymous usage statistics and telemetry data to improve the user experience and product quality. This data collection is optional and can be controlled through configuration settings.

What Data is Collected

When enabled, Qwen Code may collect:

Anonymous usage statistics (commands run, performance metrics)
Error reports and crash data
Feature usage patterns

Data Collection by Authentication Method

Qwen OAuth: Usage statistics are governed by Qwen's privacy policy. You can opt-out through Qwen Code's configuration settings.
Alibaba Cloud Coding Plan: Usage statistics are governed by Alibaba Cloud's privacy policy. You can opt-out through Qwen Code's configuration settings.
API Key: No additional data is collected by Qwen Code beyond what your chosen API provider collects.
Vertex AI: Usage statistics are governed by Google Cloud's privacy policy. No additional data is collected by Qwen Code beyond what Google Cloud collects.

Frequently Asked Questions (FAQ)

1. Is my code, including prompts and answers, used to train AI models?

Whether your code, including prompts and answers, is used to train AI models depends on your authentication method and the specific AI service provider you use:

Qwen OAuth: Data usage is governed by Qwen's Privacy Policy. Please refer to their policy for specific details about data collection and model training practices.
Alibaba Cloud Coding Plan: Data usage is governed by Alibaba Cloud's privacy policy. Please refer to their policy for specific details about data collection and model training practices.
API Key: Data usage depends entirely on your chosen API provider. Each provider has their own data usage policies. Please review the privacy policy and terms of service of your specific provider.
Vertex AI: Data usage is governed by Google Cloud's Terms of Service and Privacy Notice. Please review Google Cloud's policies for specific details about data collection and model training practices.

Important: Qwen Code itself does not use your prompts, code, or responses for model training. Any data usage for training purposes would be governed by the policies of the AI service provider you authenticate with.

2. What are Usage Statistics and what does the opt-out control?

The Usage Statistics setting controls optional data collection by Qwen Code for improving the user experience and product quality.