anomalyco / anomalyco/opencode

Cannot open a running sub-agent by clicking its task entry

Open
#40,627 2 comments 0 reactions 1 assignee View on GitHub

@kommander is already working on this.

Since Aug 5, 2026.

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

Description

Description

Describe the bug

When a sub-agent is still running, clicking its task entry does not open the sub-agent view.

The only way I can inspect a running sub-agent is:

  1. Open a sub-agent that has already finished.
  2. Use the previous/next navigation buttons to switch to the currently running sub-agent.

This means that while a task is actively executing, its details are effectively inaccessible from the task list.

Expected behavior

Clicking a task entry should open the corresponding sub-agent regardless of whether it is still running or already completed.

Actual behavior

Running sub-agents cannot be opened directly from the task list. They only become accessible indirectly through the previous/next navigation after another sub-agent view has been opened.

Environment

  • OpenCode: OpenCode 1.18.12
  • Platform: WSL1
  • Terminal: bash

Additional context

This makes it difficult to monitor the progress of long-running sub-agents, since the task list suggests they are selectable but does not actually allow opening their live view.

Plugins

oh-my-openagent

OpenCode version

OpenCode 1.18.12

Steps to reproduce
  1. Start a task that spawns one or more sub-agents.
  2. While one of the sub-agents is still running, click its task entry in the task list.
  3. Nothing happens (or the sub-agent view does not open).
  4. Wait for another sub-agent to finish.
  5. Open the completed sub-agent.
  6. Use the previous/next navigation buttons.
  7. The running sub-agent can now be viewed.
Screenshot and/or share link

No response

Operating System

Windows10 22H2 + WSL1 Ubuntu 22.04.5 LTS

Terminal

Ubuntu.exe

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.