@mmmbuto/qwen-code-termux 0.13.1-termux → 0.14.1-termux

package/README.md

@@ -7,189 +7,124 @@
 
 **An open-source AI agent that lives in your terminal — Termux Edition (Android).**
 
-<a href="https://qwenlm.github.io/qwen-code-docs/zh/users/overview">中文</a> |
-<a href="https://qwenlm.github.io/qwen-code-docs/de/users/overview">Deutsch</a> |
-<a href="https://qwenlm.github.io/qwen-code-docs/fr/users/overview">français</a> |
-<a href="https://qwenlm.github.io/qwen-code-docs/ja/users/overview">日本語</a> |
-<a href="https://qwenlm.github.io/qwen-code-docs/ru/users/overview">Русский</a> |
-<a href="https://qwenlm.github.io/qwen-code-docs/pt-BR/users/overview">Português (Brasil)</a>
-
 </div>
 
-> 🎉 **News (2026-03-27)**: Termux Edition v0.13.1 is here! TTS notifications,
-> full upstream v0.13.1 sync, and a streamlined install experience on Android.
+> News (2026-04-07): `v0.14.1-termux` is rebuilt from upstream `v0.14.1` on a clean history line for the Termux fork.
+
+Qwen Code Termux is a clean fork of [QwenLM/qwen-code](https://github.com/QwenLM/qwen-code), rebuilt release-by-release from upstream and patched only where Android/Termux needs different behavior.
+
+## Why a Termux fork?
 
-Qwen Code is an open-source AI agent for the terminal, optimized for [Qwen3-Coder](https://github.com/QwenLM/Qwen3-Coder).
-This **Termux Edition** fork keeps upstream behaviour while fixing what breaks on Android/Termux.
+Upstream targets desktop Unix and Windows first. On Android/Termux, the main breakpoints are:
 
-## Why a Termux Edition?
+- PTY availability on ARM64
+- install-time scripts that are fine on desktop but noisy on Termux
+- attention/notification workflows that are useful on mobile
 
-Upstream Qwen Code targets macOS/Linux/Windows. On Android/Termux, installs fail due to
-native dependency issues (PTY, node-gyp) and environment quirks.
+This fork keeps upstream behavior as close as possible while adding:
 
-Termux Edition fixes:
+- Android ARM64 PTY fallback via `@mmmbuto/node-pty-android-arm64`
+- optional `tts_notification` tool backed by `termux-tts-speak`
+- Termux environment detection for runtime-specific behavior
+- release docs and test suites intended to be run directly inside Termux
 
-- **Android PTY support** via `@mmmbuto/pty-termux-utils`
-- **Termux runtime patches** (base64 polyfills, character encoding)
-- **Termux-safe install** (skips husky + sandbox bundle on npm install)
-- **TTS Notifications** — speak completion/alerts via `termux-tts-speak`
-- **Tested on-device** — see [test-reports/](test-reports/)
+## Installation
 
-## Installation (Termux / Android)
+### Termux / Android
 
 ```bash
-# Requires: Termux (F-Droid), Node.js 20+
+pkg install nodejs-lts
+pkg install termux-api   # optional, only for TTS
+
 npm install -g @mmmbuto/qwen-code-termux@latest
 qwen --version
 ```
 
-**Requirements:**
-
-- [Termux (F-Droid)](https://f-droid.org/packages/com.termux/) — Google Play version has issues
-- Node.js 20+ (`pkg install nodejs-lts`)
-- `termux-api` package (optional, for TTS): `pkg install termux-api`
+Requirements:
 
-> **Not on Termux?** Use upstream instead:
-> `npm install -g @qwen-code/qwen-code@latest`
+- [Termux from F-Droid](https://f-droid.org/packages/com.termux/)
+- Node.js 20+
+- `termux-api` only if you want TTS notifications
 
-## Installation (Linux / macOS / Windows)
+### Non-Termux platforms
 
-For non-Termux platforms, use the official upstream:
+Use upstream:
 
 ```bash
-# Linux / macOS
-bash -c "$(curl -fsSL https://qwen-code-assets.oss-cn-hangzhou.aliyuncs.com/installation/install-qwen.sh)"
-
-# Windows (Admin CMD)
-curl -fsSL -o %TEMP%\install-qwen.bat https://qwen-code-assets.oss-cn-hangzhou.aliyuncs.com/installation/install-qwen.bat && %TEMP%\install-qwen.bat
-```
-
-Or via Homebrew:
-
-```bash
-brew install qwen-code
+npm install -g @qwen-code/qwen-code@latest
 ```
 
 ## Quick Start
 
 ```bash
-cd your-project/
+cd your-project
 qwen
-
-# Then inside the session:
-/help
-/auth
 ```
 
-On first use, you'll be prompted to sign in. Run `/auth` anytime to switch auth method.
+Useful first commands:
 
-Example prompts:
-
-```text
-What does this project do?
-Explain the codebase structure.
-Help me refactor this function.
-Generate unit tests for this module.
-```
+- `/help`
+- `/auth`
+- `/model`
 
 ## Authentication
 
-Two methods — API-KEY is recommended for headless/Termux environments.
-
-### API-KEY (recommended)
+For headless or Termux-heavy workflows, API-key auth is the practical default.
 
-Set up `~/.qwen/settings.json`:
+Example `~/.qwen/settings.json`:
 
 ```json
 {
   "modelProviders": {
     "openai": [
       {
-        "id": "qwen3.5-plus",
-        "name": "qwen3.5-plus",
-        "baseUrl": "https://dashscope.aliyuncs.com/compatible-mode/v1"
+        "id": "qwen3.6-plus",
+        "name": "qwen3.6-plus",
+        "baseUrl": "https://dashscope.aliyuncs.com/compatible-mode/v1",
+        "description": "Qwen via DashScope OpenAI-compatible API",
+        "envKey": "DASHSCOPE_API_KEY"
       }
     ]
   },
   "env": {
     "DASHSCOPE_API_KEY": "sk-your-key"
   },
-  "security": { "auth": { "selectedType": "openai" } },
-  "model": { "name": "qwen3.5-plus" }
+  "security": {
+    "auth": {
+      "selectedType": "openai"
+    }
+  },
+  "model": {
+    "name": "qwen3.6-plus"
+  }
 }
 ```
 
-### Qwen OAuth
+OAuth still works where a browser is available, but API-key auth is the safer recommendation on Termux and over SSH.
 
-```bash
-qwen
-/auth
-# Complete browser flow
-```
-
-> OAuth requires a browser — not available over SSH/headless. Use API-KEY instead.
+## Termux-specific features
 
-## Usage
+### TTS notifications
 
-### Interactive mode
+If `termux-api` is installed, the fork exposes a `tts_notification` tool that can speak short alerts:
 
 ```bash
-qwen
-# Use @ to reference files: @src/main.ts
+termux-tts-speak "Qwen Code Termux ready"
 ```
 
-### Headless mode
+### PTY fallback
 
-```bash
-qwen -p "your question"
-```
+The fork keeps upstream PTY loading first, then falls back to `@mmmbuto/node-pty-android-arm64` for Android ARM64.
 
-### Session commands
+### Release testing from Termux
 
-| Command     | Description                     |
-| ----------- | ------------------------------- |
-| `/help`     | Available commands              |
-| `/clear`    | Clear history                   |
-| `/compress` | Compress history to save tokens |
-| `/stats`    | Session info                    |
-| `/bug`      | Submit bug report               |
-| `/exit`     | Quit                            |
+Run the documented Termux release checks from:
 
-### Keyboard shortcuts
+- [docs/developers/BUILDING.md](docs/developers/BUILDING.md)
+- [test-reports/README.md](test-reports/README.md)
+- [test-reports/suites/latest/termux.md](test-reports/suites/latest/termux.md)
 
-- `Ctrl+C` — Cancel operation
-- `Ctrl+D` — Exit (empty line)
-- `Up/Down` — Command history
-
-## Termux-Specific Features
-
-### TTS Notifications
-
-When a task completes or needs your attention, Qwen Code can speak a notification
-using Android's text-to-speech engine:
-
-```bash
-# Install termux-api for TTS
-pkg install termux-api
-
-# TTS is used automatically by the tts_notification tool
-```
-
-### PTY Support
-
-Shell execution uses a PTY (pseudo-terminal) for proper ANSI colour and interactive
-command support. On Termux, PTY deps are auto-installed on first `npm install`.
-
-### Runtime Patches
-
-| File                                          | Purpose                        |
-| --------------------------------------------- | ------------------------------ |
-| `packages/core/src/patches/termux-runtime.ts` | Android base64 polyfill        |
-| `scripts/prepare-termux.cjs`                  | Skip husky + bundle on Termux  |
-| `scripts/postinstall.cjs`                     | Termux install confirmation    |
-| `packages/core/src/utils/termux-detect.ts`    | `isTermux()` detection utility |
-
-## Building from Source
+## Building from source
 
 ```bash
 git clone https://github.com/DioNanos/qwen-code-termux.git
@@ -197,47 +132,21 @@ cd qwen-code-termux
 npm install
 npm run build
 npm run bundle
-
-# Install globally
-npm install -g
 ```
 
-See [docs/developers/BUILDING.md](docs/developers/BUILDING.md) for full details.
-
-## Configuration
-
-| File                    | Scope   | Description                   |
-| ----------------------- | ------- | ----------------------------- |
-| `~/.qwen/settings.json` | User    | Global settings (recommended) |
-| `.qwen/settings.json`   | Project | Project-level overrides       |
-
-See the [authentication guide](https://qwenlm.github.io/qwen-code-docs/en/users/configuration/auth/) for all options.
-
-> **Security note:** Never commit API keys to version control.
+See [docs/developers/BUILDING.md](docs/developers/BUILDING.md) for the fork-specific notes.
 
 ## Troubleshooting
 
-- [Qwen Code docs](https://qwenlm.github.io/qwen-code-docs/en/users/support/troubleshooting/)
-- From the CLI: run `/bug` for a bug report template
-- [Test reports](test-reports/) — Termux-specific test results
-
-## Ecosystem
-
-- [**AionUi**](https://github.com/iOfficeAI/AionUi) — Modern GUI for Qwen Code
-- [**Gemini CLI Desktop**](https://github.com/Piebald-AI/gemini-cli-desktop) — Cross-platform desktop UI
-
-## Connect
-
-- [Discord](https://discord.gg/RN7tqZCeDK)
-- [Dingtalk](https://qr.dingtalk.com/action/joingroup?code=v1,k1,+FX6Gf/ZDlTahTIRi8AEQhIaBlqykA0j+eBKKdhLeAE=&_dt_no_comment=1&origin=1)
+- If you are not on Termux, install upstream instead of this fork.
+- If shell execution is broken on Android, verify the PTY dependency is present.
+- If TTS does nothing, install `termux-api` and check `termux-tts-speak`.
+- For release validation, use the Termux suite in [test-reports/suites/latest/termux.md](test-reports/suites/latest/termux.md).
 
 ## Acknowledgments
 
-This project is based on [Google Gemini CLI](https://github.com/google-gemini/gemini-cli) and
-[Qwen Code](https://github.com/QwenLM/qwen-code). We acknowledge and appreciate the excellent
-work of both teams. This fork focuses on Termux/Android compatibility and Termux-specific
-features.
+This fork is based on [Qwen Code](https://github.com/QwenLM/qwen-code) and exists to keep a release-quality Termux track with minimal divergence from upstream.
 
 ## License
 
-Apache-2.0 — see [LICENSE](./LICENSE)
+Apache-2.0

package/bundled/loop/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: loop
+description: Create a recurring loop that runs a prompt on a schedule. Usage - /loop 5m check the build, /loop check the PR every 30m, /loop run tests (defaults to 10m). /loop list to show jobs, /loop clear to cancel all.
+allowedTools:
+  - cron_create
+  - cron_list
+  - cron_delete
+---
+
+# /loop — schedule a recurring prompt
+
+## Subcommands
+
+If the input (after stripping the `/loop` prefix) is exactly one of these keywords, run the subcommand instead of scheduling:
+
+- **`list`** — call CronList and display the results. Done.
+- **`clear`** — call CronList, then call CronDelete for every job returned. Confirm how many were cancelled. Done.
+
+Otherwise, parse the input below into `[interval] <prompt…>` and schedule it with CronCreate.
+
+## Parsing (in priority order)
+
+1. **Leading token**: if the first whitespace-delimited token matches `^\d+[smhd]$` (e.g. `5m`, `2h`), that's the interval; the rest is the prompt.
+2. **Trailing "every" clause**: otherwise, if the input ends with `every <N><unit>` or `every <N> <unit-word>` (e.g. `every 20m`, `every 5 minutes`, `every 2 hours`), extract that as the interval and strip it from the prompt. Only match when what follows "every" is a time expression — `check every PR` has no interval.
+3. **Default**: otherwise, interval is `10m` and the entire input is the prompt.
+
+If the resulting prompt is empty, show usage `/loop [interval] <prompt>` and stop — do not call CronCreate.
+
+Examples:
+
+- `5m /babysit-prs` → interval `5m`, prompt `/babysit-prs` (rule 1)
+- `check the deploy every 20m` → interval `20m`, prompt `check the deploy` (rule 2)
+- `run tests every 5 minutes` → interval `5m`, prompt `run tests` (rule 2)
+- `check the deploy` → interval `10m`, prompt `check the deploy` (rule 3)
+- `check every PR` → interval `10m`, prompt `check every PR` (rule 3 — "every" not followed by time)
+- `5m` → empty prompt → show usage
+
+## Interval → cron
+
+Supported suffixes: `s` (seconds, rounded up to nearest minute, min 1), `m` (minutes), `h` (hours), `d` (days). Convert:
+
+| Interval pattern  | Cron expression        | Notes                                     |
+| ----------------- | ---------------------- | ----------------------------------------- |
+| `Nm` where N ≤ 59 | `*/N * * * *`          | every N minutes                           |
+| `Nm` where N ≥ 60 | `0 */H * * *`          | round to hours (H = N/60, must divide 24) |
+| `Nh` where N ≤ 23 | `0 */N * * *`          | every N hours                             |
+| `Nd`              | `0 0 */N * *`          | every N days at midnight local            |
+| `Ns`              | treat as `ceil(N/60)m` | cron minimum granularity is 1 minute      |
+
+**If the interval doesn't cleanly divide its unit** (e.g. `7m` → `*/7 * * * *` gives uneven gaps at :56→:00; `90m` → 1.5h which cron can't express), pick the nearest clean interval and tell the user what you rounded to before scheduling.
+
+## Action
+
+1. Call CronCreate with:
+   - `cron`: the expression from the table above
+   - `prompt`: the parsed prompt from above, verbatim (slash commands are passed through unchanged)
+   - `recurring`: `true`
+2. Briefly confirm: what's scheduled, the cron expression, the human-readable cadence, that recurring tasks auto-expire after 3 days, and that they can cancel sooner with CronDelete (include the job ID).
+3. **Then immediately execute the parsed prompt now** — don't wait for the first cron fire. If it's a slash command, invoke it via the Skill tool; otherwise act on it directly.
+
+## Input

package/bundled/qc-helper/SKILL.md

@@ -0,0 +1,151 @@
+---
+name: qc-helper
+description: Answer any question about Qwen Code usage, features, configuration, and troubleshooting by referencing the official user documentation. Also helps users view or modify their settings.json. Invoke with `/qc-helper` followed by a question, e.g. `/qc-helper how do I configure MCP servers?` or `/qc-helper change approval mode to yolo`.
+allowedTools:
+  - read_file
+  - edit_file
+  - grep_search
+  - glob
+  - read_many_files
+---
+
+# Qwen Code Helper
+
+You are a helpful assistant for **Qwen Code** — an AI coding agent for the terminal. Your job is to answer user questions about Qwen Code's usage, features, configuration, and troubleshooting by referencing the official documentation, and to help users modify their configuration when requested.
+
+## How to Find Documentation
+
+The official user documentation is available in the `docs/` subdirectory **relative to this skill's directory**. Use the `read_file` tool to load the relevant document on demand by concatenating this skill's base directory path with the relative doc path listed below.
+
+> **Example**: If the user asks about MCP servers, read `docs/features/mcp.md` (relative to this skill's directory).
+
+---
+
+## Documentation Index
+
+Use this index to locate the right document for the user's question. Load only the docs that are relevant — do not read everything at once.
+
+### Getting Started
+
+| Topic             | Doc Path                  |
+| ----------------- | ------------------------- |
+| Product overview  | `docs/overview.md`        |
+| Quick start guide | `docs/quickstart.md`      |
+| Common workflows  | `docs/common-workflow.md` |
+
+### Configuration
+
+| Topic                                     | Doc Path                                |
+| ----------------------------------------- | --------------------------------------- |
+| Settings reference (all config keys)      | `docs/configuration/settings.md`        |
+| Authentication setup                      | `docs/configuration/auth.md`            |
+| Model providers (OpenAI-compatible, etc.) | `docs/configuration/model-providers.md` |
+| .qwenignore file                          | `docs/configuration/qwen-ignore.md`     |
+| Themes                                    | `docs/configuration/themes.md`          |
+| Memory                                    | `docs/configuration/memory.md`          |
+| Trusted folders                           | `docs/configuration/trusted-folders.md` |
+
+### Features
+
+| Topic                                       | Doc Path                         |
+| ------------------------------------------- | -------------------------------- |
+| Approval mode (plan/default/auto_edit/yolo) | `docs/features/approval-mode.md` |
+| MCP (Model Context Protocol)                | `docs/features/mcp.md`           |
+| Skills system                               | `docs/features/skills.md`        |
+| Sub-agents                                  | `docs/features/sub-agents.md`    |
+| Sandbox / security                          | `docs/features/sandbox.md`       |
+| Slash commands                              | `docs/features/commands.md`      |
+| Headless / non-interactive mode             | `docs/features/headless.md`      |
+| LSP integration                             | `docs/features/lsp.md`           |
+| Checkpointing                               | `docs/features/checkpointing.md` |
+| Token caching                               | `docs/features/token-caching.md` |
+| Language / i18n                             | `docs/features/language.md`      |
+| Arena mode                                  | `docs/features/arena.md`         |
+
+### IDE Integration
+
+| Topic                   | Doc Path                                     |
+| ----------------------- | -------------------------------------------- |
+| VS Code integration     | `docs/integration-vscode.md`                 |
+| Zed IDE integration     | `docs/integration-zed.md`                    |
+| JetBrains integration   | `docs/integration-jetbrains.md`              |
+| GitHub Actions          | `docs/integration-github-action.md`          |
+| IDE companion spec      | `docs/ide-integration/ide-companion-spec.md` |
+| IDE integration details | `docs/ide-integration/ide-integration.md`    |
+
+### Extensions
+
+| Topic                           | Doc Path                                       |
+| ------------------------------- | ---------------------------------------------- |
+| Extension introduction          | `docs/extension/introduction.md`               |
+| Getting started with extensions | `docs/extension/getting-started-extensions.md` |
+| Releasing extensions            | `docs/extension/extension-releasing.md`        |
+
+### Reference & Support
+
+| Topic                      | Doc Path                               |
+| -------------------------- | -------------------------------------- |
+| Keyboard shortcuts         | `docs/reference/keyboard-shortcuts.md` |
+| Troubleshooting            | `docs/support/troubleshooting.md`      |
+| Uninstall guide            | `docs/support/Uninstall.md`            |
+| Terms of service & privacy | `docs/support/tos-privacy.md`          |
+
+---
+
+## Configuration Quick Reference
+
+When the user asks about configuration, the primary reference is `docs/configuration/settings.md`. Here is a quick orientation:
+
+### Config File Locations & Priority
+
+| Level   | Path                                                         | Description                            |
+| ------- | ------------------------------------------------------------ | -------------------------------------- |
+| User    | `~/.qwen/settings.json`                                      | Personal global config                 |
+| Project | `<project>/.qwen/settings.json`                              | Project-specific, overrides user level |
+| System  | macOS: `/Library/Application Support/QwenCode/settings.json` | Admin-level config                     |
+
+**Priority** (highest to lowest): CLI args > env vars > system settings > project settings > user settings > defaults
+
+**Format**: JSON with Comments (supports `//` and `/* */`), with environment variable interpolation (`$VAR` or `${VAR}`)
+
+### Common Config Categories
+
+| Category      | Key Config Keys                                                               | Reference                                                                 |
+| ------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
+| Permissions   | `permissions.allow/ask/deny`                                                  | `docs/configuration/settings.md`, `docs/features/approval-mode.md`        |
+| MCP Servers   | `mcpServers.*`, `mcp.*`                                                       | `docs/configuration/settings.md`, `docs/features/mcp.md`                  |
+| Tool Approval | `tools.approvalMode`                                                          | `docs/configuration/settings.md`, `docs/features/approval-mode.md`        |
+| Model         | `model.name`, `modelProviders`                                                | `docs/configuration/settings.md`, `docs/configuration/model-providers.md` |
+| General/UI    | `general.*`, `ui.*`, `ide.*`, `output.*`                                      | `docs/configuration/settings.md`                                          |
+| Context       | `context.*`                                                                   | `docs/configuration/settings.md`                                          |
+| Advanced      | `hooks`, `env`, `webSearch`, `security`, `privacy`, `telemetry`, `advanced.*` | `docs/configuration/settings.md`                                          |
+
+---
+
+## Workflow
+
+### Answering Questions
+
+1. **Identify the topic** from the user's question using the Documentation Index above
+2. **Use `read_file`** to load the relevant doc(s) — only load what you need
+3. **Provide a clear, concise answer** grounded in the documentation content
+4. If the docs don't cover the question, say so honestly and suggest where to look
+
+### Helping with Configuration Changes
+
+When the user wants to modify their configuration:
+
+1. **Read the relevant doc** to understand the config key, its type, allowed values, and defaults
+2. **Ask which config level** to modify if not specified: user (`~/.qwen/settings.json`) or project (`.qwen/settings.json`)
+3. **Use `read_file`** to check the current content of the target settings file
+4. **Use `edit_file`** to apply the change with correct JSON syntax
+5. **After every configuration change**, you MUST remind the user:
+
+> **Note: Most configuration changes require restarting Qwen Code (`/exit` then re-launch) to take effect.** Only a few settings (like `permissions`) are picked up dynamically.
+
+### Important Notes
+
+- Always ground your answers in the actual documentation content — do not guess or fabricate config keys
+- When showing config examples, use JSONC format with comments for clarity
+- If a question spans multiple topics (e.g., "How do I set up MCP with sandbox?"), read both relevant docs
+- For migration questions from other tools (Claude Code, Gemini CLI, etc.), check `docs/configuration/settings.md` for equivalent config keys

package/bundled/qc-helper/docs/_meta.ts

@@ -0,0 +1,30 @@
+export default {
+  'Getting started': {
+    type: 'separator',
+    title: 'Getting started', // Title is optional
+  },
+  overview: 'Overview',
+  quickstart: 'QuickStart',
+  'common-workflow': 'Command Workflows',
+  'Outside of the terminal': {
+    type: 'separator',
+    title: 'Outside of the terminal', // Title is optional
+  },
+  'integration-vscode': 'Visual Studio Code',
+  'integration-zed': 'Zed IDE',
+  'integration-jetbrains': 'JetBrains IDEs',
+  'integration-github-action': 'Github Actions',
+  'Code with Qwen Code': {
+    type: 'separator',
+    title: 'Code with Qwen Code', // Title is optional
+  },
+  features: 'Features',
+  configuration: 'Configuration',
+  extension: 'Extension',
+  reference: 'Reference',
+  support: 'Support',
+  // need refine
+  'ide-integration': {
+    display: 'hidden',
+  },
+};