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.
The former hugpy_harness.* compatibility exports are removed;
library consumers import the shared implementation from hugpy_terminal.*
directly. This package keeps only hugpy_harness.control (Harness /
WrapperControls) and the Wrapper-arm CLI entry points.
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.25
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.25.tar.gz | 34.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hugpy_harness-0.1.25-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.2 kB
Release files / hugpy_harness-0.1.25.tar.gz
| Download URL | hugpy_harness-0.1.25.tar.gz |
|---|---|
| Size | 34.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e9f8bd6e9e551138390614b5267dd372b74accae4f02edae77d401a42dfe147d
|
|
BLAKE2b-256 checksum How to use checksums |
77b3ade4194d7a07c895ebfd6d4093f2450a7eccf905385536eb83a39f0947a8
|
| 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.25-py3-none-any.whl
| Download URL | hugpy_harness-0.1.25-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fb4ad33c39f5ec42330e15d643bf20e53629faeb45aacb14da25ba9b366349aa
|
|
BLAKE2b-256 checksum How to use checksums |
3ee3fb7cb99aa4e5aa9984e17a988b47902346eb954627ca46b5babd9f484c0d
|
| 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.25
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
