Codexy
Codexy is a Codex harness for coordinating agents through planning, implementation, verification, and review.
It helps Codex turn a broad repository request into an owned plan, divide work among agents, implement changes, verify actual outcomes, and keep the next handoff tied to current evidence.
Components
Codexy is delivered as three cooperating components. github and devtools
each depend on core; the installer adds those dependencies automatically.
| Component | Plugin | What it adds |
|---|---|---|
core |
codexy |
Orchestration, finite goals and plans, worktree ownership, specialist roles, instruction hooks, and proof-driven completion. |
github |
codexy-github |
Issue-to-merge workflows for branches, pull requests, CI, review feedback, releases, and GitHub safety checks. |
devtools |
codexy-devtools |
Local Codegraph and LSP servers, configuration, wrappers, and developer-tool guidance. |
The component model lets each repository install the capabilities it needs without losing a single ownership and verification contract.
Install
Install the getcodexy command, then install the complete Codexy product:
uv tool install getcodexy
uv tool update-shell
Start a new shell so the updated tool path is available, then install Codexy:
getcodexy install
The default selection installs core, github, and devtools. To choose a
smaller dependency closure, name the optional components you need:
getcodexy install core
getcodexy install github
getcodexy install devtools
getcodexy install github devtools
Open a fresh Codex session after installation or update so the host can expose the installed plugins, skills, agents, hooks, and MCP servers.
Maintain and check Codexy
Keep the installer and installed component selection current, inspect health, or remove an optional component:
uv tool upgrade getcodexy
getcodexy update
getcodexy status
getcodexy doctor
getcodexy remove github
status reports the installed inventory and its consistency. doctor checks
host readiness and the health of each installed component. Update and removal
operations preserve the dependency closure and reject inconsistent selections.
Project links
1 maintainer
Metadata
1 maintainer
Release files for getcodexy 1.13.1
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 | |
|---|---|---|---|---|
| getcodexy-1.13.1.tar.gz | 95.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| getcodexy-1.13.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 234.2 kB
Release files / getcodexy-1.13.1.tar.gz
| Download URL | getcodexy-1.13.1.tar.gz |
|---|---|
| Size | 95.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef8e15e126498ddcfb6f18b8b4e34757bdd10b853aeda6bd8d388cdba6d7f911
|
|
BLAKE2b-256 checksum How to use checksums |
10c98c993b529ab2248f54701b0b42349ebe70816d48c4391da9c758b10d520d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 4, 2026.
Transparency logRelease files / getcodexy-1.13.1-py3-none-any.whl
| Download URL | getcodexy-1.13.1-py3-none-any.whl |
|---|---|
| Size | 139.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7081d506a50cafc6dec636efbfab048cd4ca3285bc57beec0a36620c2d3d53e6
|
|
BLAKE2b-256 checksum How to use checksums |
7538876fb702dd18f209f6efc9239b460b0798988838256245534ed2546ce6f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 4, 2026.
Transparency logSecurity for getcodexy 1.13.1
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for getcodexy-1.13.1.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 Oct 4, 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.
