mirror of https://github.com/NousResearch/hermes-agent.git synced 2026-04-30 01:41:43 +00:00

History

ethernet 9fc9c15b4a Some checks are pending Deploy Site / deploy-vercel (push) Waiting to run Details Deploy Site / deploy-docs (push) Waiting to run Details Docker Build and Publish / build-and-push (push) Waiting to run Details Nix Lockfile Fix / auto-fix-main (push) Waiting to run Details Nix Lockfile Fix / fix (push) Waiting to run Details Nix / nix (macos-latest) (push) Waiting to run Details Nix / nix (ubuntu-latest) (push) Waiting to run Details Tests / test (push) Waiting to run Details Tests / e2e (push) Waiting to run Details fix(banner): show correct update status on nix-built hermes (#17550 ) check_for_updates() looked at __file__.parent.parent for a .git dir to diff against origin/main. A nix-built hermes lives in /nix/store with no .git there, so the check fell through to whatever editable-install dev checkout last populated ~/.hermes/.update_check, producing stale "X commits behind" warnings right after a fresh `nix run --refresh`. Embed the locked flake rev into the wrapper as HERMES_REVISION (only on clean builds — dirty refs don't represent any upstream commit). When set, banner.py compares it to upstream main via `git ls-remote` instead of inspecting a local checkout, and the cache key includes the rev so nix updates invalidate immediately. Without local history we can't count commits, so the message is a plain "update available" with no suggested command — nix users may install via `nix run`, profile, system flake, or home-manager, and we don't know which. Also bump web/package-lock.json npmDepsHash via `nix run .#fix-lockfiles`.		2026-04-30 07:03:00 +05:30
..
public	feat(web): add /api/pty WebSocket bridge to embed TUI in dashboard	2026-04-24 10:51:49 -04:00
src	feat: add spinner, lowercase version	2026-04-28 13:59:33 -04:00
eslint.config.js	feat: web UI dashboard for managing Hermes Agent (#8756 )	2026-04-12 22:26:28 -07:00
index.html	fix: use grid/cell components	2026-04-19 15:21:57 -04:00
package-lock.json	fix(banner): show correct update status on nix-built hermes (#17550 )	2026-04-30 07:03:00 +05:30
package.json	feat: add spinner, lowercase version	2026-04-28 13:59:33 -04:00
README.md	feat: web UI dashboard for managing Hermes Agent (#8756 )	2026-04-12 22:26:28 -07:00
tsconfig.app.json	feat: web UI dashboard for managing Hermes Agent (#8756 )	2026-04-12 22:26:28 -07:00
tsconfig.json	feat: web UI dashboard for managing Hermes Agent (#8756 )	2026-04-12 22:26:28 -07:00
tsconfig.node.json	feat: web UI dashboard for managing Hermes Agent (#8756 )	2026-04-12 22:26:28 -07:00
vite.config.ts	fix: update design language	2026-04-28 10:57:30 -04:00

README.md

Hermes Agent — Web UI

Browser-based dashboard for managing Hermes Agent configuration, API keys, and monitoring active sessions.

Stack

Vite + React 19 + TypeScript
Tailwind CSS v4 with custom dark theme
shadcn/ui-style components (hand-rolled, no CLI dependency)

Development

# Start the backend API server
cd ../
python -m hermes_cli.main web --no-open

# In another terminal, start the Vite dev server (with HMR + API proxy)
cd web/
npm run dev

The Vite dev server proxies /api requests to http://127.0.0.1:9119 (the FastAPI backend).

Build

npm run build

This outputs to ../hermes_cli/web_dist/, which the FastAPI server serves as a static SPA. The built assets are included in the Python package via pyproject.toml package-data.

Structure

src/
├── components/ui/   # Reusable UI primitives (Card, Badge, Button, Input, etc.)
├── lib/
│   ├── api.ts       # API client — typed fetch wrappers for all backend endpoints
│   └── utils.ts     # cn() helper for Tailwind class merging
├── pages/
│   ├── StatusPage   # Agent status, active/recent sessions
│   ├── ConfigPage   # Dynamic config editor (reads schema from backend)
│   └── EnvPage      # API key management with save/clear
├── App.tsx          # Main layout and navigation
├── main.tsx         # React entry point
└── index.css        # Tailwind imports and theme variables