Skip to main content

zpx

CLI de ZPX Forge: conecta tu Claude Code o Codex con tu fábrica de software.

Uso

uvx zpx health          # probar sin instalar nada
pipx install zpx        # instalarlo de forma permanente
uv tool install zpx     # o con uv
pip install zpx         # o con pip, dentro de un entorno virtual
zpx                     # panel interactivo con comandos /
zpx login               # aprobar el código desde el navegador
zpx config language es  # español (en para volver al inglés)
zpx version             # versión del CLI
zpx health              # salud de la plataforma
zpx health --json       # en JSON
zpx health --url http://localhost:3000   # otra instancia

El CLI inicia en inglés. También puedes elegir el idioma en /config o durante /setup.

La URL por defecto es https://www.zpxforge.com; también se puede fijar con la variable ZPX_URL.

Documentación: https://zpxforge.com/docs

Publicar en PyPI

Con la versión ya construida, ejecuta:

cd ~/zynplex/zpxforge/cli && uv publish

Sincronizar el harness del proyecto

Desde el repositorio del cliente, ejecuta zpx y selecciona /setup. Al elegir el proyecto, el CLI descarga desde Forge la versión asignada de su plantilla, las políticas, la configuración del proyecto, los roles y las skills activas (incluidas las propias). Claude Code y Codex reciben sus definiciones en sus respectivas carpetas.

Después de cambiar la configuración en Forge, repite /setup o ejecuta zpx skill install en ese repositorio. El CLI actualiza y retira los archivos administrados según el registro de .zpx/installed.json y señala los conflictos con ediciones locales.

Forge identifica la configuración efectiva de cada proyecto por su contenido. El panel de skills muestra la revisión vigente. Al abrir el CLI en un repositorio vinculado, y al consultar zpx context, el CLI compara esa revisión con la última instalada. Claude y Codex reciben la instrucción de sincronizar al consultar el contexto. Para integraciones, zpx context --json expone harness.revision y harness.sync.required.

Metadata

Release files for zpx 0.2.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for zpx 0.2.3
File Size Uploaded Provenance Actions
zpx-0.2.3.tar.gz 29.6 kB Without provenance Details for zpx-0.2.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for zpx 0.2.3
File Interpreter ABI Platform Actions
zpx-0.2.3-py3-none-any.whl Python 3 none any Details for zpx-0.2.3-py3-none-any.whl

Total release size: 62.4 kB

Release files / zpx-0.2.3.tar.gz

Download URL zpx-0.2.3.tar.gz
Size 29.6 kB
Tags Source
SHA-256 checksum
How to use checksums
ac6e629e3532de585bbd822a31193e42bc1669d82ca33901ad92ce3610869f64
BLAKE2b-256 checksum
How to use checksums
0f10f4f1a7598b7a1d2b6725c188ffa57d91c4e2af5d535247e25d8efce22101
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / zpx-0.2.3-py3-none-any.whl

Download URL zpx-0.2.3-py3-none-any.whl
Size 32.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
366d59b071e1c07472aedbcf4d2a82808b617c233a30235af4accd3cbe13f9c3
BLAKE2b-256 checksum
How to use checksums
7385da01b22f79ff307dfa343611e0d7fd51f4674b665155469cff35c14826aa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.21 {"installer":{"name":"uv","version":"0.11.21","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for zpx 0.2.3

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page