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())

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, and history_migrate. 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.

Metadata

Release files for oneharness-sdk 0.11.4

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

Source distribution (sdist)

Source distribution for oneharness-sdk 0.11.4
File	Size	Uploaded
oneharness_sdk-0.11.4.tar.gz	97.1 kB	Sep 8, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for oneharness-sdk 0.11.4
File	Interpreter	ABI	Platform	Reset
oneharness_sdk-0.11.4-py3-none-any.whl 99.1 kB Sep 8, 2026	Python 3	none	any	Details

Total release size: 196.3 kB

Release files / oneharness_sdk-0.11.4.tar.gz

Download URL	oneharness_sdk-0.11.4.tar.gz
Size	97.1 kB
Tags	Source
SHA-256 checksum How to use checksums	`c53b778e9c04c6fa589e35678f00307667212b6a3a75bc092cb607ec9a51c22f`
BLAKE2b-256 checksum How to use checksums	`0aa31ed07ef1c6420a6cc8ec13d2be4e71fd2058202a9ea11177e09519a5b67b`
Upload date	Sep 8, 2026
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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/nickderobertis/oneharness
Publishing commit: github.com/nickderobertis/oneharness/tree/dbdb26a438e610bc79d8c8a32c08ae5c237badd0

Workflow

Publishing configuration: github.com/nickderobertis/oneharness/blob/dbdb26a438e610bc79d8c8a32c08ae5c237badd0/.github/workflows/release.yml
Publishing logs: github.com/nickderobertis/oneharness/actions/runs/34188305410/attempts/1

Artifact

Subject: oneharness_sdk-0.11.4.tar.gz
SHA-256 checksum: c53b778e9c04c6fa589e35678f00307667212b6a3a75bc092cb607ec9a51c22f Verifying attestations

Release files / oneharness_sdk-0.11.4-py3-none-any.whl

Download URL	oneharness_sdk-0.11.4-py3-none-any.whl
Size	99.1 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`dac39a6be50ec2ec5127c1563269af2a1588bc85d5f454916b70c9a3e8675c1c`
BLAKE2b-256 checksum How to use checksums	`92cefe473d8fd5408e20d55b0730b0c883be464bd217d5cbfb68229cc4f06ae6`
Upload date	Sep 8, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/nickderobertis/oneharness
Publishing commit: github.com/nickderobertis/oneharness/tree/dbdb26a438e610bc79d8c8a32c08ae5c237badd0

Workflow

Publishing configuration: github.com/nickderobertis/oneharness/blob/dbdb26a438e610bc79d8c8a32c08ae5c237badd0/.github/workflows/release.yml
Publishing logs: github.com/nickderobertis/oneharness/actions/runs/34188305410/attempts/1

Artifact

Subject: oneharness_sdk-0.11.4-py3-none-any.whl
SHA-256 checksum: dac39a6be50ec2ec5127c1563269af2a1588bc85d5f454916b70c9a3e8675c1c Verifying attestations