Documentation

Quick start

1. Run the installer (Termux):

bash <(curl -fsSL https://raw.githubusercontent.com/Vaizer0/zero-termux/main/install.sh)

1. Verify: zero --version prints the framework version and zero list ai shows tools with installed state.
2. Install what you need — a module or individual tools:

zero install dev --gh --fzf --jq
zero install ai --qwen-code
zero install shell

1. Open the docs site any time: zero open zero (or zero open ai for a module anchor).

Command reference

Every command follows zero <command> [target] [--tool …]. Targets are the 9 modules: ai lang db editor dev npm shell ui auto.

• zero install <module> — whole category, or
• zero install <module> --tool1 --tool2 — selected tools only.
• zero list <module> shows what exists and what is installed; zero show <module> --<tool> prints help for one tool.
• Updates: zero update zero (framework), zero update <module> (tools), pkg upgrade (APT packages).
• Removal: zero uninstall <module> [--tool …]; broken installs recover with zero reinstall <module>.

The full reference is on the commands page.

Modules

9 modules, 99 tools. Each tool is a plain bash installer under zero/tools/<category>/<tool>/ exporting the four lifecycle verbs.

Browse and search all of them on the modules explorer.

APT package repository

228 packages, GPG-signed on every build, served from https://vaizer0.github.io/zero-termux/repo (suite zero-termux). The installer configures it; manual setup:

echo "deb [trusted=yes arch=all] https://vaizer0.github.io/zero-termux/repo zero-termux main" \
  > "$PREFIX/etc/apt/sources.list.d/zero-termux.list"

curl -fsSL https://vaizer0.github.io/zero-termux/zero-termux.gpg \
  -o "$PREFIX/etc/apt/trusted.gpg.d/zero-termux.gpg"

apt update
pkg search <name>    # browse
pkg install <name>   # install

Verify the key fingerprint: DF2C7FCDABF96DF4298E953BB0C7EC7C1BB9C494. Browse the catalog on the packages page or in assets/PACKAGES.md.

Version policy

• Rolling tools → latest. Registry installs use @latest; GitHub-release binaries resolve the newest release at install time via the GitHub API (no stale fallback — clear error if unreachable).
• Pins are the exception. Build-critical/source-tag pins carry a # Zero-Termux: justified pin — <reason> comment plus a manifest entry; CI fails on any new unapproved pin.
• Package Version: ≠ tool version. It is the package revision. The installed tool's version is whatever upstream latest resolves to.
• A weekly maintenance workflow reports drift between justified pins and latest upstream.

Next steps

• Guides — installation options, customization, troubleshooting, migration.
• Architecture — how the pieces fit together.
• Security — signing model and what runs on your device.
• Contributing — add a tool or a package.