@qwen-code/qwen-code 0.17.0-preview.0 → 0.17.1

package/bundled/qc-helper/docs/features/approval-mode.md

@@ -4,18 +4,22 @@ Qwen Code offers five distinct permission modes that allow you to flexibly contr
 
 ## Permission Modes Comparison
 
-| Mode           | File Editing                | Shell Commands              | Best For                                                                                               | Risk Level |
-| -------------- | --------------------------- | --------------------------- | ------------------------------------------------------------------------------------------------------ | ---------- |
-| **Plan**​      | ❌ Read-only analysis only  | ❌ Not executed             | • Code exploration <br>• Planning complex changes <br>• Safe code review                               | Lowest     |
-| **Default**​   | ✅ Manual approval required | ✅ Manual approval required | • New/unfamiliar codebases <br>• Critical systems <br>• Team collaboration <br>• Learning and teaching | Low        |
-| **Auto-Edit**​ | ✅ Auto-approved            | ❌ Manual approval required | • Daily development tasks <br>• Refactoring and code improvements <br>• Safe automation                | Medium     |
-| **Auto**​      | ✅ Classifier-evaluated     | ✅ Classifier-evaluated     | • Long autonomous sessions <br>• When Auto-Edit is too cautious but YOLO is too risky                  | Medium     |
-| **YOLO**​      | ✅ Auto-approved            | ✅ Auto-approved            | • Trusted personal projects <br>• Automated scripts/CI/CD <br>• Batch processing tasks                 | Highest    |
+| Mode                 | File Editing                | Shell Commands              | Best For                                                                                               | Risk Level |
+| -------------------- | --------------------------- | --------------------------- | ------------------------------------------------------------------------------------------------------ | ---------- |
+| **Plan**​            | ❌ Read-only analysis only  | ❌ Not executed             | • Code exploration <br>• Planning complex changes <br>• Safe code review                               | Lowest     |
+| **Ask Permissions**​ | ✅ Manual approval required | ✅ Manual approval required | • New/unfamiliar codebases <br>• Critical systems <br>• Team collaboration <br>• Learning and teaching | Low        |
+| **Auto-Edit**​       | ✅ Auto-approved            | ❌ Manual approval required | • Daily development tasks <br>• Refactoring and code improvements <br>• Safe automation                | Medium     |
+| **Auto**​            | ✅ Classifier-evaluated     | ✅ Classifier-evaluated     | • Long autonomous sessions <br>• When Auto-Edit is too cautious but YOLO is too risky                  | Medium     |
+| **YOLO**​            | ✅ Auto-approved            | ✅ Auto-approved            | • Trusted personal projects <br>• Automated scripts/CI/CD <br>• Batch processing tasks                 | Highest    |
+
+> [!NOTE]
+>
+> The mode previously named **Default** has been renamed to **Ask Permissions** to better describe its behavior. The underlying configuration value (`tools.approvalMode: "default"`) and the `/approval-mode default` command are unchanged for backward compatibility.
 
 ### Quick Reference Guide
 
 - **Start in Plan Mode**: Great for understanding before making changes
-- **Work in Default Mode**: The balanced choice for most development work
+- **Work in Ask Permissions Mode**: The balanced choice for most development work
 - **Switch to Auto-Edit**: When you're making lots of safe code changes
 - **Try Auto Mode**: When you want fewer interruptions but still want safety on shell commands and network calls — an LLM classifier evaluates each call
 - **Use YOLO sparingly**: Only for trusted automation in controlled environments
@@ -96,11 +100,11 @@ How should we handle database migration?
 }
 ```
 
-## 2. Use Default Mode for Controlled Interaction
+## 2. Use Ask Permissions Mode for Controlled Interaction
 
-Default Mode is the standard way to work with Qwen Code. In this mode, you maintain full control over all potentially risky operations - Qwen Code will ask for your approval before making any file changes or executing shell commands.
+Ask Permissions Mode is the standard way to work with Qwen Code. In this mode, you maintain full control over all potentially risky operations - Qwen Code will ask for your approval before making any file changes or executing shell commands.
 
-### When to use Default Mode
+### When to use Ask Permissions Mode
 
 - **New to a codebase**: When you're exploring an unfamiliar project and want to be extra cautious
 - **Critical systems**: When working on production code, infrastructure, or sensitive data
@@ -108,23 +112,23 @@ Default Mode is the standard way to work with Qwen Code. In this mode, you maint
 - **Team collaboration**: When multiple people are working on the same codebase
 - **Complex operations**: When the changes involve multiple files or complex logic
 
-### How to use Default Mode
+### How to use Ask Permissions Mode
 
-**Turn on Default Mode during a session**
+**Turn on Ask Permissions Mode during a session**
 
-You can switch into Default Mode during a session using **Shift+Tab**​ (or **Tab** on Windows) to cycle through permission modes. If you're in any other mode, pressing **Shift+Tab** (or **Tab** on Windows) will eventually cycle back to Default Mode, indicated by the absence of any mode indicator at the bottom of the terminal.
+You can switch into Ask Permissions Mode during a session using **Shift+Tab**​ (or **Tab** on Windows) to cycle through permission modes. If you're in any other mode, pressing **Shift+Tab** (or **Tab** on Windows) will eventually cycle back to Ask Permissions Mode, indicated by the absence of any mode indicator at the bottom of the terminal.
 
-**Start a new session in Default Mode**
+**Start a new session in Ask Permissions Mode**
 
-Default Mode is the initial mode when you start Qwen Code. If you've changed modes and want to return to Default Mode, use:
+Ask Permissions Mode is the initial mode when you start Qwen Code. If you've changed modes and want to return to Ask Permissions Mode, use:
 
 ```
 /approval-mode default
 ```
 
-**Run "headless" queries in Default Mode**
+**Run "headless" queries in Ask Permissions Mode**
 
-When running headless commands, Default Mode is the default behavior. You can explicitly specify it with:
+When running headless commands, Ask Permissions Mode is the default behavior. You can explicitly specify it with:
 
 ```
 qwen --prompt "Analyze this code for potential bugs"
@@ -148,7 +152,7 @@ Qwen Code will analyze your codebase and propose a plan. It will then ask for ap
 
 You can review each proposed change and approve or reject it individually.
 
-### Configure Default Mode as default
+### Configure Ask Permissions Mode as default
 
 ```bash
 // .qwen/settings.json
@@ -200,7 +204,7 @@ configuration, troubleshooting, FAQ).
 
 ### When to use Auto Mode
 
-- **Long autonomous sessions**: When Default Mode interrupts too often but
+- **Long autonomous sessions**: When Ask Permissions Mode interrupts too often but
   YOLO is too risky.
 - **Trusted projects**: Internal codebases where the agent should keep
   moving but you still want a guardrail on destructive shell commands and
@@ -277,7 +281,7 @@ Refactor the auth module to use OAuth2. Run the full test suite afterwards.
 Qwen Code makes the file edits (in-workspace edits skip the classifier),
 runs `npm test` (classifier judges safe), and surfaces a block if it ever
 tries something risky like `rm -rf /Users/me/.aws`. You can review the
-reason inline and decide whether to switch to Default Mode for that step.
+reason inline and decide whether to switch to Ask Permissions Mode for that step.
 
 ### Configure Auto Mode as default
 
@@ -363,7 +367,7 @@ qwen --prompt "Run the test suite, fix all failing tests, then commit changes"
 During a Qwen Code session, use **Shift+Tab**​ (or **Tab** on Windows) to quickly cycle through the four modes:
 
 ```
-Default Mode → Auto-Edit Mode → YOLO Mode → Plan Mode → Default Mode
+Ask Permissions Mode → Auto-Edit Mode → YOLO Mode → Plan Mode → Ask Permissions Mode
 ```
 
 ### Persistent Configuration

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

@@ -31,16 +31,18 @@ These commands help you save, restore, and summarize work progress.
 
 Commands for adjusting interface appearance and work environment.
 
-| Command      | Description                                                                                                                                                                       | Usage Examples                |
-| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------- |
-| `/clear`     | Clear terminal screen content                                                                                                                                                     | `/clear` (shortcut: `Ctrl+L`) |
-| `/context`   | Show context window usage breakdown                                                                                                                                               | `/context`                    |
-| → `detail`   | Show per-item context usage breakdown                                                                                                                                             | `/context detail`             |
-| `/diff`      | Open an interactive diff viewer showing uncommitted changes and per-turn diffs. Use ←/→ to switch between current git diff and individual conversation turns, ↑/↓ to browse files | `/diff`                       |
-| `/theme`     | Change Qwen Code visual theme                                                                                                                                                     | `/theme`                      |
-| `/vim`       | Turn input area Vim editing mode on/off                                                                                                                                           | `/vim`                        |
-| `/directory` | Manage multi-directory support workspace                                                                                                                                          | `/dir add ./src,./tests`      |
-| `/editor`    | Open dialog to select supported editor                                                                                                                                            | `/editor`                     |
+| Command              | Description                                                                                                                                                                       | Usage Examples                          |
+| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- |
+| `/clear`             | Clear terminal screen content                                                                                                                                                     | `/clear` (shortcut: `Ctrl+L`)           |
+| `/context`           | Show context window usage breakdown                                                                                                                                               | `/context`                              |
+| → `detail`           | Show per-item context usage breakdown                                                                                                                                             | `/context detail`                       |
+| `/diff`              | Open an interactive diff viewer showing uncommitted changes and per-turn diffs. Use ←/→ to switch between current git diff and individual conversation turns, ↑/↓ to browse files | `/diff`                                 |
+| `/theme`             | Change Qwen Code visual theme                                                                                                                                                     | `/theme`                                |
+| `/vim`               | Turn input area Vim editing mode on/off                                                                                                                                           | `/vim`                                  |
+| `/directory`         | Manage multi-directory support workspace                                                                                                                                          | `/dir add ./src,./tests`                |
+| `/editor`            | Open dialog to select supported editor                                                                                                                                            | `/editor`                               |
+| `/statusline`        | Open interactive [status line](./status-line.md) preset dialog                                                                                                                    | `/statusline`                           |
+| `/statusline <text>` | Generate a command-mode [status line](./status-line.md) via agent                                                                                                                 | `/statusline show model and git branch` |
 
 ### 1.3 Language Settings
 

package/bundled/qc-helper/docs/features/status-line.md

@@ -1,8 +1,11 @@
 # Status Line
 
-> Display custom information in the footer using a shell command.
+> Display custom information in the footer.
 
-The status line lets you run a shell command whose output is displayed in the footer's left section. The command receives structured JSON context via stdin, so it can show session-aware information like the current model, token usage, git branch, or anything else you can script.
+The status line shows session-aware information — model name, token usage, git branch, and more — in the footer's left section. There are two configuration modes:
+
+- **Preset mode** — pick from built-in data items via an interactive dialog or JSON config. No scripting required.
+- **Command mode** — run a shell command that receives structured JSON context via stdin. Full flexibility for custom formatting.
 
 ```
 Single-line status (default approval mode — 1 row):
@@ -26,26 +29,130 @@ Multi-line status + non-default mode (3 rows max):
 
 When configured, the status line replaces the default "? for shortcuts" hint. High-priority messages (Ctrl+C/D exit prompts, Esc, vim INSERT mode) temporarily override the status line. The status line text is truncated to fit within the available width.
 
-## Prerequisites
-
-- [`jq`](https://jqlang.github.io/jq/) is recommended for parsing the JSON input (install via `brew install jq`, `apt install jq`, etc.)
-- Simple commands that don't need JSON data (e.g. `git branch --show-current`) work without `jq`
-
 ## Quick setup
 
-The easiest way to configure a status line is the `/statusline` command. It launches a setup agent that reads your shell PS1 configuration and generates a matching status line:
+The easiest way to configure a status line is the `/statusline` command. It opens an interactive dialog where you can select preset items, toggle theme colors, and see a live preview:
 
 ```
 /statusline
 ```
 
-You can also give it specific instructions:
+This opens the preset mode configurator. Use arrow keys to navigate, space to toggle items, and enter to confirm. Your selection is saved to settings automatically.
+
+You can also give `/statusline` specific instructions to have it generate a command-mode configuration:
 
 ```
 /statusline show model name and context usage percentage
 ```
 
-## Manual configuration
+---
+
+## Preset mode
+
+Preset mode provides a set of built-in data items that you can pick and combine — no shell commands, no `jq`, no scripting. Items are rendered as `item1 | item2 | item3` in a single line.
+
+### Configuration
+
+Add a `statusLine` object under the `ui` key in `~/.qwen/settings.json`:
+
+```json
+{
+  "ui": {
+    "statusLine": {
+      "type": "preset",
+      "items": [
+        "model-with-reasoning",
+        "git-branch",
+        "context-remaining",
+        "current-dir",
+        "context-used"
+      ],
+      "useThemeColors": true
+    }
+  }
+}
+```
+
+| Field                  | Type       | Required | Description                                                                                                |
+| ---------------------- | ---------- | -------- | ---------------------------------------------------------------------------------------------------------- |
+| `type`                 | `"preset"` | Yes      | Must be `"preset"`                                                                                         |
+| `items`                | string[]   | Yes      | Ordered list of preset item IDs to display (see table below). Items are joined with `\|` as the separator. |
+| `useThemeColors`       | boolean    | No       | Apply the active `/theme` color to the status line text. Defaults to `true`.                               |
+| `hideContextIndicator` | boolean    | No       | Hide the built-in context usage indicator in the footer right section. Defaults to `false`.                |
+
+### Available preset items
+
+| Item ID                | Default | Description                                                        |
+| ---------------------- | ------- | ------------------------------------------------------------------ |
+| `model-with-reasoning` | Yes     | Current model name with reasoning level (e.g. `qwen-3-235b high`)  |
+| `model`                |         | Current model name without reasoning level                         |
+| `git-branch`           | Yes     | Current Git branch name (hidden when not in a git repo)            |
+| `context-remaining`    | Yes     | Percentage of context window remaining (e.g. `Context 65.7% left`) |
+| `total-input-tokens`   |         | Total input tokens used in session (e.g. `30.0k in`)               |
+| `total-output-tokens`  |         | Total output tokens used in session (e.g. `5.0k out`)              |
+| `current-dir`          | Yes     | Current working directory                                          |
+| `project-name`         |         | Project name (basename of working directory)                       |
+| `pull-request-number`  |         | Open PR number for the current branch (requires `gh` CLI)          |
+| `branch-changes`       |         | Session file change stats (e.g. `+120 -30`)                        |
+| `context-used`         | Yes     | Percentage of context window used (e.g. `Context 34.3% used`)      |
+| `run-state`            |         | Compact session state (`Ready`, `Working`, or `Confirm`)           |
+| `qwen-version`         |         | Qwen Code version (e.g. `v0.14.1`)                                 |
+| `context-window-size`  |         | Total context window size (e.g. `131.1k window`)                   |
+| `used-tokens`          |         | Current prompt token count (e.g. `45.0k used`)                     |
+| `session-id`           |         | Current session identifier                                         |
+
+Items marked **Default** are pre-selected when you first open the `/statusline` dialog.
+
+### Example output
+
+With the default items, the status line looks like:
+
+```
+qwen-3-235b high | main | Context 65.7% left | /home/user/project | Context 34.3% used
+```
+
+### Customizing via the dialog
+
+Running `/statusline` opens an interactive multi-select dialog:
+
+```
+┌ Configure Status Line ────────────────────────────────────────┐
+│ Select which items to display in the status line.             │
+│                                                               │
+│ Type to search                                                │
+│ >                                                             │
+│                                                               │
+│ [x] Use theme colors        Apply colors from the active /theme│
+│ ───────────────────────                                       │
+│ [x] model-with-reasoning    Current model name with reasoning │
+│ [ ] model-only              Current model name without reason │
+│ [x] git-branch              Current Git branch when available │
+│ [x] context-remaining       Percentage of context remaining   │
+│ ...                                                           │
+│                                                               │
+│ Preview                                                       │
+│ qwen-3-235b high | main | Context 65.7% left                 │
+│                                                               │
+│ Use up/down to navigate, space to select, enter to confirm    │
+└───────────────────────────────────────────────────────────────┘
+```
+
+- Type to filter items by name or description
+- A live preview updates as you toggle items
+- Press enter to save the configuration
+
+---
+
+## Command mode
+
+Command mode runs a shell command whose stdout is displayed in the status line. The command receives structured JSON context via stdin for session-aware output.
+
+### Prerequisites
+
+- [`jq`](https://jqlang.github.io/jq/) is recommended for parsing the JSON input (install via `brew install jq`, `apt install jq`, etc.)
+- Simple commands that don't need JSON data (e.g. `git branch --show-current`) work without `jq`
+
+### Configuration
 
 Add a `statusLine` object under the `ui` key in `~/.qwen/settings.json`:
 
@@ -68,7 +175,7 @@ Add a `statusLine` object under the `ui` key in `~/.qwen/settings.json`:
 | `respectUserColors`    | boolean     | No       | Preserve ANSI color codes in command output instead of applying dimmed footer styling. Defaults to `false`.                       |
 | `hideContextIndicator` | boolean     | No       | Hide the built-in context usage indicator in the footer right section. Defaults to `false`.                                       |
 
-## JSON input
+### JSON input
 
 The command receives a JSON object via stdin with the following fields:
 
@@ -93,6 +200,13 @@ The command receives a JSON object via stdin with the following fields:
   "git": {
     "branch": "main"
   },
+  "worktree": {
+    "name": "fix-auth",
+    "path": "/home/user/project/.qwen/worktrees/fix-auth",
+    "branch": "fix-auth",
+    "original_cwd": "/home/user/project",
+    "original_branch": "main"
+  },
   "metrics": {
     "models": {
       "qwen-3-235b": {
@@ -135,6 +249,12 @@ The command receives a JSON object via stdin with the following fields:
 | `workspace.current_dir`               | string           | Current working directory                                                          |
 | `git`                                 | object \| absent | Present only inside a git repository.                                              |
 | `git.branch`                          | string           | Current branch name                                                                |
+| `worktree`                            | object \| absent | Present only when inside an active worktree (created by `enter_worktree`).         |
+| `worktree.name`                       | string           | Worktree slug name                                                                 |
+| `worktree.path`                       | string           | Absolute path to the worktree directory                                            |
+| `worktree.branch`                     | string           | Branch checked out in the worktree                                                 |
+| `worktree.original_cwd`               | string           | Working directory before entering the worktree                                     |
+| `worktree.original_branch`            | string           | Branch that was active before entering the worktree                                |
 | `metrics.models.<id>.api`             | object           | Per-model API stats: `total_requests`, `total_errors`, `total_latency_ms`          |
 | `metrics.models.<id>.tokens`          | object           | Per-model token usage: `prompt`, `completion`, `total`, `cached`, `thoughts`       |
 | `metrics.files`                       | object           | File change stats: `total_lines_added`, `total_lines_removed`                      |
@@ -142,9 +262,9 @@ The command receives a JSON object via stdin with the following fields:
 
 > **Important:** stdin can only be read once. Always store it in a variable first: `input=$(cat)`.
 
-## Examples
+### Examples
 
-### Model and token usage
+#### Model and token usage
 
 ```json
 {
@@ -159,7 +279,7 @@ The command receives a JSON object via stdin with the following fields:
 
 Output: `qwen-3-235b  ctx:34%`
 
-### Git branch + directory
+#### Git branch + directory
 
 ```json
 {
@@ -176,7 +296,7 @@ Output: `my-project (main)`
 
 > Note: The `git.branch` field is provided directly in the JSON input — no need to shell out to `git`.
 
-### File change stats
+#### File change stats
 
 ```json
 {
@@ -191,7 +311,7 @@ Output: `my-project (main)`
 
 Output: `+120/-30 lines`
 
-### Live clock and git branch
+#### Live clock and git branch
 
 Use `refreshInterval` when the statusline shows data that changes without an Agent event (e.g. the clock, uptime, or rate-limit counters):
 
@@ -209,7 +329,7 @@ Use `refreshInterval` when the statusline shows data that changes without an Age
 
 Output (refreshed every second): `14:32:07  (main)`
 
-### Script file for complex commands
+#### Script file for complex commands
 
 For longer commands, save a script file at `~/.qwen/statusline-command.sh`:
 
@@ -246,18 +366,32 @@ Then reference it in settings:
 
 ## Behavior
 
-- **Update triggers**: The status line updates when the model changes, a new message is sent (token count changes), vim mode is toggled, git branch changes, tool calls complete, or file changes occur. Updates are debounced (300ms). Set `refreshInterval` (seconds) to additionally re-run the command on a timer — useful for data that changes without an Agent event (clock, rate limits, build status).
-- **Timeout**: Commands that take longer than 5 seconds are killed. The status line clears on failure.
-- **Output**: Multi-line output is supported (up to 2 lines; extra lines are discarded). Each line is rendered as a separate row with dimmed colors in the footer's left section. Lines that exceed the available width are truncated.
+**Both modes:**
+
+- **Update triggers**: The status line updates when the model changes, a new message is sent (token count changes), vim mode is toggled, git branch changes, tool calls complete, or file changes occur. Updates are debounced (300ms).
+- **Output**: Up to 2 lines. Each line is rendered as a separate row in the footer's left section. Lines that exceed the available width are truncated.
 - **Hot reload**: Changes to `ui.statusLine` in settings take effect immediately — no restart required.
-- **Shell**: Commands run via `/bin/sh` on macOS/Linux. On Windows, `cmd.exe` is used by default — wrap POSIX commands with `bash -c "..."` or point to a bash script (e.g. `bash ~/.qwen/statusline-command.sh`).
 - **Removal**: Delete the `ui.statusLine` key from settings to disable. The "? for shortcuts" hint returns.
 
+**Command mode only:**
+
+- **Timeout**: Commands that take longer than 5 seconds are killed. The status line clears on failure.
+- **Refresh**: Set `refreshInterval` (seconds) to additionally re-run the command on a timer — useful for data that changes without an Agent event (clock, rate limits, build status).
+- **Shell**: Commands run via `/bin/sh` on macOS/Linux. On Windows, `cmd.exe` is used by default — wrap POSIX commands with `bash -c "..."` or point to a bash script (e.g. `bash ~/.qwen/statusline-command.sh`).
+
+**Preset mode only:**
+
+- **No external dependencies**: Preset items are computed internally — no shell commands, no `jq`, no timeouts.
+- **Theme integration**: When `useThemeColors` is `true` (default), the status line text uses the active `/theme` color. When `false`, dimmed footer styling is applied.
+- **PR lookup**: The `pull-request-number` item runs `gh pr view` in the background (2s timeout). It only triggers when the branch changes, not on every update.
+
 ## Troubleshooting
 
-| Problem                 | Cause                  | Fix                                                                                                                                                                                                                                                                                                                                                                                                    |
-| ----------------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Status line not showing | Config at wrong path   | Must be under `ui.statusLine`, not root-level `statusLine`                                                                                                                                                                                                                                                                                                                                             |
-| Empty output            | Command fails silently | Test manually: `echo '{"session_id":"test","version":"0.14.1","model":{"display_name":"test"},"context_window":{"context_window_size":0,"used_percentage":0,"remaining_percentage":100,"current_usage":0,"total_input_tokens":0,"total_output_tokens":0},"workspace":{"current_dir":"/tmp"},"metrics":{"models":{},"files":{"total_lines_added":0,"total_lines_removed":0}}}' \| sh -c 'your_command'` |
-| Stale data              | No trigger fired       | Send a message or switch models to trigger an update — or set `refreshInterval` to re-run the command on a timer                                                                                                                                                                                                                                                                                       |
-| Command too slow        | Complex script         | Optimize the script or move heavy work to a background cache                                                                                                                                                                                                                                                                                                                                           |
+| Problem                     | Cause                          | Fix                                                                                                                                                                                                                                                                                                                                                                                                    |
+| --------------------------- | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Status line not showing     | Config at wrong path           | Must be under `ui.statusLine`, not root-level `statusLine`                                                                                                                                                                                                                                                                                                                                             |
+| Empty output (command mode) | Command fails silently         | Test manually: `echo '{"session_id":"test","version":"0.14.1","model":{"display_name":"test"},"context_window":{"context_window_size":0,"used_percentage":0,"remaining_percentage":100,"current_usage":0,"total_input_tokens":0,"total_output_tokens":0},"workspace":{"current_dir":"/tmp"},"metrics":{"models":{},"files":{"total_lines_added":0,"total_lines_removed":0}}}' \| sh -c 'your_command'` |
+| Stale data (command mode)   | No trigger fired               | Send a message or switch models to trigger an update — or set `refreshInterval` to re-run the command on a timer                                                                                                                                                                                                                                                                                       |
+| Command too slow            | Complex script                 | Optimize the script or move heavy work to a background cache                                                                                                                                                                                                                                                                                                                                           |
+| Preset items missing        | Conditional items have no data | `git-branch` is hidden outside git repos; `context-used` is hidden when usage is 0; `branch-changes` is hidden when no files changed. This is expected — items appear once their data is available                                                                                                                                                                                                     |
+| PR number not showing       | `gh` CLI not installed         | Install [GitHub CLI](https://cli.github.com/) and authenticate with `gh auth login`. The lookup runs with a 2s timeout                                                                                                                                                                                                                                                                                 |

package/chunks/{agent-Z7O3I6MY.js → agent-ZJHHICAC.js}

@@ -7,34 +7,34 @@ import {
   hasRebuiltToolRegistry,
   rebuildToolRegistryOnOverride,
   resolveSubagentApprovalMode
-} from "./chunk-7JHNICSJ.js";
+} from "./chunk-2KEXT6RB.js";
 import "./chunk-24YKA2DA.js";
 import "./chunk-O4PICXES.js";
 import "./chunk-TW522KN6.js";
-import "./chunk-TI4GXJKO.js";
+import "./chunk-7TQVELRB.js";
 import "./chunk-AKBFRR6J.js";
 import "./chunk-MLZQVCF3.js";
-import "./chunk-FEENTAB2.js";
+import "./chunk-6O244QKR.js";
 import "./chunk-EY6BDW7Y.js";
-import "./chunk-HAQCNXSG.js";
+import "./chunk-RQW7WUJR.js";
 import "./chunk-77WXWU44.js";
 import "./chunk-GVWPJCXU.js";
-import "./chunk-OXXOAIGT.js";
-import "./chunk-J5VCSWPA.js";
+import "./chunk-C5CUHYSM.js";
+import "./chunk-3PJXIDKI.js";
 import "./chunk-UWCTAVOD.js";
 import "./chunk-W57YDFU5.js";
 import "./chunk-OFEVLU4C.js";
 import "./chunk-NQ3E7YLD.js";
 import "./chunk-OJFMTECH.js";
-import "./chunk-UQRYJQBE.js";
+import "./chunk-SOGUPKP6.js";
 import "./chunk-6RQTH7UQ.js";
-import "./chunk-R2B65CAN.js";
+import "./chunk-JKUAX6UT.js";
 import "./chunk-G4K6P5KN.js";
 import "./chunk-OIL7KDWV.js";
 import "./chunk-HX3JRTWL.js";
-import "./chunk-U2K6HDUJ.js";
+import "./chunk-QVJ33ZBG.js";
 import "./chunk-TDZCEIK6.js";
-import "./chunk-HCSJIOLR.js";
+import "./chunk-BNESGOSJ.js";
 import "./chunk-SZOEIL6S.js";
 import "./chunk-5IFG2VC4.js";
 import "./chunk-ACBGEKB7.js";

package/chunks/{anthropicContentGenerator-UCGOKLGC.js → anthropicContentGenerator-M45RXZVS.js}

@@ -6,7 +6,7 @@ import {
 } from "./chunk-KQIKOTQJ.js";
 import {
   RequestTokenizer
-} from "./chunk-V7LMZR76.js";
+} from "./chunk-JBSYXHJF.js";
 import {
   Blob,
   File,
@@ -16,7 +16,7 @@ import {
 import {
   buildRuntimeFetchOptions,
   redactProxyError
-} from "./chunk-U2K6HDUJ.js";
+} from "./chunk-QVJ33ZBG.js";
 import {
   CAPPED_DEFAULT_MAX_TOKENS,
   DEFAULT_TIMEOUT,
@@ -29,7 +29,7 @@ import {
 import {
   FinishReason,
   GenerateContentResponse
-} from "./chunk-HCSJIOLR.js";
+} from "./chunk-BNESGOSJ.js";
 import "./chunk-SZOEIL6S.js";
 import "./chunk-5IFG2VC4.js";
 import {

package/chunks/{askUserQuestion-DC6OWQIL.js → askUserQuestion-TGRD7FNQ.js}

@@ -8,7 +8,7 @@ import {
 import {
   BaseDeclarativeTool,
   BaseToolInvocation
-} from "./chunk-R2B65CAN.js";
+} from "./chunk-JKUAX6UT.js";
 import {
   createDebugLogger
 } from "./chunk-ACBGEKB7.js";

package/chunks/{ca-NMZFEGAU.js → ca-6RSCDYUS.js}

@@ -21,6 +21,7 @@ var ca_default = {
   "@src/myFile.ts": "@src/myFile.ts",
   "Shell mode": "Mode shell",
   "YOLO mode": "Mode YOLO",
+  "Auto mode": "Mode auto",
   "plan mode": "mode de planificaci\xF3",
   "auto-accept edits": "acceptaci\xF3 autom\xE0tica de canvis",
   "Accepting edits": "Acceptant canvis",
@@ -359,7 +360,7 @@ var ca_default = {
   Text: "Text",
   JSON: "JSON",
   Plan: "Planificaci\xF3",
-  Default: "Per defecte",
+  "Ask permissions": "Demanar permisos",
   "Auto Edit": "Edici\xF3 autom\xE0tica",
   YOLO: "YOLO",
   "toggle vim mode on/off": "activar/desactivar el mode Vim",