oneharness-sdk
Async Python access to the oneharness engine, generated from and validated against the Rust-owned JSON Schema contracts. The distribution is oneharness-sdk, the import is oneharness_sdk, and every release depends on the exact same oneharness-cli version.
pip install oneharness-sdk
import asyncio
from oneharness_sdk import OneHarness
async def main() -> None:
oneharness = OneHarness()
report = await oneharness.run(
{"prompt": "Summarize this repository", "harnesses": ["codex"]}
)
print(report["results"][0]["text"])
asyncio.run(main())
Every JSON-returning method passes --format json --compact itself, so the CLI's own default (a human-readable text view) never reaches the SDK. A run over several harnesses is a fallback chain by default — the first candidate that can run does, and the report's fallback block says which; pass "run_mode": "parallel" to run them all at once.
The client covers every verb the CLI exposes, so nothing needs a hand-built command line: run, run_mock, run_stream, list, detect, config, sync, init, usage, gate, mock, interrupt, history, history_list, history_watch, history_clear, history_migrate, history_reindex, and history_pointers. That coverage is gated, not asserted here. run_mock uses the deterministic responder shipped in the CLI; see Testing patterns. run_stream and history_watch are async iterators. Every envelope is validated before it is yielded; closing or cancelling an iterator terminates its subprocess.
An option whose name is a Python keyword takes the conventional trailing underscore — sync({"global_": True}) sends --global — and nothing else about the spelling changes.
async for envelope in oneharness.run_stream(
{"prompt": "Inspect this repository", "harnesses": ["codex"]}
):
if envelope["type"] == "event" and envelope["event"]["name"] == "shell":
break
async for envelope in oneharness.history_watch(
{"labels": {"graph": "release"}, "after": last_history_id}
):
print(envelope["record"]["history_id"])
Python input keys are snake case and strict: unknown fields and misspellings fail before the CLI starts. Output dictionaries preserve additive fields from newer compatible CLI versions. history and history_watch raise HistoryNotFoundError when a session, record, or cursor cannot be resolved.
1 maintainer
Metadata
1 maintainer
Release files for oneharness-sdk 0.25.10
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 | |
|---|---|---|---|---|
| oneharness_sdk-0.25.10.tar.gz | 118.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| oneharness_sdk-0.25.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 238.7 kB
Release files / oneharness_sdk-0.25.10.tar.gz
| Download URL | oneharness_sdk-0.25.10.tar.gz |
|---|---|
| Size | 118.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8e5c99a9d80bb17887ebdd49d1e3617812e41fff8a2f5b43e12bd2ca866710a1
|
|
BLAKE2b-256 checksum How to use checksums |
e8bc0454d28e40d1defa513fb875f48af72cb39edfc0a1da8da6a5052a8b7428
|
| 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 Oct 21, 2026.
Transparency logRelease files / oneharness_sdk-0.25.10-py3-none-any.whl
| Download URL | oneharness_sdk-0.25.10-py3-none-any.whl |
|---|---|
| Size | 120.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34e40a204091946c5abda44a15c04131912ce7e6219f6ce6a643e15060cba1e7
|
|
BLAKE2b-256 checksum How to use checksums |
fba01b1711bdfc78c0d6fbf41a3c164c6f8d63c3c309f9bb239bf1f75a2ea0bf
|
| 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 Oct 21, 2026.
Transparency logSecurity for oneharness-sdk 0.25.10
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 oneharness_sdk-0.25.10.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 21, 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.
