QZX stands for Quick Zap Exchange. It is the name of an open-source Python CLI—and of its qzx package and executable—that gives AI agents, automation, and people one consistent command vocabulary across Windows, Linux, and macOS.

Is QZX completely free?

Yes. QZX is completely free to use, with no paid plans or paid features. Optional donations support ongoing development, but never unlock features or change the product experience.

What makes QZX different from Bash or PowerShell?

Traditional shells expose platform-specific commands. QZX provides one documented vocabulary for supported operations and a consistent result contract, avoiding separate Windows, Linux, and macOS instructions.

How does QZX help AI agents?

With --json, QZX returns structured fields such as success and message, plus command-specific details. Agents can inspect those fields instead of parsing terse terminal text.

Where can I check availability and risk?

Each command page states whether the command is on PyPI, whether it changes state, which privileges it may require, and whether dry-run is available.

QZX — Quick Zap Exchange

Predictable cross-platform commands for AI agents

QZX gives agents, automation and developers one documented CLI vocabulary for supported operations on Windows, Linux and macOS. It prints readable messages by default and complete structured results when you pass --json.

QZX is completely free and open source. Donations are welcome because they support ongoing development, but they never unlock features or change the product experience.

Explore commands See recorded output

Install published release 0.2.2.0.2

Verify on PyPI Release notes

python -m pip install qzx
qzx qzxListCommands
qzx getCurrentDate --json

The website also documents a newer development checkout. Every command page labels whether the capability is present in the published wheel.

An observed result

One documented interface instead of three date branches

The QZX snapshot is complete stdout from a real Windows 11 10.0.26200 run with QZX 0.2.2.0.2 and CPython 3.13.12; no fields were invented.

Without QZX

Windows PowerShell

(Get-Date).ToString("yyyy-MM-dd")

Linux

date +%F

macOS

date +%F

With QZX

qzx getCurrentDate --json

{
    "success": true,
    "date": "2026-07-25",
    "message": "Current date is Saturday, July 25, 2026 (ISO format: 2026-07-25)",
    "details": {
        "year": 2026,
        "month": 7,
        "month_name": "July",
        "day": 25,
        "day_of_week": "Saturday",
        "day_of_year": 206,
        "week_of_year": 30
    },
    "meta": {
        "command": "getCurrentDate",
        "duration_ms": 0.985,
        "schema_version": 1
    }
}

Captured on 25 July 2026; date and duration change on each run. See the reference and evidence.

What the interface changes

A smaller contract surface for supported work

One documented vocabulary

Use the same command name on supported hosts instead of maintaining a separate instruction for each shell.

Explicit machine output

Request JSON deliberately with --json, then inspect success, message and command-specific fields.

Visible limitations

Availability, platform dependencies, mutations, backups and observed evidence are documented instead of implied.

Published channel

PyPI 0.2.2.0.2

The inspected official wheel contains 93 historical command spellings that normalize to 93 current catalog capabilities. Its published metadata declares Python >=3.9.

Development documentation

Checkout 0.2.2.0.2

The current catalog documents 93 commands: the 93 capabilities reconciled with the wheel plus 0 development-only capabilities. The checkout requires Python >=3.13.

QZX supports the standard CPython 3.13.x build. Other Python versions or implementations may work, but experimental free-threaded CPython builds, PyPy, and other implementations are not certified. See the compatibility evidence.

Choose QZX with the boundary in view

QZX is a local command interface, not a sandbox or a guarantee of native parity. Prefer it when a documented command covers the operation and a consistent result contract helps. Use native APIs or the shell for capabilities QZX does not model.

Decision guide Security and telemetry Compatibility evidence