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
One cross-platform CLI for the diagnostics AI agents keep reimplementing
Inspect projects, storage, websites and system state with one Python CLI on Windows, Linux and macOS. Read the result yourself or add --json so an AI agent or automation gets explicit, structured evidence instead of guessing from shell output.
Free and open source · 89 commands in the published wheel · created and maintained by Alejandro Sánchez.
The primary button copies the current PyPI install plus one harmless read-only check. Prefer to browse first? See three useful workflows or browse the command catalog.
Two commands · no account · read-only first check
Try QZX in 60 seconds
python -m pip install --upgrade qzx
qzx getCurrentDateTime --output-format iso --json- 1. Install: get the current published package from PyPI.
- 2. Run: Confirm QZX with a fast, read-only ISO timestamp.
- 3. Confirm: if the JSON result contains
"success": trueand a non-emptymessage, QZX is ready.
Need an isolated CLI or a managed-system Python?
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.
This starter is generated from QZX's published onboarding contract, so the site, wheel, PyPI release and GitHub release stay on the same first-success path.
Next: turn these commands into a project briefingStart 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 .
Website not loading?
Check DNS, certificate validity and HTTP separately, then decide what to inspect next without changing server settings.
Use the DNS, TLS and HTTP workflowQZX 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.9 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-10T14:51:35.977340-05:00.",
"output": "2026-09-10T14:51:35.977340-05:00",
"output_format": "iso",
"date": {
"year": 2026,
"month": 9,
"month_name": "September",
"day": 10,
"day_of_week": "Thursday",
"day_of_year": 253,
"iso_week": 37,
"iso_week_year": 2026,
"quarter": 3,
"is_leap_year": false
},
"time": {
"hour_24": 14,
"hour_12": 2,
"minute": 51,
"second": 35,
"microsecond": 977340,
"am_pm": "PM",
"timezone": "Hora est. Pacífico, Sudamérica",
"utc_offset": "-05:00"
},
"timestamp": 1789069895,
"iso_format": "2026-09-10T14:51:35.977340-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": 3.731,
"schema_version": 1
}
}Captured on 10 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.9
The inspected official wheel contains 89 historical command spellings that normalize to 89 current catalog capabilities. Its published metadata declares Python >=3.11.
Development documentation
Checkout 0.2.2.0.9
The current catalog documents 89 commands: the 89 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.