Skip to content

Openocde Agents not replying #40471

New issue
New issue
Closed as not planned
Closed as not planned
Openocde Agents not replying#40471
Assignees
kitlangton

Description

@Shan7Usmani
Shan7Usmani
opened on Aug 4, 2026

Description

The agent is stuck at thinking and not giving any response.

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

Activity

  1. github-actions
    assigned
    kitlangton
    on Aug 4, 2026

  2. github-actions commented on Aug 4, 2026

    @github-actions
    github-actionsBot
    on Aug 4, 2026 – with GitHub Actions
    Contributor

    This issue doesn't fully meet our contributing guidelines.

    What needs to be fixed:

    • The description is too vague to be actionable — "The agent is stuck at thinking and not giving any response" does not provide enough context to reproduce or investigate the problem.
    • OpenCode version is missing (required).
    • Steps to reproduce are missing (required for bug reports).
    • Operating System and Terminal are missing.

    Please edit this issue to fill in the missing fields within 2 hours, or it will be automatically closed.

    This issue might be a duplicate of existing issues. Please check:

    If you believe this was flagged incorrectly, please let a maintainer know.

  3. github-actions
    added
    needs:complianceThis means the issue will auto-close after 2 hours.
    on Aug 4, 2026

  4. marvix1122333 commented on Aug 4, 2026

    @marvix1122333
    marvix1122333
    on Aug 4, 2026

    same here, even ordinary "hello" , i didnt get any response

  5. asim-ali-peerzada commented on Aug 4, 2026

    @asim-ali-peerzada
    asim-ali-peerzada
    on Aug 4, 2026

    Same here resolve it ASAP!

  6. Serpentv commented on Aug 4, 2026

    @Serpentv
    Serpentv
    on Aug 4, 2026

    me too, it still thinking for 15 minute

  7. justdoshiba commented on Aug 4, 2026

    @justdoshiba
    justdoshiba
    on Aug 4, 2026

    same, only on deepseek v4 flash new free, other models seem to work correctly

  8. PhucTruong-ctrl commented on Aug 4, 2026

    @PhucTruong-ctrl
    PhucTruong-ctrl
    on Aug 4, 2026

    +1 with Deepseek v4 flash new, encountering this for like 1 hour and still not working.

  9. DejanGegic commented on Aug 4, 2026

    @DejanGegic
    DejanGegic
    on Aug 4, 2026

    can confirm, this has been going on for a bit longer than this issue is opened.

    I tested multiple models on Zen and Go, it's a DeepSeek V4 Flash specific issue as i see. Kimi K3 has some "hickups" too but it's good enough

  10. DejanGegic commented on Aug 4, 2026

    @DejanGegic
    DejanGegic
    on Aug 4, 2026

    Same here resolve it ASAP!

    We are paying customers, but keep your tone polite and respectful, thank you.

  11. lightninng commented on Aug 4, 2026

    @lightninng
    lightninng
    on Aug 4, 2026

    This has been occurring since 21:30. When I set deepseek-v4-flash as the default request model and keep only deepseek-v4-flash in the candidate models, it keeps showing 'Thinking...'. However, when I add glm5.2 to the candidate models, even though my default model and the top-priority candidate model are still deepseek-v4-flash, I see in the OpenCode Go backend that the model being requested is actually glm5.2.and I also tried for mimo-v2.5，it's same as deepseek-v4-flash

  12. MrBoggi commented on Aug 4, 2026

    @MrBoggi
    MrBoggi
    on Aug 4, 2026

    I use opencode in Home assistant and see the same behaviour. I have tried attaching more useful info:

    [Bug] OpenChamber / OpenCode crash on restart after manual configuration reload ("OpenCode service unavailable" & WebSocket/SSE proxy errors)

    Summary

    When triggering a Manual configuration reload, OpenChamber attempts to restart the managed OpenCode instance. During this process, existing connection proxies (SSE and WebSockets) crash, throwing UND_ERR_SOCKET / terminated errors, followed by Error: OpenCode service unavailable while OpenChamber tries to establish connections before the new OpenCode process is fully ready.

    Although OpenChamber eventually recovers once the port is detected and [PushWatcher] reconnects, the transition generates substantial error noise and stream disconnections.

    Additionally, there is continuous log spam regarding Git operations (simple-git) failing repeatedly when running in non-git directories (such as /data, which is simply used to store session files).

    Environment / Context

    • Environment: Home Assistant Add-on container (s6-overlay / s6-rc)
    • Interface Mode: openchamber
    • OpenCode Version: 1.18.10 (also observed on 1.18.9)
    • Node module path: @openchamber/web
    • Working Directory: /data (non-git directory containing session files)

    Steps to Reproduce

    1. Start the add-on with INTERFACE_MODE=openchamber in a non-git working directory (e.g., /data).
    2. Trigger a Manual configuration reload via settings.
    3. OpenChamber attempts to stop the running OpenCode process and launch a new one on a newly allocated port.
    4. Observe the log output during the transition.

    Observed Behavior

    1. Abrupt termination of SSE/WS streams:
      When OpenCode is stopped during the config reload, OpenChamber encounters unhandled socket errors from undici:

      [proxy] OpenCode SSE proxy error: terminated
Message stream WS proxy error: TypeError: terminated
    at Fetch.onAborted (node:internal/deps/undici/undici:11700:53)
...
[cause]: SocketError: other side closed (UND_ERR_SOCKET)

    2. Race condition during service startup:
      While launching the new OpenCode managed server on the new port (e.g., 46209), OpenChamber repeatedly attempts to connect before OpenCode is fully bound and ready, leading to temporary connection error spikes:

      Message stream WS proxy error: Error: OpenCode service unavailable
    at buildUrl (file:///usr/local/lib/node_modules/@openchamber/web/server/lib/event-stream/global-hub.js:73:17)
    at file:///usr/local/lib/node_modules/@openchamber/web/server/lib/event-stream/upstream-reader.js:124:23
[PushWatcher] disconnected OpenCode service unavailable

      (Note: The system eventually recovers after port detection, but the process startup window is unhandled.)

    3. Excessive Git Discovery / Worktree Error Spam:
      When cwd is set to a non-git directory like /data, simple-git continuously attempts rev-parse --show-toplevel and worktree listings, flooding the log stream:

      Failed to get remotes: GitError: fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

    Expected Behavior

    • Graceful Proxy Teardown: SSE and WebSocket proxy connections should handle upstream process termination gracefully without throwing unhandled socket errors.
    • Readiness Polling: OpenChamber should wait for the new OpenCode HTTP/API server readiness check before attempting to reconnect PushWatcher / WebSocket streams.
    • Git Check Guard: OpenChamber / simple-git should verify if the working directory is a valid Git repository before executing Git commands to avoid continuous log spam in non-git directories.

    Log Excerpt

    [Server] Manual configuration reload requested
Refreshing OpenCode after manual configuration reload
Restarting OpenCode process...
Stopping existing OpenCode process...
[proxy] OpenCode SSE proxy error: terminated
Message stream WS proxy error: TypeError: terminated
...
    code: 'UND_ERR_SOCKET',
    socket: { localAddress: '127.0.0.1', localPort: 51150, remoteAddress: '127.0.0.1', remotePort: 36089 }
...
Starting OpenCode on allocated port 46209...
[OpenCode] Launching managed server ...
Message stream WS proxy error: Error: OpenCode service unavailable
    at buildUrl (file:///usr/local/lib/node_modules/@openchamber/web/server/lib/event-stream/global-hub.js:73:17)
[PushWatcher] disconnected OpenCode service unavailable
Detected OpenCode port: 46209
[PushWatcher] connected

  13. marvix1122333 commented on Aug 4, 2026

    @marvix1122333
    marvix1122333
    on Aug 4, 2026

    i think it is fixed for big pickle model

  14. DejanGegic commented on Aug 4, 2026

    @DejanGegic
    DejanGegic
    on Aug 4, 2026

    Thanks OpenCode team. This is fixed now.

  15. github-actions commented on Aug 4, 2026

    @github-actions
    github-actionsBot
    on Aug 4, 2026 – with GitHub Actions
    Contributor

    This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.

    Feel free to open a new issue that follows our issue templates.

  16. github-actions
    removed
    needs:complianceThis means the issue will auto-close after 2 hours.
    on Aug 4, 2026
  17. github-actions
    closed this as not plannedon Aug 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions