Skip to main content

Hugpy Harness — Wrapper arm

hugpy-harness is the headless control center for one Hugpy Wrapper. It discovers the installed Wrapper endpoint automatically and keeps the Wrapper role even when Core is present. hugpy-fleet is the separate Core arm. Both reuse hugpy-terminal; neither requires the other arm.

Headless use

hugpy-harness endpoint
hugpy-harness status
hugpy-harness models
hugpy-harness schema
hugpy-harness settings
hugpy-harness settings --model MODEL
hugpy-harness settings --model MODEL --set '{"ctx":8192}'

Commands return JSON. An optional --base URL changes the service address, not the arm's identity. No endpoint selection prompt or environment variable is needed for a locally installed Wrapper. An unavailable Wrapper is reported; the command never selects Core as a fallback.

from hugpy_harness import Harness
host = Harness()
print(host.settings())
# host.settings(model='MODEL', changes={'ctx': 8192})

Writes use the shared Wrapper validation/readback contract. A mismatch is an unconfirmed command, never a reason to replay it. Wrapper owns execution and its database. Settings readbacks describe saved settings, separately from active loaded-engine configuration.

Interactive and session clients

hugpy-harness tui, hugpy-harness chat, hugpy-harness sessions and hugpy-harness serve host the shared terminal/session runtime in Wrapper mode. hugpy-chat remains a Wrapper-bound compatibility command. Fleet mode uses hugpy-fleet and hugpy-fleet-chat. Fleet journals use .hugpy_fleet/chat; legacy Wrapper journals remain .hugpy_wrapper/chat. Existing histories are preserved. An explicit journal may be reused, but cross-arm destinations are rejected instead of silently switching roles.

Existing hugpy_harness.* library imports used by Agent remain compatibility exports of hugpy-terminal. The Agent runtime is not renamed or removed.

Build and install

installers/debian/build.sh OUTPUT builds an offline standalone .deb using the staged Terminal, Settings, Tools and Toolserver wheels. Install the explicit artifact with sudo dpkg -i hugpy-harness_0.1.27_all.deb.

Fleet terminal compatibility release — 2026-10-22

Includes the interactive GPU Workers console, multi-select + Model allocation table, opaque popup rendering, and the resource Wrapper selector. Auto-route is checked by default and sends general fleet calls; unchecking it restricts routing to the highlighted Worker batch. Selection and mode persist per session. Explicit Wrapper selection targets that Wrapper.

Metadata

Release files for hugpy-harness 0.1.22

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

Source distribution (sdist)

Source distribution for hugpy-harness 0.1.22
File Size Uploaded Provenance
hugpy_harness-0.1.22.tar.gz 40.7 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for hugpy-harness 0.1.22
File Interpreter ABI Platform
hugpy_harness-0.1.22-py3-none-any.whl Python 3 none any Details

Total release size: 68.7 kB

Release files / hugpy_harness-0.1.22.tar.gz

Download URL hugpy_harness-0.1.22.tar.gz
Size 40.7 kB
Tags Source
SHA-256 checksum
How to use checksums
274bd3ca8a3c6c76cecd4ee70b900fe8bd169b7933ac422e20a45a011007a538
BLAKE2b-256 checksum
How to use checksums
2187e4b10cae11a2f05e2b3479b38eb4b2e503ca6d226ce5736951ca203fe0cc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Release files / hugpy_harness-0.1.22-py3-none-any.whl

Download URL hugpy_harness-0.1.22-py3-none-any.whl
Size 27.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c2e093f3b73b5acd31ff8f89ac4b07413634922e07440eacc7a9fc340442717f
BLAKE2b-256 checksum
How to use checksums
31619994ec54f7524c91a3598392a11a4bb77998c3f133cbb0e88307f5fcfaef
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Security for hugpy-harness 0.1.22

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

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

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page