Skip to content

Muse Code pane stays working after the turn ends #3951

Description

@JacobStephens2

Is this a reproducible bug?

  • I confirm this is a reproducible bug, not a feature request, idea, question, contribution proposal, or direction check.
  • I reproduced this bug on the version and environment reported below using the exact steps provided.

Current behavior

A Muse Code 1.1.1 pane is detected as muse, but after the turn finishes the sidebar status bubble stays yellow/working.

On the live pane the Muse UI is idle:

◆ Worked for 3m 13s · 12:29 AM
── Voice input (⌥ + v to start) ──
❯
──
  muse-spark-1.3 · high · ~/.herdr/worktrees/career/79 · YOLO

Same pane, same moment:

  • herdr agent listagent: muse, agent_status: working, revision: 2 (stuck)
  • herdr agent explain w4J:p1 --jsonstate: idle, matched idle_status_fallback, visible_idle: true

Neighboring Grok panes in the same workspace update normally (working / done).

Expected behavior

When Muse finishes a turn and shows the idle prompt, the pane should become idle (or done if unfocused), and the space/pane status bubble should follow.

Reproduction

  1. Herdr 0.9.0 stable, Muse Code 1.1.1 (muse-bin-1.1.1-R2514.1).
  2. In a Herdr pane, start muse and send a prompt that completes.
  3. Wait until the Muse UI shows ◆ Worked for … and the prompt.
  4. Run herdr agent list and herdr agent explain <pane> --json.

explain reports idle. list and the sidebar bubble stay working.

Impact

I cannot trust the Herdr sidebar for Muse the way I do for Grok/Claude. A finished Muse session keeps looking like it still needs attention, so I have to open the pane to find out.

Environment

  • Herdr version: 0.9.0 (/Users/jacob/.local/bin/herdr)
  • Update channel (stable or preview): stable
  • Operating system: macOS 26.5.2 (Apple Silicon)
  • Terminal: Ghostty
  • Shell, if relevant: zsh
  • Relevant config, if any: Muse Code 1.1.1 (1.1.1-R2514.1); muse detection manifest 2026.08.26.1; no local ~/.config/herdr/agent-detection/muse.toml override

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-detectionagent recognition or working, blocked, idle, and lifecycle classificationmaintainer-neededrequires maintainer judgment or maintainer-only reproductionneeds-upstream-fix

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions