Spaces:
Sleeping
Sleeping
Commit History
-
fix: pass --insecure to hermes dashboard so it can bind 0.0.0.0 on HF Spaces
Hermes CLI refuses 0.0.0.0 bind by default. HF Spaces is already a sandbox per container, Repository Secrets never reach the browser, and sync_hf.py widens CORS / relaxes iframe headers — so --insecure is the right setting for this deploy environment. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>8d98ed1 -
feat: HuggingClaw-parity — DoH DNS, atomic persistence utils, branding, marketing
- DoH DNS escape hatch: dns-resolve.py (Python, writes /etc/hosts) + dns-fix.cjs (Node dns.lookup preload) — unblocks Telegram/Discord/WhatsApp on HF Spaces - Atomic persistence utilities: hermes_persist.py CLI (save/load/status), save_to_dataset[_atomic].py, restore_from_dataset[_atomic].py — tar.gz snapshots with 5-way rotation + optional checksummed commit ops - sync_hf.py: iframe-embed fix — also relax X-Frame-Options + CSP frame-ancestors so HF Spaces can embed the Hermes dashboard - entrypoint.sh: background DoH resolver + NODE_OPTIONS preload dns-fix.cjs - Dockerfile: copy assets/, chmod new scripts, cache-bust to v2 - Branding: HermesFace.svg, HermesFace-social.svg, assets/architecture.svg, README embeds SVGs, datasets frontmatter, Duplicate-Space warning, Security + Manual backup sections - marketing.md: 6 bilingual Reddit plans (selfhosted / LocalLLaMA / ChatGPT / LLMDevs / artificial / OpenAI) centred on self-improving agent angle - LICENSE (MIT)c22deee
-
rename to HermesFace + professional README + always start gateway
- Rename project from HuggingHermes to HermesFace everywhere - Professional README matching HuggingClaw style: badges, architecture, quick start, data persistence, env vars, messaging platforms - Always start gateway process (fixes "Gateway Not running" in dashboard) - Gateway runs alongside web dashboard for full functionality Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>8377d8e -
fix: dashboard first on 7860, gateway only if messaging tokens set
- Start dashboard (React UI) first to claim port 7860 - Only start gateway when messaging tokens are configured - Remove API_SERVER env vars to prevent gateway port conflict - Fixes 404 on root caused by gateway's API server taking 7860 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>656d2be -
feat: serve Hermes web dashboard on port 7860
- Build React frontend in Dockerfile (npm run build in web/) - Run gateway in background for messaging platforms - Run hermes dashboard on 0.0.0.0:7860 as main process (HF Spaces visible) - Patch web_server.py CORS to allow HF Spaces origins - StatusPage, ConfigPage, EnvPage all accessible from Space Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>9001a75 -
fix: remove health server to avoid port 7860 conflict with API server
The health server was holding port 7860 even after shutdown(), causing Hermes API server to fail with "port already in use". Let Hermes API server bind 7860 directly. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>52d26c8 -
fix: set API_SERVER_KEY for 0.0.0.0 binding + GATEWAY_ALLOW_ALL_USERS
Hermes requires API_SERVER_KEY when binding to 0.0.0.0 (security). Auto-generate a random key if not explicitly set. Also set GATEWAY_ALLOW_ALL_USERS=true for HF Spaces public access. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>f543e28 -
feat: professional README + enable Hermes API server on port 7860
- Full professional README with badges, architecture diagram, quick start, env vars table, API docs, messaging platform guide - Enable Hermes built-in OpenAI-compatible API server on port 7860 (/health, /v1/chat/completions, /v1/models) - Health check server as boot-time placeholder until gateway starts Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>18d0345 -
fix: add HTTP health check server on port 7860 for HF Spaces
HF Spaces requires an HTTP service on app_port to detect the app is running. Hermes gateway is a messaging client without HTTP server, so we add a lightweight status page + JSON API on port 7860. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>e8245d8 -
fix: build from source, replicate HuggingClaw architecture fully
- Dockerfile: build from source (git clone) since no pre-built image exists - Use official Hermes deps: uv, gosu, debian:13.4, playwright - entrypoint.sh: activate venv, bootstrap config, sync skills - sync_hf.py: full persistence with /opt/data, auto-derive dataset repo - .env.example: complete docs matching HuggingClaw format Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>463c7dc -
Initial commit: HuggingHermes — Hermes Agent on HF Spaces
Replicated from HuggingClaw architecture with adaptations for Hermes Agent: - Dockerfile with pre-built ghcr.io/nousresearch/hermes-agent image - HF Dataset persistence for /opt/data (config, skills, memories) - Entrypoint with auto-detection of hermes CLI/gateway/run_agent entry points - Environment config for LLM providers and messaging platforms Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>7bdfe23