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.
1 maintainer
Metadata
1 maintainer
Release files for hugpy-harness 0.1.21
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| hugpy_harness-0.1.21.tar.gz | 40.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hugpy_harness-0.1.21-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 67.9 kB
Release files / hugpy_harness-0.1.21.tar.gz
| Download URL | hugpy_harness-0.1.21.tar.gz |
|---|---|
| Size | 40.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d82f702219b75bbea425206559d5a1e4257ed73b4b7cafe17a65311db7cb2dbd
|
|
BLAKE2b-256 checksum How to use checksums |
d7a1825d19dee5b6e6a81266358cdec14247070f5d07a95bf60cd39554d4aeea
|
| 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.21-py3-none-any.whl
| Download URL | hugpy_harness-0.1.21-py3-none-any.whl |
|---|---|
| Size | 27.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a2c89970dcd96d9634c7fc752d883e2df2d5165406bcc6b56811a73142ece464
|
|
BLAKE2b-256 checksum How to use checksums |
91f45f635df0b592614832f62b540a22dc1eca40a18084900c1734801b29c848
|
| 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.21
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.
