Hermes HUD Web UI

The README states the server is local-only by default, rejects cross-site requests and non-loopback access, and requires explicit --unsafe-allow-remote plus --allowed-origin for remote binding, which is a sound least-privilege and external-effects default (least_privilege=2, external_effects=2). The Update hermes action is deliberately two-click, and remote publishing is off by default and only triggered manually, supporting user confirmation (user_confirmation=2). Replay exports default to Safe Share Mode, redacting raw tool arguments, terminal output, reasoning, token-like values, emails, and local paths, and the README clarifies signatures prove local integrity only, giving real data-flow transparency and sensitive-data handling (data_flow_transparency=2, sensitive_data_handling=2). Dependencies are mainstream (fastapi, uvicorn, pyyaml, watchfiles, pillow, cryptography), and CI runs npm audit --audit-level=high and CodeQL, but there is no pip-audit or lockfile on the Python side, so dependency_security=2 rather than 3. Rollback is only implied by last-run logs/status for Update hermes; no version pinning, backup, or restore path is described, so rollback=1. Source attribution is limited to README and pyproject pointing at the same repo and author, with no upstream Hermes version pin or third-party provenance, so source_attribution=1. No malware, credential theft, covert exfiltration, or destructive defaults were found.

README and pyproject agree on Python 3.11+, Node 22.12+, port 3001, and the hermes-hudui CLI entry point; CI covers 3.11/3.12/3.13 and smoke-tests the wheel, so self-consistency is good (self_consistency=2). Dependencies are public PyPI packages installed via pip and npm ci, so availability is predictable (dependency_availability=2). However, apart from the Health tab's schema-drift checks, there is no concrete error text or recovery guidance for missing Hermes, empty data directories, or WebSocket disconnects, so failure_messages=1.

The README clearly targets Hermes users and documents 19 tabs, themes, shortcuts, English/Chinese support, and macOS/Linux/WSL platforms, making audience and scenarios clear (audience_and_scenarios=2). Capability boundaries are stated: it only reads ~/.hermes/ and the hermes CLI, remote exposure requires adding auth and TLS, and Replay signatures are not third-party attestation (capability_boundaries=2). Trigger precision is weak: only tabs and shortcuts are described, with no criteria for when to use the HUD versus the TUI or CLI, so trigger_precision=1. Environment fit is good: HERMES_HUD_FORCE_POLLING=1 covers NFS/WSL1/VM shares, and schema v16/v23/v26 compatibility is declared (environment_fit=2).

The README is well structured with Quick Start, feature sections, Replay, language, themes, shortcuts, TUI relationship, and platform support, giving solid information architecture (information_architecture=2). Install steps are concrete, including git clone, install.sh, venv activation, and the zsh quoting caveat (install_notes=2). Package, CLI, and data-directory naming are consistent (naming_stability=2). Examples are limited to screenshots and one redacted replay JSON, with no FAQ or troubleshooting (examples_and_faq=1). Known limitations are only mentioned in passing (schema drift, polling fallback) rather than consolidated (known_limitations=1). The LICENSE is full MIT text and pyproject declares license=MIT, so license=3. Version 0.12.0 exists but there is no CHANGELOG or release history (versioning_changelog=1). Maintenance responsibility points only to the author and an Issues link, with no governance or support commitment, and the publisher is unverified (maintenance_responsibility=1).

The output is a browser dashboard with an executive summary, cost, model analytics, and Replay exports (JSON/Markdown/HTML/PNG) that can be shared or attached to issues, so output usability is good (output_usability=2). Compared with the TUI it adds Memory, Skills, Sessions, Replay, Health, Providers, Gateway, Model, and Plugins tabs plus a command palette, giving clear marginal value (marginal_value=2). However, it requires a running Hermes agent, Node 22.12+, and Python 3.11+ with data in ~/.hermes/, and no performance or resource data is given, so cost_benefit=1.

The README claims 'Verified against Hermes Agent v0.20.3 (state.db schema v26)', but no verification script, test output, or version pin in the repository traces that claim (claim_traceability=1). CI configuration and test files exist and partially corroborate the test process, but there is no independent third-party source or run result backing the functional claims (cross_source_corroboration=1). The README mixes factual statements with inferential or promotional phrasing (e.g., 'same soul', 'popular') without separating verified facts from marketing language (fact_inference_separation=1).