unharness
Compile a project's manifesto stack into a Claude Code session's system prompt, and launch the session with the harness's own instructions switched off.
/compile-commitments
uvx unharness prompt | uvx unharness launch -- claude
To run the source at the v3.7.1 tag instead, use uvx --from "git+https://github.com/ryzhakar/llm-manifestos@v3.7.1#subdirectory=plugin/unharness" unharness in place of uvx unharness. The launcher's input is reopened on the terminal.
The strip table in the Unharness section of plugin/README.md lists every switch launch passes, and unharness switches prints it.
A pypi-<version> tag on a commit whose pyproject.toml carries that version publishes it to PyPI; v<version> tags release the plugin and do not publish.
unharness prompt [--config PATH] [--digests] [--stack-digests] [--overlap] [--minified]prints the compiled prompt.--digestsand--stack-digestsswap manifesto texts for digests,--overlaplets stack digests share a manifesto, and--minifiedloads the min pair, the two.min.mdsession files; the Unharness section ofplugin/README.mdstates the cover rule.unharness stack [--config PATH] [SLUG ...]prints the<stack>block and the constitution; given slugs, it prints those manifestos alone.unharness stamp DIGEST [--config PATH]writes the digest's entry into itsindex.json, as inunharness stamp .claude/digests/dry.md.unharness doctor [--config PATH] [--digests] [--stack-digests] [--overlap] [--minified] [--claude-version X.Y.Z]prints oneOK,WARN, orFAILline per check and exits 1 on any FAIL;--claude-versionreplaces the detected claude version in its switch lines.unharness switchesprints the strip table from the switch registry.unharness launch [--keep-claude-md] [--keep-web-search] [--no-hooks] [--claude-version X.Y.Z] [PROMPT] [-- LAUNCHER [ARGS...]]caches the prompt and runs the launcher, or prints the command when none follows--.
launch runs LAUNCHER ARGS... --version, directly for a program on PATH and through $SHELL -ic otherwise, and claude --version when no launcher follows --. It passes the switches verified at the detected version when the registry holds it, else at the nearest registry version below it, else at the oldest registry version, and writes unharness: claude <D> is not in the switch registry; using switches verified at <C> on stderr. A launcher that times out, fails to start, or prints no version gets the newest registry version and unharness: <launcher> --version printed no version; using switches verified at <newest> on stderr. --claude-version X.Y.Z states the version and runs nothing.
The config schema is in plugin/SCHEMA.md. The strip table and the text that stays are in the Unharness section of plugin/README.md.
Test with uv run --project plugin/unharness pytest -q from the repository root.
1 maintainer
Metadata
1 maintainer
Release files for unharness 3.7.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 | |
|---|---|---|---|---|
| unharness-3.7.1.tar.gz | 23.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| unharness-3.7.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.6 kB
Release files / unharness-3.7.1.tar.gz
| Download URL | unharness-3.7.1.tar.gz |
|---|---|
| Size | 23.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c5ffabac6cc78e2af9b0e59a638c4065c5eb063d9b4d377b98251a75e9bf79ce
|
|
BLAKE2b-256 checksum How to use checksums |
e5084a600484cef5c5767692623e2a12482cd096864e2215b5a7e0cf5b7e3179
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / unharness-3.7.1-py3-none-any.whl
| Download URL | unharness-3.7.1-py3-none-any.whl |
|---|---|
| Size | 28.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
39db97298f9b0f279e9d91cf3cf4ec91881b8d3852407b13b3c15b9b1a8d2b93
|
|
BLAKE2b-256 checksum How to use checksums |
2b9ff6e152ddfea91377212192fa6d2ccbc04af6c6a9a5b9f0cc3f4b454ea4c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for unharness 3.7.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.
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.
