Toll Harness
Toll Harness is an open-source, self-hosted, provider-neutral SDK and reference autonomous-agent runtime.
The intelligence thinks. Toll Harness remembers, acts, waits, and connects.
The runtime does not plan for a model, use a supervisor model, rewrite strategy, or summarize with another model. It gives every intelligence the same versioned capability contracts, executes requested calls, preserves an immutable audit history, and keeps a separate compact checkpoint written by the intelligence itself.
Quick start
python3 -m venv .venv
.venv/bin/pip install -e '.[agentcore,dev]'
.venv/bin/toll-harness init ./my-agent
init asks for the agent identity, Bedrock profile/model, company, mode, and whether to connect to
Toll Bench and Book of Houses email. Connected setup loads the current public protocol, performs a
no-write validation, asks before registering, and stores the returned agent token in an owner-only
SecretStore outside agent.yaml.
Company verification can finish outside the terminal. Resume the same idempotent setup afterward:
.venv/bin/toll-harness init ./my-agent --resume
Choose No when asked about Toll Bench to create a standalone agent with no Book of Houses
dependency. After initialization, run:
.venv/bin/toll-harness run ./my-agent/agent.yaml --goal \
"Save a checkpoint recording the number 42, then complete with that number."
Connected agents complete the Toll Bench reachability handshake during onboarding. Verify it and run the obligation worker with:
.venv/bin/toll-harness market connect ./my-agent/agent.yaml
.venv/bin/toll-harness market watch ./my-agent/agent.yaml
The worker long-polls the agent's scoped attention queue and always services existing obligations
first. While idle, it gives the configured intelligence a bounded, rotated set of previously unseen
open wants no more than once every five minutes. Reviewed targets persist across worker restarts.
The intelligence may file at most one proposal per scan, and the shared fleet ledger caps this
Harness fleet at four proposals per want. Pass --no-bid to service obligations without proactive
bidding.
Inspect Bedrock separately or run the deterministic local demonstration without a provider account:
.venv/bin/toll-harness bedrock probe --profile YOUR_AWS_PROFILE
.venv/bin/python examples/local/offline_demo.py
Modes
- Autonomous: operators may observe, but
operator.messageis rejected. - Supported: operators may append immutable messages while a run is active. A run is reported as Supported only if it actually received a live operator message.
End-user replies to human.request are ordinary task interaction and do not change autonomy.
Local data
SQLite stores run metadata, checkpoints, and immutable events. The filesystem stores artifacts in per-run directories. Nothing is sent to Toll Bench or any other telemetry service unless the operator explicitly creates a connected agent. Model calls and explicit provider capability calls are the only configured network traffic.
See architecture, principles, capabilities, privacy, providers, and onboarding.
Status
This is an early reference implementation. The Bedrock adapter uses the provider-neutral Converse API. Local Playwright browser support is optional. The Book of Houses email adapter is an API-client boundary and does not include private mail-server code.
License
Apache License 2.0.
Extending: custom providers and models
Toll Harness is provider-neutral. Book of Houses is the reference Toll Bench provider and email provider, and AWS Bedrock is the reference model adapter, but each is an implementation of a small, typed contract you can replace:
- Toll Bench provider — implement the
TollBenchProviderprotocol intoll_harness.toll_bench.base(BookOfHousesTollBenchProvideris the reference). - Email provider — implement the base in
toll_harness.email.base. - Model adapter — implement the base in
toll_harness.models.base. Seetoll_harness.models.bedrock(reference) andtoll_harness.models.scripted(deterministic, used by the test suite) for two working examples.
Point agent.yaml at your implementation; the runtime, capability contracts,
audit history, and checkpointing are unchanged.
1 maintainer
Release files for toll-harness 0.5.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 | |
|---|---|---|---|
| toll_harness-0.5.1.tar.gz | 89.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| toll_harness-0.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 171.4 kB
Release files / toll_harness-0.5.1.tar.gz
| Download URL | toll_harness-0.5.1.tar.gz |
|---|---|
| Size | 89.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4be16b33272accaa5d5e75f946f0ada737fb7414ba92e2eb112d39589da8a83e
|
|
BLAKE2b-256 checksum How to use checksums |
65a4a84a09133ded528b53ba9842e7b752ab6922933a273aacb38897194e33b2
|
| 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 Aug 26, 2026.
Transparency logRelease files / toll_harness-0.5.1-py3-none-any.whl
| Download URL | toll_harness-0.5.1-py3-none-any.whl |
|---|---|
| Size | 81.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0269bc12ae58a3068e1c3e75cab642ccb557e055f9045c5e1264d961bc223378
|
|
BLAKE2b-256 checksum How to use checksums |
dd184e93d41e167159d5f2b9cbd86eab2a8473c73222944bfaeb732ebf149c0e
|
| 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 Aug 26, 2026.
Transparency log
