hugpy-harness 0.1.3__tar.gz

hugpy_harness-0.1.3/PKG-INFO

@@ -0,0 +1,114 @@
+Metadata-Version: 2.4
+Name: hugpy-harness
+Version: 0.1.3
+Summary: Optional standalone terminal chat and agent harness for a Hugpy wrapper or fleet
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Requires-Dist: hugpy-tools>=0.2.7
+
+# Hugpy Harness
+
+Connect to either a standalone wrapper or a basic Core fleet endpoint with
+`hugpy-harness --base http://host:port`. The harness displays fleet resource
+snapshots per worker, including stale/offline state. Conversations remain in the
+same local workspace journal when changing endpoints.
+
+Optional standalone terminal interface for a local or remote Hugpy wrapper.
+No dependency on hugpy-agent or the hugpy-wrapper Python package. Communication
+uses HTTP; no background service, engine installation or worker enrollment.
+
+## Install
+
+Build with `bash packaging/debian/build.sh`. The output directory contains the
+harness `.deb`, a separate wrapper `.deb` when its local build is available,
+and `install.sh`. Distribute these together for installation without an APT
+repository (system Python packages must still be available).
+
+```sh
+cd build/debian
+./install.sh                         # missing local wrapper: prompt [Y/n]
+./install.sh --yes                   # default yes without prompts
+./install.sh --without-wrapper       # harness only, e.g. remote wrapper
+./install.sh --dry-run               # show APT plan without changing packages
+```
+
+A compatible installed wrapper is reused. The installer checks all required
+local package files before calling APT. Noninteractive default is yes; use
+`--without-wrapper` explicitly for a remote-only client.
+
+The `.deb` declares the wrapper as `Recommends`, so standard APT installations
+include it by default when a repository provides it. It is optional, not a
+hard dependency. For the current local release use `install.sh`, which passes
+the separate wrapper package to APT when needed. Alternatively:
+
+```sh
+sudo apt install ./hugpy-wrapper_0.1.62_all.deb ./hugpy-harness_0.1.1_all.deb
+sudo apt install --no-install-recommends ./hugpy-harness_0.1.1_all.deb
+```
+
+The harness runtime is `/opt/hugpy-harness/venv`; the wrapper retains its own
+runtime and service. Neither package embeds the other. Installing the wrapper
+alone does not install the harness.
+
+## Launch
+
+```sh
+hugpy-harness
+hugpy-harness launch --workspace /path/to/project
+hugpy-harness --base http://HOST:PORT --workspace /path/to/project
+hugpy-harness chat --model MODEL_ID
+```
+
+A local endpoint is discovered from the wrapper endpoint file. Remote access
+uses `--base` and `HUGPY_WRAPPER_API_KEY` when authentication is required.
+`hugpy-chat` is an alias for the plain chat interface. `/model` opens the model
+picker; `/resources` toggles telemetry and `/resources full` opens the monitor.
+
+Existing sessions remain in each workspace's `.hugpy_wrapper/chat` directory
+for compatibility. Reopen using the same `--workspace` and `/session`.
+Removal (`sudo apt remove hugpy-harness`) leaves chat history, the wrapper,
+models, and original Hugpy Agent untouched. Purge removes only this package's
+runtime, not workspace data. The wrapper never installs this optional package.
+
+Chat accepts plain replies; tools are optional when the request needs them.
+Each user message has its own bounded agent loop. Empty answers and engine
+errors are reported without demanding a tool call.
+
+## Model tools
+
+The harness imports the standalone `hugpy_tools` catalog. Core file, search,
+text, data, hash, time, and web tools are available automatically in both the
+full-screen interface and plain chat. Schemas reach models through prompted
+tool instructions or native function calling, and results feed back into the
+conversation through the existing journaled loop.
+
+Existing `fs_read`, `fs_write`, `fs_glob`, and `shell` calls remain supported.
+The harness keeps its workspace-relative `fs_glob(pattern)` contract when the
+portable catalog contains the same name. File arguments are resolved inside
+`--workspace`; writes, network requests, and host operations use `--policy`
+(`ask` by default). Tools execute on the harness machine, even when the model
+runs on a remote wrapper or fleet.
+
+```sh
+hugpy-harness --workspace /path/to/project
+hugpy-harness chat --workspace /path/to/project --policy readonly
+# Add optional document, media, rendering, image, desktop, and VM tools:
+hugpy-harness --workspace /path/to/project --optional-tools
+hugpy-harness chat --workspace /path/to/project --optional-tools
+```
+
+Optional tools load their backends only when called. Install the relevant
+`hugpy-tools` extras in the harness environment, for example
+`pip install 'hugpy-tools[images,files,render]'`; rendering also needs Playwright
+Chromium, and desktop/VM tools need the corresponding host software. Missing
+backends return a tool error to the model. Generated image and screenshot
+outputs default to `.hugpy_wrapper/tool-artifacts` inside the workspace.
+
+Python installations require `hugpy-tools>=0.2.7`. The Debian build bundles
+the core tools wheel alongside the harness wheel and installs both offline.
+Neither mode requires a Toolserver service. Optional backend dependencies are
+not bundled. To install the unreleased workspace versions together:
+
+```sh
+pip install ../hugpy_tools .
+```

hugpy_harness-0.1.3/README.md

@@ -0,0 +1,106 @@
+# Hugpy Harness
+
+Connect to either a standalone wrapper or a basic Core fleet endpoint with
+`hugpy-harness --base http://host:port`. The harness displays fleet resource
+snapshots per worker, including stale/offline state. Conversations remain in the
+same local workspace journal when changing endpoints.
+
+Optional standalone terminal interface for a local or remote Hugpy wrapper.
+No dependency on hugpy-agent or the hugpy-wrapper Python package. Communication
+uses HTTP; no background service, engine installation or worker enrollment.
+
+## Install
+
+Build with `bash packaging/debian/build.sh`. The output directory contains the
+harness `.deb`, a separate wrapper `.deb` when its local build is available,
+and `install.sh`. Distribute these together for installation without an APT
+repository (system Python packages must still be available).
+
+```sh
+cd build/debian
+./install.sh                         # missing local wrapper: prompt [Y/n]
+./install.sh --yes                   # default yes without prompts
+./install.sh --without-wrapper       # harness only, e.g. remote wrapper
+./install.sh --dry-run               # show APT plan without changing packages
+```
+
+A compatible installed wrapper is reused. The installer checks all required
+local package files before calling APT. Noninteractive default is yes; use
+`--without-wrapper` explicitly for a remote-only client.
+
+The `.deb` declares the wrapper as `Recommends`, so standard APT installations
+include it by default when a repository provides it. It is optional, not a
+hard dependency. For the current local release use `install.sh`, which passes
+the separate wrapper package to APT when needed. Alternatively:
+
+```sh
+sudo apt install ./hugpy-wrapper_0.1.62_all.deb ./hugpy-harness_0.1.1_all.deb
+sudo apt install --no-install-recommends ./hugpy-harness_0.1.1_all.deb
+```
+
+The harness runtime is `/opt/hugpy-harness/venv`; the wrapper retains its own
+runtime and service. Neither package embeds the other. Installing the wrapper
+alone does not install the harness.
+
+## Launch
+
+```sh
+hugpy-harness
+hugpy-harness launch --workspace /path/to/project
+hugpy-harness --base http://HOST:PORT --workspace /path/to/project
+hugpy-harness chat --model MODEL_ID
+```
+
+A local endpoint is discovered from the wrapper endpoint file. Remote access
+uses `--base` and `HUGPY_WRAPPER_API_KEY` when authentication is required.
+`hugpy-chat` is an alias for the plain chat interface. `/model` opens the model
+picker; `/resources` toggles telemetry and `/resources full` opens the monitor.
+
+Existing sessions remain in each workspace's `.hugpy_wrapper/chat` directory
+for compatibility. Reopen using the same `--workspace` and `/session`.
+Removal (`sudo apt remove hugpy-harness`) leaves chat history, the wrapper,
+models, and original Hugpy Agent untouched. Purge removes only this package's
+runtime, not workspace data. The wrapper never installs this optional package.
+
+Chat accepts plain replies; tools are optional when the request needs them.
+Each user message has its own bounded agent loop. Empty answers and engine
+errors are reported without demanding a tool call.
+
+## Model tools
+
+The harness imports the standalone `hugpy_tools` catalog. Core file, search,
+text, data, hash, time, and web tools are available automatically in both the
+full-screen interface and plain chat. Schemas reach models through prompted
+tool instructions or native function calling, and results feed back into the
+conversation through the existing journaled loop.
+
+Existing `fs_read`, `fs_write`, `fs_glob`, and `shell` calls remain supported.
+The harness keeps its workspace-relative `fs_glob(pattern)` contract when the
+portable catalog contains the same name. File arguments are resolved inside
+`--workspace`; writes, network requests, and host operations use `--policy`
+(`ask` by default). Tools execute on the harness machine, even when the model
+runs on a remote wrapper or fleet.
+
+```sh
+hugpy-harness --workspace /path/to/project
+hugpy-harness chat --workspace /path/to/project --policy readonly
+# Add optional document, media, rendering, image, desktop, and VM tools:
+hugpy-harness --workspace /path/to/project --optional-tools
+hugpy-harness chat --workspace /path/to/project --optional-tools
+```
+
+Optional tools load their backends only when called. Install the relevant
+`hugpy-tools` extras in the harness environment, for example
+`pip install 'hugpy-tools[images,files,render]'`; rendering also needs Playwright
+Chromium, and desktop/VM tools need the corresponding host software. Missing
+backends return a tool error to the model. Generated image and screenshot
+outputs default to `.hugpy_wrapper/tool-artifacts` inside the workspace.
+
+Python installations require `hugpy-tools>=0.2.7`. The Debian build bundles
+the core tools wheel alongside the harness wheel and installs both offline.
+Neither mode requires a Toolserver service. Optional backend dependencies are
+not bundled. To install the unreleased workspace versions together:
+
+```sh
+pip install ../hugpy_tools .
+```

hugpy_harness-0.1.3/hugpy_harness/LICENSE

@@ -0,0 +1,41 @@
+hugpy — Source-Available License
+
+Copyright (c) 2026 putkoff (hugpy.ai). All rights reserved.
+
+Permission is granted, free of charge, to use this software ("hugpy") for
+personal and non-commercial purposes, and for time-limited commercial
+evaluation, subject to the following conditions:
+
+1. Non-commercial use means use by an individual for personal purposes, or
+   use by a non-profit or educational institution for its own internal
+   purposes. Any use by, for, or on behalf of a for-profit business or in
+   connection with revenue-generating activity is commercial use — including
+   internal business use, use in producing goods or services, and use on
+   paid engagements.
+
+2. Commercial use requires a commercial license from the copyright holder.
+   Exception: a business may evaluate the software internally for up to
+   thirty (30) days free of charge; continued use after that requires a
+   commercial license.
+
+3. Redistribution of this software, in source or binary form, modified or
+   unmodified, is not permitted without prior written permission from the
+   copyright holder. Downloading the software from an official distribution
+   channel (PyPI, npm, hugpy.ai) is not redistribution.
+
+4. Modification for personal use or internal evaluation is permitted;
+   distribution of modified versions is not.
+
+5. This notice must be retained in all copies or substantial portions of
+   the software.
+
+6. Any use outside these terms automatically terminates this license.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY ARISING
+FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
+IN THE SOFTWARE.
+
+For commercial licensing or redistribution permission: https://hugpy.ai

hugpy_harness-0.1.3/hugpy_harness/PROVENANCE.md

@@ -0,0 +1,37 @@
+# Hugpy Agent chat extraction
+
+Source: `/srv/hugpy/app/packages/hugpy_agent`, version 0.1.114.
+The AgentLoop, adapter, gateway, journal, memory, audit and policy code are
+retained. Config is its dataclass without fleet endpoint discovery. Tools use
+the existing filesystem and shell implementations plus final_answer and a
+terminal operator channel. Fleet leases, remote tools, subagents and embedding
+RAG are omitted. State lives in `.hugpy_wrapper/chat` within the workspace.
+The CLI turn sequence is extracted from `hugpy_agent.cli.cmd_chat`.
+Original file SHA-256 values:
+
+```
+loop.py 9cdb541f090367eba65aec54561845cb09e5258249a512aa54c68255999e0934
+gateway.py 5df914e06e2edc3f3a91cbcc7207df5da78abd5e63684d304f39eb9829c15440
+adapter.py 25259f038bfb117e341db7d27d4588a1bbcffe35fd3947ce4f98f5941cfa15a3
+journal.py 3acf8ab60c4d5194207cb05e3a17633bdb21276bbed4938f591c829189b5451f
+memory.py 6e187ce5f2ab653bb4a67fb1d2060f9438a226a67428608c363a07f56a6269d8
+audit.py b58a8f9ada3698f81970cf37d6d90a496987b2251d917f8c278a9858bc2ca466
+policy.py ab4e391739db83dd31b38d1e28b12367ef4c5aad9853bdc708e2230755f17006
+tools/fs.py 810bf6ea730a15412f693e3b5a7773b5cf75e5623c2e54f76cae08a6039858d4
+tools/shell.py 868ae9aeb93bcce25563f5ffd427872c0ede4ae421054e424f4e679b7d6cd54d
+```
+
+Local fixes: conversation mode permits plain chat replies; terminal approvals
+replace remote comms. A final_answer with an unambiguous top-level answer is
+normalized; invalid final answers request repair instead of displaying `{}`.
+
+The `tui/`, `serve_client/`, and `branding.py` sources are also extracted from
+Hugpy Agent 0.1.114. The original curses screens, command menu, model/session
+pickers, tool cards and approval UI are retained. `serve_client/wrapper.py`
+adapts them to the standalone wrapper and local AgentLoop journals. Remote-only
+commands are hidden from the local menu. `hugpy-agent launch` and `tui` both
+open this interface; `chat` remains the plain REPL. No OpenCode launch is used.
+
+Wrapper additions: the resources pane and full resource monitor poll the
+connected wrapper independently of the chat/event loop, displaying telemetry
+freshness, unavailable counters, resident health, and admission queue reasons.

hugpy_harness-0.1.3/hugpy_harness/__init__.py

@@ -0,0 +1 @@
+"""Standalone extraction of Hugpy Agent 0.1.114 chat runtime."""