Project briefing
Understand an unfamiliar codebase
Surface technologies, dependency manifests, Git state, scan coverage and concrete findings before an AI agent starts editing.
qzx diagnoseProject .
QZX — Quick Zap Exchange
QZX: predictable cross-platform commands for AI agents
Give an AI agent or automation structured evidence before it changes anything. Inspect an unfamiliar project, diagnose disk-space pressure, or use the same documented system, file and development vocabulary across Windows, Linux and macOS; add --json when another program consumes the result.
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.
Install published Alpha 0.2.2.0.8
python -m pip install --upgrade qzx
qzx getCurrentDateTime --output-format iso --json
qzx listCommands file
qzx help findFiles- First success: Confirm QZX with a fast, read-only ISO timestamp.
- Explore: Filter the installed catalog to commands related to files.
- Understand: Inspect parameters, examples, maturity, and safety before execution.
These commands come from the same versioned onboarding contract packaged in the wheel and verified against the current checkout, PyPI, GitHub, and this website.
Prefer an isolated CLI? pipx install qzx keeps QZX's Python dependencies separate from project environments. If pip reports externally-managed-environment, use this route instead of forcing the system Python.
The primary installation command above is generated from QZX's current published channel, so you do not need to remember PyPI pre-release rules. QZX remains Alpha software; verify the installed identity with qzx version --json.
Start with a real problem
Get useful evidence before you change anything
The published Alpha already has complete read-only workflows for two common jobs. Run one as a readable briefing, or add --json when an agent or program should consume the evidence.
Storage triage
Find what is consuming disk space
Measure capacity, surface the largest files and verify duplicate evidence without deleting or changing anything.
qzx diagnoseStorage .
QZX is created and maintained by Alejandro Sánchez. If the free CLI solves part of your workflow but you need a custom integration, automation or implementation, there is a direct path to work with its creator. Optional support helps keep the open-source project moving.
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.8 and CPython 3.13.13; no fields were invented.
Without QZX
Windows PowerShell
(Get-Date).ToString("o")Linux
date --iso-8601=secondsmacOS
date +%Y-%m-%dT%H:%M:%S%zWith QZX
qzx getCurrentDateTime --output-format iso --json{
"success": true,
"message": "Current local date and time (ISO 8601): 2026-09-08T19:19:57.029830-05:00.",
"output": "2026-09-08T19:19:57.029830-05:00",
"output_format": "iso",
"date": {
"year": 2026,
"month": 9,
"month_name": "September",
"day": 8,
"day_of_week": "Tuesday",
"day_of_year": 251,
"iso_week": 37,
"iso_week_year": 2026,
"quarter": 3,
"is_leap_year": false
},
"time": {
"hour_24": 19,
"hour_12": 7,
"minute": 19,
"second": 57,
"microsecond": 29830,
"am_pm": "PM",
"timezone": "Hora est. Pacífico, Sudamérica",
"utc_offset": "-05:00"
},
"timestamp": 1788913197,
"iso_format": "2026-09-08T19:19:57.029830-05:00",
"meta": {
"command": "getCurrentDateTime",
"command_maturity": {
"stage": "alpha",
"label": "Alpha",
"sequence": 2,
"public_executable": true,
"stability": "interface_may_change",
"summary": "Available for real use and feedback while its interface and behavior can still evolve.",
"promotion_review_required": false,
"assessment_scope": "development_checkout"
},
"duration_ms": 2.348,
"schema_version": 1
}
}Captured on 8 September 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.
An open contract others can implement
QZX Result Contract v1 makes the promise downloadable
The stable core is deliberately small: every JSON result has an explicit boolean success and a useful non-empty message. Commands add typed evidence without forcing unrelated operations into one rigid payload.
{
"success": true,
"message": "Current local date and time returned in ISO 8601 format.",
"output": "2026-08-07T21:45:00-05:00",
"meta": {
"command": "getCurrentDateTime",
"duration_ms": 2.4,
"schema_version": 1
}
}Start in five minutes
A safer first workflow for terminal-capable agents
Install QZX, verify the real local catalog, begin with read-only commands, and give Codex, Claude Code, Gemini CLI, or another agent a durable JSON-first policy.
Open the AI agent quickstartArchitecture guide
MCP, CLI, or direct API?
Compare discovery, transport, permissions, portability, and maintenance without pretending that one interface wins every workload.
Read the MCP vs CLI vs API guidePublished channel
PyPI 0.2.2.0.8
The inspected official wheel contains 88 historical command spellings that normalize to 88 current catalog capabilities. Its published metadata declares Python >=3.11.
Development documentation
Checkout 0.2.2.0.8
The current catalog documents 88 commands: the 88 capabilities reconciled with the wheel plus 0 development-only capabilities. The checkout requires Python >=3.11.
QZX supports standard CPython 3.11 or newer. Its cross-platform certification matrix uses standard CPython 3.13.x; 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.