Standalone computer-use plugin
Find a file
San Mononoke 053c28b11e feat: initial release of hermes-computer-use standalone plugin
Extracted from hermes-agent branch feature/computer-use-read-consent-2026-09.
Per J7 directive 2026-09-09 (cross-pack modularity), any AI agent can
pip install this and use the same once-per-Hermes-conversation
observation-consent gate.

Original jigo CERTIFIED_WITH_CONDITIONS: t_6c5ac213 + t_7f48a44b.

Co-authored-by: San Mononoke <san@mononoke.local>
2026-09-09 17:54:50 -04:00
src/hermes_computer_use feat: initial release of hermes-computer-use standalone plugin 2026-09-09 17:54:50 -04:00
tests feat: initial release of hermes-computer-use standalone plugin 2026-09-09 17:54:50 -04:00
.gitignore feat: initial release of hermes-computer-use standalone plugin 2026-09-09 17:54:50 -04:00
LICENSE feat: initial release of hermes-computer-use standalone plugin 2026-09-09 17:54:50 -04:00
pyproject.toml feat: initial release of hermes-computer-use standalone plugin 2026-09-09 17:54:50 -04:00
README.md feat: initial release of hermes-computer-use standalone plugin 2026-09-09 17:54:50 -04:00

hermes-computer-use

Session-scoped read-consent gate for the computer_use desktop-control surface.

Standalone Python plugin extracted from hermes-agent on 2026-09-09 per J7 directive (cross-pack modularity). Any AI agent (OMP, Kilo, Codex, Claude, OpenClaw, Toyoko's 5 wolves, or raw Python scripts) can pip install hermes-computer-use and use the same once-per-Hermes-conversation observation-consent gate without depending on hermes-agent.

What it does

computer_use lets an AI agent drive a desktop (click, type, screenshot, etc.). The existing write-approval gate covers mutating actions but not observation-only actions (capture / screenshot). Screenshots can leak off-screen widget values, window titles, focus history, and accessibility metadata from unrelated windows.

read_consent.py adds a session-scoped consent gate that fires once per Hermes conversation (or once per (db_session_id, current_session_key) pair) before any read-only action. After consent, subsequent reads in the same session are silent. YOLO / unrestricted mode covers both namespaces (db_session_id, current_session_key) identically to the upstream write-approval gate.

Install

pip install hermes-computer-use

Use

from hermes_computer_use.read_consent import (
    set_read_consent_callback,
    request_read_consent,
    is_approval_bypass_active_for_session,
    reset_read_consent_for_session,
)

def my_cb(wolf: str, args: dict, session_id: str) -> str:
    return "approve"  # or "deny"

set_read_consent_callback(my_cb)

if not is_approval_bypass_active_for_session("my-wolf", session_id="sess-1"):
    decision = request_read_consent("my-wolf", {"action": "capture"}, session_id="sess-1")
    if decision != "approve":
        return {"error": "read_consent_denied"}

Cross-pack contract

  • Auth model: YOLO/unrestricted-mode covers both namespaces identically to upstream write-approval gates.
  • Fail-open: if no callback is wired, the gate returns approve. Production CLI/gateway paths always wire a callback.
  • Session-key scope: a grant is keyed by (db_session_id, current_session_key). Per-turn identity on messaging platforms (Telegram, Matrix) rotates current_session_key → triggers a re-prompt.

Provenance

Extracted from hermes-agent branch feature/computer-use-read-consent-2026-09 on 2026-09-09. Original jigo CERTIFIED_WITH_CONDITIONS: kanban cards t_6c5ac213 and t_7f48a44b (August 2026).

License

Apache-2.0