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.14.0

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.14.0
File	Size	Uploaded
oneharness_sdk-0.14.0.tar.gz	103.0 kB	Sep 18, 2026	Details

Built distribution (wheel)

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

Total release size: 208.5 kB

Release files / oneharness_sdk-0.14.0.tar.gz

Download URL	oneharness_sdk-0.14.0.tar.gz
Size	103.0 kB
Tags	Source
SHA-256 checksum How to use checksums	`fc92bb82afbe3da186745b15fa300eb9c829ea63201286b6f8b7c2e9c6d17906`
BLAKE2b-256 checksum How to use checksums	`5a0e89bb8f625088c4978bd95e80f0938e6f58cdf3bd9236230246845dc2e36f`
Upload date	Sep 18, 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/8bf80da672b4fc747defa54eeb77535913827e15

Workflow

Publishing configuration: github.com/nickderobertis/oneharness/blob/8bf80da672b4fc747defa54eeb77535913827e15/.github/workflows/release.yml
Publishing logs: github.com/nickderobertis/oneharness/actions/runs/35379424086/attempts/1

Artifact

Subject: oneharness_sdk-0.14.0.tar.gz
SHA-256 checksum: fc92bb82afbe3da186745b15fa300eb9c829ea63201286b6f8b7c2e9c6d17906 Verifying attestations

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

Download URL	oneharness_sdk-0.14.0-py3-none-any.whl
Size	105.5 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`b5a761b6e4a08a67ff53aa81fbf113377a9da4dad371f4cfd1143c0ef0f9c19d`
BLAKE2b-256 checksum How to use checksums	`60fac5ff4fad7c1ca4a84cae7d35f4cb903c026ab6525eb7eb2c2e4f07c5c8d7`
Upload date	Sep 18, 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/8bf80da672b4fc747defa54eeb77535913827e15

Workflow

Publishing configuration: github.com/nickderobertis/oneharness/blob/8bf80da672b4fc747defa54eeb77535913827e15/.github/workflows/release.yml
Publishing logs: github.com/nickderobertis/oneharness/actions/runs/35379424086/attempts/1

Artifact

Subject: oneharness_sdk-0.14.0-py3-none-any.whl
SHA-256 checksum: b5a761b6e4a08a67ff53aa81fbf113377a9da4dad371f4cfd1143c0ef0f9c19d Verifying attestations