Reason Harbor adapter
Run Reason as an agent in Harbor. Harbor starts the task container and grades the result. The adapter installs the published Reason CLI in that container, checks its checksum, and starts it as a worker; the agent runs as a normal Reason Session. Your API key stays on your machine; the container only receives a one-use enrollment ticket.
Install
uv pip install reason-machines-harbor
This installs Harbor 0.22.0. For cloud environments, add the matching Harbor
extra, for example uv pip install "harbor[modal]==0.22.0".
Run
Get a Reason API key with
run, sessions:read, deployment:read, devices:read, devices:write,
devices:use and org:write, and enable the model under
Models.
export REASON_API_KEY="YOUR_REASON_API_KEY"
DOCKER_DEFAULT_PLATFORM=linux/amd64 harbor run \
--dataset datacurve/deep-swe-1-1 --n-tasks 1 \
--agent reasonmachines_harbor:ReasonAgent \
--model openai/gpt-6-luna \
--ak reasoning_effort=xhigh \
--allow-agent-host api.reasonmachines.com \
--allow-agent-host relay.reasonmachines.com \
--env reasonmachines_harbor.environment:ReasonDockerEnvironment
The worker connects out to the Reason API and relay, so both
--allow-agent-host flags are required, even for offline tasks.
Agent kwarg (--ak) |
Default | Meaning |
|---|---|---|
reasoning_effort |
medium |
minimal, low, medium, high, xhigh or max |
mode |
ephemeral |
ephemeral: a new single-use workspace per trial, with memory and skills on. standard: your own workspace |
runtime_profile |
server default | An experimental harness listed by GET /v3/deployment |
Ephemeral mode has to be enabled for your workspace; ask us, or pass
--ak mode=standard.
To run the full benchmarks and reproduce our results, see reason-machines/benchmark.
Source
reason-machines/reason-machines-harbor
is a read-only copy of the adapter in the Reason monorepo, where it is
developed and tested. Releases are tagged vX.Y.Z.
Metadata
Release files for reason-machines-harbor 0.3.9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| reason_machines_harbor-0.3.9.tar.gz | 42.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| reason_machines_harbor-0.3.9-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 80.6 kB
Release files / reason_machines_harbor-0.3.9.tar.gz
| Download URL | reason_machines_harbor-0.3.9.tar.gz |
|---|---|
| Size | 42.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cce576599fa1792d365b35274b257ff3fd687f0de4b35b6a2682714e53eb9485
|
|
BLAKE2b-256 checksum How to use checksums |
8e71c227a228dbf7654b52a8a888202e989a0be0833c34b48f2f4ff6305b2c6b
|
| 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 Oct 5, 2026.
Transparency logRelease files / reason_machines_harbor-0.3.9-py3-none-any.whl
| Download URL | reason_machines_harbor-0.3.9-py3-none-any.whl |
|---|---|
| Size | 38.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
900ad8940622dfe2c0680cfcda931bc08f02c31893e276686a48a49b41eac3eb
|
|
BLAKE2b-256 checksum How to use checksums |
b30ee8340bfcf88ed1df03e0dadacf42b404cf3841d4c679daa73037bb2578d1
|
| 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 Oct 5, 2026.
Transparency log