@qwen-code/qwen-code 0.17.0 → 0.17.1-nightly.20260604.16dd99fa3

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`:
 
@@ -60,13 +167,15 @@ Add a `statusLine` object under the `ui` key in `~/.qwen/settings.json`:
 }
 ```
 
-| Field             | Type        | Required | Description                                                                                                                       |
-| ----------------- | ----------- | -------- | --------------------------------------------------------------------------------------------------------------------------------- |
-| `type`            | `"command"` | Yes      | Must be `"command"`                                                                                                               |
-| `command`         | string      | Yes      | Shell command to execute. Receives JSON via stdin, stdout is displayed (up to 2 lines).                                           |
-| `refreshInterval` | number      | No       | Re-run the command every N seconds (minimum 1). Useful for data that changes without an Agent state event (clock, quota, uptime). |
+| Field                  | Type        | Required | Description                                                                                                                       |
+| ---------------------- | ----------- | -------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `type`                 | `"command"` | Yes      | Must be `"command"`                                                                                                               |
+| `command`              | string      | Yes      | Shell command to execute. Receives JSON via stdin, stdout is displayed (up to 2 lines).                                           |
+| `refreshInterval`      | number      | No       | Re-run the command every N seconds (minimum 1). Useful for data that changes without an Agent state event (clock, quota, uptime). |
+| `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:
 
@@ -91,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": {
@@ -133,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`                      |
@@ -140,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
 {
@@ -157,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
 {
@@ -174,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
 {
@@ -189,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):
 
@@ -207,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`:
 
@@ -244,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/bundled/qc-helper/docs/reference/keyboard-shortcuts.md

@@ -67,6 +67,22 @@ This document lists the available keyboard shortcuts in Qwen Code.
 | `1-9`                         | Select an item by its number.                                                                                 |
 | (multi-digit)                 | For items with numbers greater than 9, press the digits in quick succession to select the corresponding item. |
 
+## History scrollback
+
+Active only when `ui.useTerminalBuffer` is enabled (Settings → UI → Virtualized History). In that mode conversation history is rendered inside an in-app viewport instead of the host terminal scrollback, so the keys below replace the terminal's native scroll.
+
+| Shortcut        | Description                                          |
+| --------------- | ---------------------------------------------------- |
+| `Shift+Up`      | Scroll history up one line.                          |
+| `Shift+Down`    | Scroll history down one line.                        |
+| `PgUp`          | Scroll history up one page (viewport height).        |
+| `PgDn`          | Scroll history down one page (viewport height).      |
+| `Ctrl+Home`     | Jump to the top of the conversation.                 |
+| `Ctrl+End`      | Jump to the bottom (and re-engage live auto-follow). |
+| **Mouse wheel** | Scroll history (3 lines per tick).                   |
+
+When `ui.useTerminalBuffer` is on, the terminal forwards mouse events to qwen-code so the wheel can drive the in-app viewport. As a side effect, **native click-and-drag text selection is consumed by the program** — hold `Shift` (or `Option` on macOS Terminal / iTerm) while dragging to bypass mouse capture and select text the usual way.
+
 ## IDE Integration
 
 | Shortcut | Description                       |

package/bundled/simplify/SKILL.md

@@ -0,0 +1,123 @@
+---
+name: simplify
+description: Review recent code changes for reuse, code quality, and efficiency, then directly apply straightforward cleanup improvements. Use when the user wants a post-implementation cleanup pass, pre-PR polish, or asks to simplify/refine recent changes. Invoke with `/simplify` or `/simplify <focus>`.
+allowedTools:
+  - agent
+  - run_shell_command
+  - grep_search
+  - read_file
+  - write_file
+  - edit
+  - glob
+---
+
+# Simplify Recent Changes
+
+You are running a structured cleanup workflow over recent code changes. Your goal is not just to comment on the code, but to safely improve it.
+
+## Step 1: Identify the review scope
+
+Determine which files and changes to review.
+
+1. First inspect the current git state.
+2. If there are staged changes, review against `HEAD` so both staged and unstaged tracked changes are included.
+3. Otherwise review the current uncommitted diff.
+4. If there is no git diff, fall back to `git ls-files --modified --others --exclude-standard` so the scope respects `.gitignore` (this keeps build output, `node_modules`, and other ignored paths out of the cleanup).
+5. If that is still empty, fall back to files edited in this conversation.
+6. If you still cannot identify a meaningful scope, stop and tell the user there are no recent changes to simplify.
+
+Preferred commands:
+
+- `git diff --name-only`
+- `git diff --staged --name-only`
+- `git diff HEAD --name-only`
+- `git diff`
+- `git diff HEAD`
+- `git status --short`
+
+Use `git diff HEAD` whenever staged changes exist. Otherwise use `git diff`.
+
+## Step 2: Launch three review passes in parallel
+
+Use the `agent` tool and launch all review passes in a single response so they run concurrently. Each pass must receive the same review scope and diff command. These passes are read-only: each one inspects and reports findings only and must not modify files — all edits happen later in Step 4.
+
+Keep each review prompt short and focused. Do not paste the full diff into the prompt. Tell each pass to read the diff itself and inspect only files relevant to its findings.
+
+### Pass 1: Code Reuse Review
+
+Look for opportunities to reduce duplication and reuse existing code:
+
+- existing utilities or helpers that should be reused
+- duplicated logic introduced in new code
+- inline logic that should delegate to an existing abstraction
+- ad-hoc helpers for string, path, env, parsing, or type checks when a project utility already exists
+
+### Pass 2: Code Quality Review
+
+Look for maintainability issues:
+
+- copy-paste variants that should be unified
+- parameter sprawl or awkward APIs
+- redundant state or indirection
+- abstraction leaks
+- stringly-typed code that should be modeled more clearly
+- unnecessary nesting
+- unnecessary comments that explain what instead of why
+- naming or structure that does not match surrounding code
+
+### Pass 3: Efficiency Review
+
+Look for wasteful work and unnecessary overhead:
+
+- repeated work that can be memoized, cached, or removed
+- serial work that can be parallelized safely
+- unnecessary scans, allocations, reads, or traversals
+- hot-path blocking work
+- redundant no-op updates
+- overly broad operations when a narrower one would work
+- existence-check patterns that introduce TOCTOU style waste or risk
+
+## Step 3: Aggregate findings
+
+Wait for all three passes to finish, then merge overlapping findings.
+
+Prioritize fixes that are:
+
+- low risk
+- local in scope
+- clearly aligned with existing project patterns
+- easy to validate with tests or targeted commands
+
+Do not force a cleanup if it would require speculative architectural changes.
+
+## Step 4: Apply straightforward improvements
+
+Directly implement safe cleanup improvements.
+
+Examples of good automatic fixes:
+
+- replace duplicated logic with an existing helper
+- remove redundant code, but only after a repository-wide search confirms it has no remaining callers
+- simplify conditionals or control flow
+- tighten loops or repeated work
+- reduce unnecessary state or wrapper code
+- remove low-value comments
+- align code with nearby conventions
+
+Skip items that are uncertain, risky, or too invasive. Do not spend time debating rejected findings; simply move on.
+
+## Step 5: Verify the cleanup
+
+After making changes:
+
+1. Run focused tests for the changed area when they exist.
+2. Run the relevant project quality checks you can identify for the touched code.
+3. If there are no applicable tests, at least run a targeted build, typecheck, or lint command that covers the edited files.
+
+Prefer targeted verification over whole-repo commands unless the project only exposes repo-wide checks.
+
+## Additional focus
+
+If the user supplied extra instructions after `/simplify`, treat them as additional review focus and prioritize them alongside the default dimensions.
+
+The raw user invocation appears below when present. Use it to extract any extra focus such as performance, duplication, rendering, API clarity, testability, or naming consistency.

package/chunks/{agent-KVXFGIOU.js → agent-GNHB6UIW.js}

@@ -7,33 +7,34 @@ import {
   hasRebuiltToolRegistry,
   rebuildToolRegistryOnOverride,
   resolveSubagentApprovalMode
-} from "./chunk-7EHPK6TK.js";
+} from "./chunk-JR346RJ5.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-EMVEDSVZ.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-MEN6IEKX.js";
-import "./chunk-J5VCSWPA.js";
+import "./chunk-YVGIQ2CS.js";
+import "./chunk-3PJXIDKI.js";
 import "./chunk-UWCTAVOD.js";
 import "./chunk-W57YDFU5.js";
 import "./chunk-OFEVLU4C.js";
 import "./chunk-NQ3E7YLD.js";
-import "./chunk-ODPVJ6JJ.js";
-import "./chunk-UQRYJQBE.js";
+import "./chunk-OJFMTECH.js";
+import "./chunk-SOGUPKP6.js";
 import "./chunk-6RQTH7UQ.js";
-import "./chunk-R2B65CAN.js";
-import "./chunk-7YJIR2FX.js";
+import "./chunk-JKUAX6UT.js";
+import "./chunk-G4K6P5KN.js";
 import "./chunk-OIL7KDWV.js";
-import "./chunk-U2K6HDUJ.js";
-import "./chunk-6NUSWV4M.js";
-import "./chunk-HCSJIOLR.js";
+import "./chunk-HX3JRTWL.js";
+import "./chunk-QVJ33ZBG.js";
+import "./chunk-TDZCEIK6.js";
+import "./chunk-BNESGOSJ.js";
 import "./chunk-SZOEIL6S.js";
 import "./chunk-5IFG2VC4.js";
 import "./chunk-ACBGEKB7.js";

package/chunks/{anthropicContentGenerator-L4HWAOIV.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,
@@ -25,11 +25,11 @@ import {
   runtimeDiagnostics,
   safeJsonParse,
   tokenLimit
-} from "./chunk-6NUSWV4M.js";
+} from "./chunk-TDZCEIK6.js";
 import {
   FinishReason,
   GenerateContentResponse
-} from "./chunk-HCSJIOLR.js";
+} from "./chunk-BNESGOSJ.js";
 import "./chunk-SZOEIL6S.js";
 import "./chunk-5IFG2VC4.js";
 import {
@@ -4842,7 +4842,12 @@ var AnthropicContentGenerator = class {
     } catch (error) {
       throw redactProxyError(error);
     }
-    return this.processStream(this.redactStreamErrors(stream));
+    return this.processStreamWithEmptyFallback(
+      this.redactStreamErrors(stream),
+      anthropicRequest,
+      request.config?.abortSignal,
+      headers
+    );
   }
   async countTokens(request) {
     try {
@@ -5320,6 +5325,44 @@ var AnthropicContentGenerator = class {
       }
     }
   }
+  // Some Anthropic-compatible gateways close the SSE stream with HTTP 200
+  // but emit no assistant content or stop reason (e.g. billing / quota
+  // limits hit mid-proxy). When that happens we probe once with the same
+  // request in non-streaming mode so the real provider error surfaces
+  // instead of the generic "stream ended without a finish reason".
+  async *processStreamWithEmptyFallback(stream, fallbackRequest, abortSignal, headers) {
+    let hasAssistantPayload = false;
+    let hasFinishReason = false;
+    for await (const chunk of this.processStream(stream)) {
+      const candidates = chunk.candidates ?? [];
+      hasFinishReason ||= candidates.some(
+        (candidate) => candidate.finishReason !== void 0
+      );
+      hasAssistantPayload ||= candidates.some(
+        (candidate) => candidate.content?.parts?.some(
+          (part) => part.text || part.thought || part.thoughtSignature || part.functionCall
+        )
+      );
+      yield chunk;
+    }
+    if (hasAssistantPayload || hasFinishReason) {
+      return;
+    }
+    debugLogger.warn(
+      "Anthropic stream ended without assistant payload or finish reason; probing once with a non-streaming request to surface provider errors."
+    );
+    let response;
+    try {
+      runtimeDiagnostics.recordAnthropicWireRequest(fallbackRequest);
+      response = await this.client.messages.create(fallbackRequest, {
+        signal: abortSignal,
+        ...headers ? { headers } : {}
+      });
+      yield this.converter.convertAnthropicResponseToGemini(response);
+    } catch (error) {
+      throw redactProxyError(error);
+    }
+  }
   buildGeminiChunk(part, responseId, model, finishReason, usageMetadata) {
     const response = new GenerateContentResponse();
     response.responseId = responseId;

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",