anomalyco / anomalyco/opencode

Agent activity appears stuck while tool execution continues

Open
#46,559 1 comment 0 reactions 1 assignee View on GitHub

@kommander is already working on this.

Since Sep 1, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

When I give OpenCode a prompt, the agent can produce an initial output and then call a tool to continue working. At that point, the UI appears to get stuck.

The build/activity animation continues to show, but there is no visible progress or new output, making it look like the agent has stopped responding.

I pressed Esc to stop the agent. After forcing the agent to stop, OpenCode immediately displayed the work that had been happening in the background, including file edits and continued agent activity that were not visible while the agent was running.

Expected behavior

While the agent is actively working or waiting on a tool, OpenCode should continue displaying its progress, tool calls, output, and file changes in real time.

Actual behavior

The UI appears stuck even though the agent is still working in the background. The activity animation continues, but there is no visible progress.

The work only becomes visible after the agent is manually stopped with Esc

Plugins

No response

OpenCode version

1.18.25

Steps to reproduce
  1. Give the OpenCode agent a prompt that requires tool usage and continued work.
  2. Let the agent produce its initial output.
  3. Wait for the agent to call a tool and continue working.
  4. Observe the UI while the tool/agent is working.
  5. The activity/build animation remains visible, but no progress or output is displayed.
  6. Press Esc to stop the agent.
  7. Previously hidden agent activity and file edits become visible.
Screenshot and/or share link

No response

Operating System

Windows 11

Terminal

Windows Terminal

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.