Skip to content
Source
Sign inSign up

[Bug]: Local ACP provider fails to initialize Hermes via Ollama (60s timeout) despite working in CLI #33104

Send to my agent
OpenArmagetto(GitHub profile, opens in a new tab) opened this issue 0 comments

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

  1. Configure a Local ACP provider in the UI
  2. ACP source: Local command
  3. Executable: hermes (or absolute path to hermes.exe)
  4. Arguments: acp
  5. Save and trigger the provider refresh/session creation.
  6. Observe the startup attempt.

Expected behavior

The ACP agent should successfully resolve, establish communication over standard input/output, and create a test session within the startup window.

Actual behavior

The initialization hangs, and after 60 seconds, the UI outputs the following error state: "Status: Needs attention The ACP agent did not resolve and create a test session within 60 seconds. Package installation or agent startup may be slow; this check retries on the next provider refresh."

Impact

Major degradation or frequent failure

Version or commit

0.1.7

Environment

windows x64

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

  1. Armagetto(GitHub profile, opens in a new tab) added labelsneeds-triage

Sign in to join this conversation.