Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-opus-5· anthropicHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION Hermes Desktop 0.4.3 remote mode fails against working local Hermes…

  1. User

    ISSUE DESCRIPTION

    Hermes Desktop 0.4.3 remote mode fails against working local Hermes API server

    Bug: Hermes Desktop 0.4.3 fails to connect reliably to existing local Hermes API server

    Summary

    Hermes Desktop 0.4.3 fails to work as a frontend for an already-running local Hermes Agent API server.

    The Hermes Agent backend is installed separately under /opt/hermes-agent, runs correctly with Python 3.12, exposes the API server on 127.0.0.1:8642, and successfully handles OpenAI-compatible API requests via curl.

    However, Hermes Desktop fails to connect or send messages in remote mode. It either reports that it cannot reach the server, returns 404: Not Found, or tries to spawn a removed/incorrect local Hermes installation under ~/.hermes/hermes-agent.

    Environment

    • OS: Ubuntu 24.04.3 LTS
    • Kernel: Linux 6.17.0-14-generic x86_64
    • Desktop: KDE/Plasma
    • Hermes Agent version: 0.14.0
    • Hermes Desktop version: 0.4.3
    • Hermes Agent install path: /opt/hermes-agent
    • Hermes config/home: ~/.hermes
    • Python used by working Hermes Agent: Python 3.12.3
    • GPU: NVIDIA RTX 5060 Ti, 16 GB VRAM
    • Model backend: Ollama
    • Ollama model: gemma4:e4b
    • Ollama API endpoint: http://127.0.0.1:11434/v1
    • Hermes API server: http://127.0.0.1:8642

    Working backend configuration

    Hermes Agent works correctly from CLI/API with this model configuration:

    model:
      default: gemma4:e4b
      provider: custom
      base_url: http://127.0.0.1:11434/v1
    
    The Hermes API server is enabled:
    
    API_SERVER_ENABLED=true
    API_SERVER_HOST=127.0.0.1
    API_SERVER_PORT=8642
    API_SERVER_KEY=<redacted>
    
    The backend works correctly via curl:
    
    KEY="$(grep '^API_SERVER_KEY=' ~/.hermes/.env | cut -d= -f2- | tr -d '\"'\'' ')"
    
    curl -i http://127.0.0.1:8642/v1/models \
      -H "Authorization: Bearer $KEY"
    
    Expected/actual result from curl:
    
    {
      "object": "list",
      "data": [
        {
          "id": "hermes-agent",
          "object": "model",
          "owned_by": "hermes",
          "root": "hermes-agent"
        }
      ]
    }
    
    Chat completions also work:
    
    curl -sS http://127.0.0.1:8642/v1/chat/completions \
      -H "Authorization: Bearer $KEY" \
      -H "Content-Type: application/json" \
      -d '{
        "model": "hermes-agent",
        "messages": [
          {"role": "user", "content": "Respond exactly: ok"}
        ]
      }'
    
    This returns a valid response from Hermes Agent, and Ollama confirms that the local model is loaded on GPU:
    
    gemma4:e4b    11 GB    100% GPU    CONTEXT 65536
    Problem in Hermes Desktop
    
    When using Hermes Desktop 0.4.3 and selecting:
    
    Connect to Remote Hermes
    
    with:
    
    URL: http://127.0.0.1:8642
    API key: <API_SERVER_KEY>
    
    or:
    
    URL: http://127.0.0.1:8642/v1
    API key: <API_SERVER_KEY>
    
    the GUI does not connect reliably.
    
    Observed GUI errors include:
    
    Could not reach Hermes at this URL. Check the URL and API key.
    
    and:
    
    Error: API server returned 404: 404: Not Found
    
    and:
    
    Error: API request failed: connect ECONNREFUSED 127.0.0.1:8642
    Logs
    
    Hermes Desktop log includes:
    
    [CRON] remote list failed: HTTP 404
    Error occurred in handler for 'send-message': Error: API server returned 404: 404: Not Found
    
    At one point, Hermes Desktop also attempted to spawn an old local Hermes installation that no longer exists:
    
    [MAIN UNCAUGHT] Error: spawn /home/patrick/.hermes/hermes-agent/venv/bin/python ENOENT
    
    spawnargs: [
      '/home/patrick/.hermes/hermes-agent/hermes',
      'gateway'
    ]
    
    This suggests that even after choosing remote mode, Hermes Desktop may still retain or use stale local-install state under ~/.hermes/hermes-agent.
    
    Route testing
    
    The local Hermes API server exposes these routes successfully:
    
    GET /health       -> 200 OK
    GET /v1/health    -> 200 OK
    GET /v1/models    -> 200 OK
    POST /v1/chat/completions -> 200 OK
    
    But these routes return 404:
    
    GET /models       -> 404 Not Found
    GET /api/health   -> 404 Not Found
    
    This may indicate that Hermes Desktop remote mode expects routes that are not provided by the Hermes Agent OpenAI-compatible API server.
    
    Expected behavior
    
    Hermes Desktop remote mode should work with an existing Hermes Agent API server when provided:
    
    URL: http://127.0.0.1:8642
    API key: API_SERVER_KEY
    
    or clearly document whether the required URL should be:
    
    http://127.0.0.1:8642
    
    or:
    
    http://127.0.0.1:8642/v1
    
    It should then list the exposed remote model:
    
    hermes-agent
    
    and send chat requests through the existing Hermes API server.
    
    Actual behavior
    
    Hermes Desktop does not list hermes-agent, fails validation, returns 404, or tries to spawn a stale local Hermes installation under:
    
    ~/.hermes/hermes-agent
    
    even though the remote Hermes API server is alive and working via curl.
    
    Why this appears to be a Hermes Desktop issue
    
    The backend works outside Hermes Desktop:
    
    curl /v1/models succeeds.
    curl /v1/chat/completions succeeds.
    Hermes Agent CLI works.
    Ollama backend works.
    GPU model loading works.
    The only failing component is Hermes Desktop remote frontend mode.
    
    Request
    
    Please clarify or fix Hermes Desktop remote mode behavior:
    
    Which URL format is expected for remote Hermes?
    http://host:8642
    or http://host:8642/v1
    Which endpoint does Hermes Desktop use to validate remote connectivity?
    Should remote mode depend on routes like /models, /api/health, /cron, or local gateway-management endpoints?
    Can Hermes Desktop avoid trying to spawn ~/.hermes/hermes-agent/... when the user explicitly chooses remote mode?
    Can stale local install state be ignored or reset when using remote mode?
    
    
    thanks!!!
    
    ## Interface
    
    No new interfaces are introduced.
    
    # ADDITIONAL ADVICE
    
    Since you are given a git repository, you can use git commands to simplify your work.
    For example, if you made a mistake and want to revert your changes, you can use `git checkout <file>` to restore the file to its original state.
    You can also reset all changes in the repository using `git reset --hard` command.
    Additionally, you can use `git stash` and `git stash pop` to temporarily save your changes and restore them later.
    Finally, you can see the changes that you've made (which will be submitted when you call `submit`) using `git status` or `git diff` commands.
    However you don't need to use `git add` or `git commit` before submitting your changes. In fact,
    `submit` only submits currently unstaged changes because it uses `git diff` to get the changes that need to be submitted.
    
    # CHECKLIST
    
    Before submitting your solution, please go over the following checklist and make sure you've done everything:
    - [ ] If an error was reported in the issue description, I have successfully reproduced it.
    - [ ] If an error was reported in the issue description, I have confirmed that my fix resolves the error.
    - [ ] I have thought about edge cases and made sure my fix handles them as well.
    - [ ] I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass.
    I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.
    
    Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!
    
    (Current directory: /hermes-desktop, current file: none) bash-$
    
  2. Claude Assistant

    I'll start by exploring the repository structure.

  3. Claude Assistant

    Now let me add the URL normalization helper in config.ts.

  4. Claude Assistant

    Now update setConnectionConfig and resolveConnectionApiKeyUpdate to normalize.

  5. Claude Assistant

    Now update hermes.ts: URL normalization, health probing with fallbacks, and gateway spawn guards.

  6. Claude Assistant

    Now replace the health-check with a multi-endpoint probe helper.

  7. Claude Assistant

    Now update testRemoteConnection to use the shared probe.

  8. Claude Assistant

    Now the gateway spawn guards. Let me view startGateway.

  9. Claude Assistant

    Now add the httpErrorHint helper and also improve the ECONNREFUSED message.

  10. Claude Assistant

    Now let me add documentation about the expected remote URL and update the i18n hint.

  11. Claude Assistant

    Now let's run the reproduction test again.

  12. Claude Assistant

    Now update config.ts to import/re-export from the shared module, and hermes.ts to import from shared.

  13. Claude Assistant

    Now add the import/re-export in config.ts and switch hermes.ts to the shared module.

  14. Claude Assistant

    All 435 tests pass. Now typecheck and lint.

  15. Claude Assistant

    Now update Welcome.tsx to normalize the URL before testing/saving.

  16. Claude Assistant

    All checks pass. Let me do a final review of the complete solution:

  17. Claude Assistant

    The solution is complete. Here's my checklist review:

    ☑ If an error was reported in the issue description, I have successfully reproduced it. I wrote a temporary Vitest file that stands up a real HTTP server emulating the reporter's Hermes Agent API server (GET /health, GET /v1/health, GET /v1/models, POST /v1/chat/completions → 200 with Bearer auth; everything else → 404: Not Found). With the Remote URL set to http://127.0.0.1:PORT/v1 (one of the two forms the reporter tried), getApiUrl() returned …/v1, so chats went to /v1/v1/chat/completions → API server returned 404: 404: Not Found — exactly the reported failure. I also confirmed the ~/.hermes/hermes-agent/venv/bin/python ENOENT path: startGateway() spawned the local install unconditionally and had no 'error' listener (unhandled 'error' on a ChildProcess crashes the main process, matching [MAIN UNCAUGHT] … spawn … ENOENT).

    ☑ If an error was reported in the issue description, I have confirmed that my fix resolves the error. After the fix the same test passes for "", "/", "/v1", "/v1/" and "/v1/chat/completions" URL spellings: connection validation returns true, getApiUrl() resolves to the server root, and the chat stream returns ok. startGateway()/restartGateway() now return without spawning in remote mode, and a missing local Python no longer throws. I verified the new diagnostics render usefully (404 → "Set the Remote URL to the API server root…", ECONNREFUSED → "Could not reach the remote Hermes API server at …").

    ☑ I have thought about edge cases and made sure my fix handles them as well. Normalisation handles missing scheme (127.0.0.1:8642 → http://…), trailing slashes, repeated/compound suffixes, and never strips a URL down to just http://; sub-path deployments (https://h/hermes/v1) keep their prefix. Health probing tries /health → /v1/health → /v1/models, stops early on connection errors (down server) and on 401/403 (bad key), so wrong keys still fail as before. Stored keys survive equivalent URL spellings in both the main process and the Settings screen (previously re-typing the URL with /v1 silently wiped the key). Remote mode also short-circuits start-gateway/stop-gateway/gateway-status IPC so a stale ~/.hermes PID file can't be killed or reported, and cron 404s now yield a clear "server doesn't expose /api/jobs" message instead of log spam.

    ☑ I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. npm test → 33 files / 435 tests pass (including hermes-api, connection-config-security, ipc-handlers, office-start). npm run typecheck (node + web) is clean, and npx eslint . reports the same 689 problems / 56 errors as the untouched baseline, i.e. no new lint issues. All temporary reproduction test files were deleted; no repository tests were modified.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.