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

package/README.md

@@ -1,6 +1,6 @@
 <div align="center">
 
-[![npm version](https://img.shields.io/npm/v/@mmmbuto/qwen-code-termux/0.12.0-termux.svg)](https://www.npmjs.com/package/@mmmbuto/qwen-code-termux/v/0.12.0-termux)
+[![npm version](https://img.shields.io/npm/v/@mmmbuto/qwen-code-termux.svg)](https://www.npmjs.com/package/@mmmbuto/qwen-code-termux)
 [![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](./LICENSE)
 [![Node.js Version](https://img.shields.io/badge/node-%3E%3D20.0.0-brightgreen.svg)](https://nodejs.org/)
 [![Downloads](https://img.shields.io/npm/dm/@mmmbuto/qwen-code-termux.svg)](https://www.npmjs.com/package/@mmmbuto/qwen-code-termux)
@@ -16,102 +16,228 @@
 
 </div>
 
-Qwen Code is an open-source AI agent for the terminal, optimized for **Qwen3-Coder**.  
-This repository/package is a **Termux-first build** that keeps upstream behavior, while fixing the parts that commonly break on Android/Termux (notably PTY and a few runtime quirks).
+> 🎉 **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.
 
-> **Not on Termux?** Use upstream: `npm install -g @qwen-code/qwen-code@latest` (or Homebrew).  
-> **On Termux?** Use this package: `npm install -g @mmmbuto/qwen-code-termux@latest`.
-
-![](https://gw.alicdn.com/imgextra/i1/O1CN01D2DviS1wwtEtMwIzJ_!!6000000006373-2-tps-1600-900.png)
+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.
 
 ## Why a Termux Edition?
 
-Upstream Qwen Code targets macOS/Linux/Windows. On Android/Termux, installs may fail due to native dependency issues (PTY / build tooling) and small environment differences.
+Upstream Qwen Code targets macOS/Linux/Windows. On Android/Termux, installs fail due to
+native dependency issues (PTY, node-gyp) and environment quirks.
 
-Termux Edition focuses on:
+Termux Edition fixes:
 
-- **Android PTY support** via `@mmmbuto/pty-termux-utils` + `@mmmbuto/node-pty-android-arm64` (optional dependency)
-- **Termux runtime patches** (polyfills/quirks, clipboard behavior)
-- **Termux-safe install** (avoid node-gyp/husky pitfalls where possible)
-- **Tested on-device** — see [test-reports/](test-reports/README.md)
+- **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 (Termux / Android)
 
-### Prerequisites
+```bash
+# Requires: Termux (F-Droid), Node.js 20+
+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`
 
-- Termux (recommended from F-Droid)
-- Node.js **20+** (Termux `nodejs-lts` is recommended)
+> **Not on Termux?** Use upstream instead:
+> `npm install -g @qwen-code/qwen-code@latest`
+
+## Installation (Linux / macOS / Windows)
+
+For non-Termux platforms, use the official upstream:
 
 ```bash
-pkg update -y && pkg upgrade -y
-pkg install -y nodejs-lts git
+# 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
 ```
 
-Optional (recommended) for extra tools:
+Or via Homebrew:
 
-- Install the **Termux:API** Android app
-- Install the Termux package:
+```bash
+brew install qwen-code
+```
+
+## Quick Start
 
 ```bash
-pkg install -y termux-api
+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.
+
+Example prompts:
+
+```text
+What does this project do?
+Explain the codebase structure.
+Help me refactor this function.
+Generate unit tests for this module.
 ```
 
-### Install
+## Authentication
+
+Two methods — API-KEY is recommended for headless/Termux environments.
+
+### API-KEY (recommended)
+
+Set up `~/.qwen/settings.json`:
+
+```json
+{
+  "modelProviders": {
+    "openai": [
+      {
+        "id": "qwen3.5-plus",
+        "name": "qwen3.5-plus",
+        "baseUrl": "https://dashscope.aliyuncs.com/compatible-mode/v1"
+      }
+    ]
+  },
+  "env": {
+    "DASHSCOPE_API_KEY": "sk-your-key"
+  },
+  "security": { "auth": { "selectedType": "openai" } },
+  "model": { "name": "qwen3.5-plus" }
+}
+```
+
+### Qwen OAuth
 
 ```bash
-npm install -g @mmmbuto/qwen-code-termux@latest
-qwen --version
+qwen
+/auth
+# Complete browser flow
 ```
 
-## Quick Start
+> OAuth requires a browser — not available over SSH/headless. Use API-KEY instead.
+
+## Usage
+
+### Interactive mode
 
 ```bash
-qwen              # Interactive
-qwen -p "Hello"   # Non-interactive
-qwen /help        # Commands
-qwen /auth        # Authentication
+qwen
+# Use @ to reference files: @src/main.ts
 ```
 
-## Resources
+### Headless mode
 
-- **Test Reports**: [test-reports/](test-reports/README.md)
-- **Patches**: [patches/](patches/README.md)
-- **Build**: [docs/developers/BUILDING.md](docs/developers/BUILDING.md)
-- **Config**: [docs/users/configuration.md](docs/users/configuration.md)
+```bash
+qwen -p "your question"
+```
 
----
+### Session commands
 
-## Changelog & Releases
+| Command     | Description                     |
+| ----------- | ------------------------------- |
+| `/help`     | Available commands              |
+| `/clear`    | Clear history                   |
+| `/compress` | Compress history to save tokens |
+| `/stats`    | Session info                    |
+| `/bug`      | Submit bug report               |
+| `/exit`     | Quit                            |
 
-- [CHANGELOG.md](./CHANGELOG.md)
+### Keyboard shortcuts
 
-## Troubleshooting
+- `Ctrl+C` — Cancel operation
+- `Ctrl+D` — Exit (empty line)
+- `Up/Down` — Command history
 
-If you encounter issues, check the [upstream troubleshooting guide](https://qwenlm.github.io/qwen-code-docs/en/users/support/troubleshooting/).
+## Termux-Specific Features
 
-To report a bug from within the CLI, run `/bug`.
+### TTS Notifications
 
-## Support
+When a task completes or needs your attention, Qwen Code can speak a notification
+using Android's text-to-speech engine:
 
-If this Termux edition helps you, you can support the project on Ko-fi:
+```bash
+# Install termux-api for TTS
+pkg install termux-api
 
-- https://ko-fi.com/dionanos
+# TTS is used automatically by the tts_notification tool
+```
 
-## Connect with Upstream
+### PTY Support
 
-- Discord: https://discord.gg/ycKBjdNd
-- Dingtalk: https://qr.dingtalk.com/action/joingroup?code=v1,k1,+FX6Gf/ZDlTahTIRi8AEQhIaBlqykA0j+eBKKdhLeAE=&_dt_no_comment=1&origin=1
+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`.
 
-## Acknowledgments
+### 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
+
+```bash
+git clone https://github.com/DioNanos/qwen-code-termux.git
+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.
 
-This project is based on [Google Gemini CLI](https://github.com/google-gemini/gemini-cli). We acknowledge and appreciate the excellent work of the Gemini CLI team. Our main contribution focuses on parser-level adaptations to better support Qwen-Coder models.
+## 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.
+
+## 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)
+
+## 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.
 
 ## License
 
-Original project by Qwen Team: https://github.com/QwenLM/qwen-code<br>
-Apache License 2.0 (upstream Qwen Code)<br>
-Termux-port maintenance by Davide A. Guglielmi<br>
-See [LICENSE](./LICENSE) for details and upstream terms.<br>
-Made in Italy 🇮🇹
+Apache-2.0 — see [LICENSE](./LICENSE)

package/dist/bundled/review/SKILL.md

@@ -0,0 +1,123 @@
+---
+name: review
+description: Review changed code for correctness, security, code quality, and performance. Use when the user asks to review code changes, a PR, or specific files. Invoke with `/review`, `/review <pr-number>`, or `/review <file-path>`.
+allowedTools:
+  - task
+  - run_shell_command
+  - grep_search
+  - read_file
+  - glob
+---
+
+# Code Review
+
+You are an expert code reviewer. Your job is to review code changes and provide actionable feedback.
+
+## Step 1: Determine what to review
+
+Your goal here is to understand the scope of changes so you can dispatch agents effectively in Step 2. Based on the arguments provided:
+
+- **No arguments**: Review local uncommitted changes
+  - Run `git diff` and `git diff --staged` to get all changes
+  - If both diffs are empty, inform the user there are no changes to review and stop here — do not proceed to the review agents
+
+- **PR number or URL** (e.g., `123` or `https://github.com/.../pull/123`):
+  - Save the current branch name, stash any local changes (`git stash --include-untracked`), then `gh pr checkout <number>`
+  - Run `gh pr view <number>` and save the output (title, description, base branch, etc.) to a temp file (e.g., `/tmp/pr-review-context.md`) so agents can read it without you repeating it in each prompt
+  - Note the base branch (e.g., `main`) — agents will use `git diff <base>...HEAD` to get the diff and can read files directly
+
+- **File path** (e.g., `src/foo.ts`):
+  - Run `git diff HEAD -- <file>` to get recent changes
+  - If no diff, read the file and review its current state
+
+## Step 2: Parallel multi-dimensional review
+
+Launch **four parallel review agents** to analyze the changes from different angles. Each agent should focus exclusively on its dimension.
+
+**IMPORTANT**: Do NOT paste the full diff into each agent's prompt — this duplicates it 4x. Instead, give each agent the command to obtain the diff, a concise summary of what the changes are about, and its review focus. Each agent can read files and search the codebase on its own.
+
+### Agent 1: Correctness & Security
+
+Focus areas:
+
+- Logic errors and edge cases
+- Null/undefined handling
+- Race conditions and concurrency issues
+- Security vulnerabilities (injection, XSS, SSRF, path traversal, etc.)
+- Type safety issues
+- Error handling gaps
+
+### Agent 2: Code Quality
+
+Focus areas:
+
+- Code style consistency with the surrounding codebase
+- Naming conventions (variables, functions, classes)
+- Code duplication and opportunities for reuse
+- Over-engineering or unnecessary abstraction
+- Missing or misleading comments
+- Dead code
+
+### Agent 3: Performance & Efficiency
+
+Focus areas:
+
+- Performance bottlenecks (N+1 queries, unnecessary loops, etc.)
+- Memory leaks or excessive memory usage
+- Unnecessary re-renders (for UI code)
+- Inefficient algorithms or data structures
+- Missing caching opportunities
+- Bundle size impact
+
+### Agent 4: Undirected Audit
+
+No preset dimension. Review the code with a completely fresh perspective to catch issues the other three agents may miss.
+Focus areas:
+
+- Business logic soundness and correctness of assumptions
+- Boundary interactions between modules or services
+- Implicit assumptions that may break under different conditions
+- Unexpected side effects or hidden coupling
+- Anything else that looks off — trust your instincts
+
+## Step 3: Restore environment and present findings
+
+If you checked out a PR branch in Step 1, restore the original state first: check out the original branch, `git stash pop` if changes were stashed, and remove the temp file.
+
+Then combine results from all four agents into a single, well-organized review. Use this format:
+
+### Summary
+
+A 1-2 sentence overview of the changes and overall assessment.
+
+### Findings
+
+Use severity levels:
+
+- **Critical** — Must fix before merging. Bugs, security issues, data loss risks.
+- **Suggestion** — Recommended improvement. Better patterns, clearer code, potential issues.
+- **Nice to have** — Optional optimization. Minor style tweaks, small performance gains.
+
+For each finding, include:
+
+1. **File and line reference** (e.g., `src/foo.ts:42`)
+2. **What's wrong** — Clear description of the issue
+3. **Why it matters** — Impact if not addressed
+4. **Suggested fix** — Concrete code suggestion when possible
+
+### Verdict
+
+One of:
+
+- **Approve** — No critical issues, good to merge
+- **Request changes** — Has critical issues that need fixing
+- **Comment** — Has suggestions but no blockers
+
+## Guidelines
+
+- Be specific and actionable. Avoid vague feedback like "could be improved."
+- Reference the existing codebase conventions — don't impose external style preferences.
+- Focus on the diff, not pre-existing issues in unchanged code.
+- Keep the review concise. Don't repeat the same point for every occurrence.
+- When suggesting a fix, show the actual code change.
+- Flag any exposed secrets, credentials, API keys, or tokens in the diff as **Critical**.