CueApril for Python package managers
This package runs the same CueApril CLI as the npm package. Python 3.10 or later and an installed Node.js 20 or later are required. It bundles the CLI's JavaScript and skill; it installs no Python runtime dependencies, runs no npm install and downloads no runtime when launched.
Install with your usual Python package manager:
pipx install cueapril
cueapril init
# Or run in an isolated environment:
uvx cueapril init
# A regular Python environment also works:
python -m pip install cueapril
python -m cueapril --help
Have node on PATH before running these commands. The launcher checks its version and replaces itself with the bundled CLI, preserving arguments, environment, standard input/output and exit status. It reports a missing or old Node.js installation with exit code 5. It does not install Node.js for you. Choose either the Python or npm installation for your normal cueapril command; both expose that command name.
cueapril init connects a coding agent through one browser approval. It then checks project setup and can configure Claude Code, Codex, Gemini CLI and Cursor. A scoped agent key can also come from the CUEAPRIL_API_KEY environment variable. Use CUEAPRIL_URL to select another API origin. The Python launcher never reads, prints or passes a key as a command-line argument; it preserves the existing CLI environment and credential-store behavior.
cueapril projects
cueapril setup --project PROJECT_ID
cueapril assess --pr https://github.com/OWNER/REPO/pull/42 --wait --json
cueapril status ASSESSMENT_ID --json
cueapril wait ASSESSMENT_ID --timeout 4 --json
cueapril results ASSESSMENT_ID --all --json
cueapril mcp-config --client codex
Assessment exit codes are unchanged: 0 passed; 1 failed; 2 incomplete or cancelled; 3 blocked; 4 still running; 5 usage, authentication, API or launcher error. A CLI wait timeout leaves the assessment running. Each server wait call lasts at most 50 seconds.
The complete CLI reference is bundled in cueapril/_cli/README.md; public setup documentation is at https://app.cueapril.com/agents. The Python package contains the same Node modules, package metadata and cueapril-qa skill as the unscoped npm package.
Source maintenance
From the CueApril repository, synchronize the bundled CLI after a change:
node packages/quality-python/scripts/sync-cli.mjs --sync --repository-root .
node packages/quality-python/scripts/sync-cli.mjs --check --repository-root .
python -m unittest discover -s packages/quality-python/tests
The sync script uses the repository's canonical npm package builder in a temporary directory with packing disabled. It compares every bundled file and records deterministic hashes in bundled-cli.json; --check fails if a file, version or manifest differs. It performs no npm command or network request. The initial release additionally compares the source with the independently reviewed npm staging directory. A distribution build includes those already reviewed bytes and does not fetch or rewrite the bundled CLI.
Metadata
Release files for cueapril 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cueapril-1.1.0.tar.gz | 79.4 kB | With provenance | Details for cueapril-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cueapril-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for cueapril-1.1.0-py3-none-any.whl |
Total release size: 161.4 kB
Release files / cueapril-1.1.0.tar.gz
| Download URL | cueapril-1.1.0.tar.gz |
|---|---|
| Size | 79.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
80d34ec57c84c8a96e2d0a9f46c1048070c7c8ecaf91dc8964774ee62fbf94de
|
|
BLAKE2b-256 checksum How to use checksums |
712120742bd731b87ec522e096abb9431099c10c358754dfd2a3ec76500a0fbd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.
Transparency logRelease files / cueapril-1.1.0-py3-none-any.whl
| Download URL | cueapril-1.1.0-py3-none-any.whl |
|---|---|
| Size | 82.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2a020bc6627ace5ee4916706a4456ffc02c6c4a4a13b40ded0026a16c7dcd438
|
|
BLAKE2b-256 checksum How to use checksums |
4f928b138d41ec17a87cf1e36209936861b27f450a73c8eb4dec6edc48c45f1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.
Transparency logSecurity for cueapril 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for cueapril-1.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 16, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.