Repository navigation
Description
Bug Description
PS C:\Users\c00522789> hermes update --force
⚕ Updating Hermes Agent...
→ Fetching updates...
→ Found 6 new commit(s)
✓ Pre-update snapshot: 20260530-024829-pre-update
→ Pulling updates...
✓ Cleared 72 stale pycache directories
→ Updating Python dependencies...
Using Python 3.11.4 environment at: venv
Resolved 103 packages in 3.44s
Built hermes-agent @ file:///C:/Users/c00522789/AppData/Local/hermes/hermes-agent
Prepared 1 package in 25.63s
… still installing dependencies (30s elapsed) — compiling Rust/C extensions can take several minutes
Uninstalled 2 packages in 269ms
Installed 2 packages in 267ms
- aiohttp==3.13.4
- aiohttp==3.13.3
~ hermes-agent==0.15.1 (from file:///C:/Users/c00522789/AppData/Local/hermes/hermes-agent)
→ Refreshing 10 active lazy backend(s)...
↑ 1 refreshed: platform.slack
✓ 9 already current
→ Updating Node.js dependencies...
hermes-agent@1.0.0 postinstall
echo '✅ Browser tools ready. Run: python run_agent.py --help'
'✅ Browser tools ready. Run: python run_agent.py --help'
added 1 package in 5s
✓ repo root
npm warn deprecated @babel/plugin-proposal-private-methods@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.
added 403 packages in 23s
✓ ui-tui
→ Core update complete. Building dashboard (optional)...
→ Building web UI...
During the execution of hermes update, the step "Building web UI..." remains stuck in a processing state, with no task response.
Steps to Reproduce
1.hermes update
Expected Behavior
hermes update success
Actual Behavior
hermes update no task response
Affected Component
Setup / Installation
Messaging Platform (if gateway-related)
No response
Debug Report
2026-05-30 10:32:54,932 INFO gateway.memory_monitor: [MEMORY] baseline rss=88MB gc=(417, 2, 2) threads=1 uptime=0s
2026-05-30 10:32:54,941 INFO gateway.memory_monitor: [MEMORY] Periodic memory monitoring started (interval: 300s)
2026-05-30 10:32:56,964 INFO gateway.run: Starting Hermes Gateway...
2026-05-30 10:32:56,968 INFO gateway.run: Session storage: C:\Users\c00522789\AppData\Local\hermes\sessions
2026-05-30 10:32:56,979 INFO gateway.run: Agent budget: max_iterations=90 (agent.max_turns from config.yaml, or HERMES_MAX_ITERATIONS from .env, or default 90)
2026-05-30 10:32:56,982 INFO gateway.run: Secret redaction: ENABLED (tool output, logs, and chat responses are scrubbed before delivery)
2026-05-30 10:32:57,029 WARNING gateway.run: No user allowlists configured. All unauthorized users will be denied. Set GATEWAY_ALLOW_ALL_USERS=true in ~/.hermes/.env to allow open access, or configure platform allowlists (e.g., TELEGRAM_ALLOWED_USERS=your_id).
2026-05-30 10:32:57,077 WARNING gateway.run: No messaging platforms enabled.
2026-05-30 10:32:57,082 INFO gateway.run: Gateway will continue running for cron job execution.
2026-05-30 10:32:57,113 INFO gateway.run: Channel directory built: 0 target(s)
2026-05-30 10:32:57,117 INFO gateway.run: Press Ctrl+C to stop
2026-05-30 10:32:57,238 INFO gateway.run: Cron ticker started (interval=60s)
2026-05-30 10:33:02,173 INFO gateway.run: kanban dispatcher: embedded in gateway (interval=10.0s)Operating System
Windows 11
Python Version
3.11.4
Hermes Version
0.15.1
Additional Logs / Traceback (optional)
Root Cause Analysis (optional)
No response
Proposed Fix (optional)
No response
Are you willing to submit a PR for this?
- I'd like to fix this myself and submit a PR
Activity
chenwenkai070-cyber commentedon May 30, 2026
The issue has been resolved because the npm proxy settings caused a prolonged build process. This can be optimized later by printing out the specific npm build logs.