sequential-hooks
sequential-hooks runs coding-agent hooks in a strict order. Without a wrapper, a host may start
several hooks concurrently or in an undocumented order. A validator can then inspect an old tool
input while another hook is still replacing it. Register one wrapper hook and place the former hook
commands inside it as ordered steps.
Quick start
sequential-hooks requires native CPython 3.13 or newer and uv. The project is not published to
a package index. Install the current checkout from the repository root:
uv tool install .
To update an existing installation after pulling changes:
uv tool install --reinstall .
sequential-hooks has no configuration file. Choose the coding agent that will run the wrapper, then add the registration from its setup guide:
Check compatibility for the recorded host versions and known host limits,
and platforms for process handling. The guides use first-hook,
second-hook, and audit-hook as sample child commands. Replace them with hooks you have
installed and want to run in order. Move those child hooks into the wrapper and remove their
separate registrations, or the host may still start duplicate copies concurrently.
The wrapper command expects a native host payload on stdin. Configure it as a host hook rather than running the hook command interactively. After saving the registration, inspect it with the matching read-only report:
sequential-hooks doctor --agent claude
sequential-hooks doctor --agent codex
sequential-hooks doctor --agent agy
Exit 0 means the findings are informational. Exit 1 means at least one warning or error needs action. The troubleshooting guide explains common findings.
Antigravity requires an explicit event in each hook command. An all-neutral Antigravity pre-tool
chain emits the host's real automatic allow decision; it does not preserve the ordinary
permission prompt. Review the Antigravity setup guide before enabling it.
How commands compose
-a, --agent selects the installed host adapter for a coding agent. The built-in names are
claude, codex, and agy; a third-party adapter installed with
uv tool install . --with PACKAGE is selected by its own name. Nothing is inferred from the
payload. See adding a host.
-h, --help prints help for wrapper mode; doctor -h and doctor --help print doctor help.
sequential-hooks --agent codex --step-timeout 30 defsort hook --agent codex -- docwrap hook --agent codex
The exact -- token separates steps and cannot be passed to a step. Each child receives its own
literal arguments, including its own --agent; wrapper options are not inherited by child
commands.
Continue with the documentation map, concepts, security, or the CLI reference.
Metadata
Release files for sequential-hooks 0.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 |
|---|---|---|---|---|
| sequential_hooks-0.1.0.tar.gz | 143.6 kB | With provenance | Details for sequential_hooks-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sequential_hooks-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for sequential_hooks-0.1.0-py3-none-any.whl |
Total release size: 258.9 kB
Release files / sequential_hooks-0.1.0.tar.gz
| Download URL | sequential_hooks-0.1.0.tar.gz |
|---|---|
| Size | 143.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f16032c64903a053efe25b16d6fc5195eb0cedba4613aab63a2c0463b095dab
|
|
BLAKE2b-256 checksum How to use checksums |
edb78de75934c45c8215843b99ba77be27cca77d797a55e29e172d38704605e0
|
| 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 Sep 30, 2026.
Transparency logRelease files / sequential_hooks-0.1.0-py3-none-any.whl
| Download URL | sequential_hooks-0.1.0-py3-none-any.whl |
|---|---|
| Size | 115.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
65be23abb40150106a0c3e61d9eb467678c7b764bfaf5c1ac21bff0a3b1f8ca8
|
|
BLAKE2b-256 checksum How to use checksums |
a889e550b0a5d91bdbaff9e5edf11bc54ae3cd5b804f9d147fe2d1b05d967a00
|
| 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 Sep 30, 2026.
Transparency logSecurity for sequential-hooks 0.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 sequential_hooks-0.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 Sep 30, 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.