@qwen-code/qwen-code 0.14.4 → 0.14.5-nightly.20260417.12b24e2d2

package/bundled/qc-helper/docs/features/memory.md

@@ -0,0 +1,166 @@
+# Memory
+
+Every Qwen Code session starts with a fresh context window. Two mechanisms carry knowledge across sessions so you don't have to re-explain yourself every time:
+
+- **QWEN.md** — instructions *you* write once and Qwen reads every session
+- **Auto-memory** — notes Qwen writes itself based on what it learns from you
+
+---
+
+## QWEN.md: your instructions to Qwen
+
+QWEN.md is a plain text file where you write things Qwen should always know about your project or your preferences. Think of it as a permanent briefing that loads at the start of every conversation.
+
+### What to put in QWEN.md
+
+Add things you'd otherwise have to repeat every session:
+
+- Build and test commands (`npm run test`, `make build`)
+- Coding conventions your team follows ("all new files must have JSDoc comments")
+- Architectural decisions ("we use the repository pattern, never call the database directly from controllers")
+- Personal preferences ("always use pnpm, not npm")
+
+Don't include things Qwen can figure out by reading your code. QWEN.md works best when it's short and specific — the longer it gets, the less reliably Qwen follows it.
+
+### Where to create QWEN.md
+
+| File | Who it applies to |
+|---|---|
+| `~/.qwen/QWEN.md` | You, across all your projects |
+| `QWEN.md` in the project root | Your whole team (commit it to source control) |
+
+You can have both. Qwen loads all QWEN.md files it finds when you start a session — your personal one plus any in the project.
+
+If your repository already has an `AGENTS.md` file for other AI tools, Qwen reads that too. No need to duplicate instructions.
+
+### Generate one automatically with `/init`
+
+Run `/init` and Qwen will analyze your codebase to create a starter QWEN.md with build commands, test instructions, and conventions it finds. If one already exists, it suggests additions instead of overwriting.
+
+### Reference other files
+
+You can point QWEN.md at other files so Qwen reads them too:
+
+```markdown
+See @README.md for project overview.
+
+# Conventions
+- Git workflow: @docs/git-workflow.md
+```
+
+Use `@path/to/file` anywhere in QWEN.md. Relative paths resolve from the QWEN.md file itself.
+
+---
+
+## Auto-memory: what Qwen learns about you
+
+Auto-memory runs in the background. After each of your conversations, Qwen quietly saves useful things it learned — your preferences, feedback you gave, project context — so it can use them in future sessions without you repeating yourself.
+
+This is different from QWEN.md: you don't write it, Qwen does.
+
+### What Qwen saves
+
+Qwen looks for four kinds of things worth remembering:
+
+| What | Examples |
+|---|---|
+| **About you** | Your role, background, how you like to work |
+| **Your feedback** | Corrections you made, approaches you confirmed |
+| **Project context** | Ongoing work, decisions, goals not obvious from the code |
+| **External references** | Dashboards, ticket trackers, docs links you mentioned |
+
+Qwen doesn't save everything — only things that would actually be useful next time.
+
+### Where it's stored
+
+Auto-memory files live at `~/.qwen/projects/<project>/memory/`. All branches and worktrees of the same repository share the same memory folder, so what Qwen learns in one branch is available in others.
+
+Everything saved is plain markdown — you can open, edit, or delete any file at any time.
+
+### Periodic cleanup
+
+Qwen periodically goes through its saved memories to remove duplicates and clean up outdated entries. This runs automatically in the background once a day after enough sessions have accumulated. You can trigger it manually with `/dream` if you want it to run now.
+
+While cleanup is running, **✦ dreaming** appears in the corner of the screen. Your session continues normally.
+
+### Turning it on or off
+
+Auto-memory is on by default. To toggle it, open `/memory` and use the switches at the top. You can turn off just the automatic saving, just the periodic cleanup, or both.
+
+You can also set them in `~/.qwen/settings.json` (applies to all projects) or `.qwen/settings.json` (this project only):
+
+```json
+{
+  "memory": {
+    "enableManagedAutoMemory": true,
+    "enableManagedAutoDream": true
+  }
+}
+```
+
+---
+
+## Commands
+
+### `/memory`
+
+Opens the Memory panel. From here you can:
+
+- Turn auto-memory saving on or off
+- Turn periodic cleanup (dream) on or off
+- Open your personal QWEN.md (`~/.qwen/QWEN.md`)
+- Open the project QWEN.md
+- Browse the auto-memory folder
+
+### `/init`
+
+Generates a starter QWEN.md for your project. Qwen reads your codebase and fills in build commands, test instructions, and conventions it discovers.
+
+### `/remember <text>`
+
+Immediately saves something to auto-memory without waiting for Qwen to pick it up automatically:
+
+```
+/remember always use snake_case for Python variable names
+/remember the staging environment is at staging.example.com
+```
+
+### `/forget <text>`
+
+Removes auto-memory entries that match your description:
+
+```
+/forget old workaround for the login bug
+```
+
+### `/dream`
+
+Runs the memory cleanup now instead of waiting for the automatic schedule:
+
+```
+/dream
+```
+
+---
+
+## Troubleshooting
+
+### Qwen isn't following my QWEN.md
+
+Open `/memory` to see which files are loaded. If your file isn't listed, Qwen can't see it — make sure it's in the project root or `~/.qwen/`.
+
+Instructions work better when they're specific:
+- ✓ `Use 2-space indentation for TypeScript files`
+- ✗ `Format code nicely`
+
+If you have multiple QWEN.md files with conflicting instructions, Qwen may behave inconsistently. Review them and remove any contradictions.
+
+### I want to see what Qwen has saved
+
+Run `/memory` and select **Open auto-memory folder**. All saved memories are readable markdown files you can browse, edit, or delete.
+
+### Qwen keeps forgetting things
+
+If auto-memory is on but Qwen doesn't seem to remember things across sessions, try running `/dream` to force a cleanup pass. Also check `/memory` to confirm both toggles are enabled.
+
+For things you always want Qwen to remember, add them to QWEN.md instead — auto-memory is best-effort, QWEN.md is guaranteed.

package/bundled/qc-helper/docs/features/sub-agents.md

@@ -12,10 +12,46 @@ Subagents are independent AI assistants that:
 - **Work autonomously** - Once given a task, they work independently until completion or failure
 - **Provide detailed feedback** - You can see their progress, tool usage, and execution statistics in real-time
 
+## Fork Subagent (Implicit Fork)
+
+In addition to named subagents, Qwen Code supports **implicit forking** — when the AI omits the `subagent_type` parameter, it triggers a fork that inherits the parent's full conversation context.
+
+### How Fork Differs from Named Subagents
+
+|               | Named Subagent                    | Fork Subagent                                         |
+| ------------- | --------------------------------- | ----------------------------------------------------- |
+| Context       | Starts fresh, no parent history   | Inherits parent's full conversation history           |
+| System prompt | Uses its own configured prompt    | Uses parent's exact system prompt (for cache sharing) |
+| Execution     | Blocks the parent until done      | Runs in background, parent continues immediately      |
+| Use case      | Specialized tasks (testing, docs) | Parallel tasks that need the current context          |
+
+### When Fork is Used
+
+The AI automatically uses fork when it needs to:
+
+- Run multiple research tasks in parallel (e.g., "investigate module A, B, and C")
+- Perform background work while continuing the main conversation
+- Delegate tasks that require understanding of the current conversation context
+
+### Prompt Cache Sharing
+
+All forks share the parent's exact API request prefix (system prompt, tools, conversation history), enabling DashScope prompt cache hits. When 3 forks run in parallel, the shared prefix is cached once and reused — saving 80%+ token costs compared to independent subagents.
+
+### Recursive Fork Prevention
+
+Fork children cannot create further forks. This is enforced at runtime — if a fork attempts to spawn another fork, it receives an error instructing it to execute tasks directly.
+
+### Current Limitations
+
+- **No result feedback**: Fork results are reflected in the UI progress display but are not automatically fed back into the main conversation. The parent AI sees a placeholder message and cannot act on the fork's output.
+- **No worktree isolation**: Forks share the parent's working directory. Concurrent file modifications from multiple forks may conflict.
+
 ## Key Benefits
 
 - **Task Specialization**: Create agents optimized for specific workflows (testing, documentation, refactoring, etc.)
 - **Context Isolation**: Keep specialized work separate from your main conversation
+- **Context Inheritance**: Fork subagents inherit the full conversation for context-heavy parallel tasks
+- **Prompt Cache Sharing**: Fork subagents share the parent's cache prefix, reducing token costs
 - **Reusability**: Save and reuse agent configurations across projects and sessions
 - **Controlled Access**: Limit which tools each agent can use for security and focus
 - **Progress Visibility**: Monitor agent execution with real-time progress updates
@@ -23,7 +59,7 @@ Subagents are independent AI assistants that:
 ## How Subagents Work
 
 1. **Configuration**: You create Subagents configurations that define their behavior, tools, and system prompts
-2. **Delegation**: The main AI can automatically delegate tasks to appropriate Subagents
+2. **Delegation**: The main AI can automatically delegate tasks to appropriate Subagents — or implicitly fork when no specific subagent type is needed
 3. **Execution**: Subagents work independently, using their configured tools to complete tasks
 4. **Results**: They return results and execution summaries back to the main conversation
 

package/bundled/qc-helper/docs/support/tos-privacy.md

@@ -6,7 +6,7 @@ Qwen Code is an open-source AI coding assistant tool maintained by the Qwen Code
 
 Qwen Code supports three authentication methods to access AI models. Your authentication method determines which terms of service and privacy policies apply to your usage:
 
-1. **Qwen OAuth** — Log in with your qwen.ai account (free daily quota, ending 2026-04-15)
+1. **Qwen OAuth** — Log in with your qwen.ai account (free tier discontinued 2026-04-15)
 2. **Alibaba Cloud Coding Plan** — Use an API key from Alibaba Cloud
 3. **API Key** — Bring your own API key