Skip to content

Running state misleading #81

Closed
Closed

Description

@arnonuem

When i run my coding tool by executing its binary the state of the session immediately goes into running.

But that coding tool is idling. Would be nice to make that status more fine grained somehow otherwise its not that helpful.

I have multiple sessions all with that coding tool but not all coding tools are really doing anything at the same time they are idling. But the tab shows running. I guess you determine it by whether a process is started or not.

I know its hard to find out - but maybe other tools can kind of hook into the state model by providing information like flag files or whatever.

Would love to have some sort of a solution here.

Activity

  1. arnonuem commented on Jul 10, 2026

    @arnonuem
    Author

    Whats also interesting is, that when the app started to fire up some shell commands for example for merging pullrequests and stuff - the session went to idle o_O

  2. arnonuem commented on Jul 10, 2026

    @arnonuem
    Author

    As a workaround it would be helpful if i could set the state manually RUNNING or IDLE - its not ideal but at least it would reflect the truth then. RightClick toggle state or similar.

  3. tawman commented on Jul 11, 2026

    @tawman
    Contributor

    @arnonuem have you installed the latest release with PR 79 merged? it had fixes on the status being wrong

  4. added a commit that references this issue on Jul 11, 2026
  5. amirlehmam commented on Jul 11, 2026

    @amirlehmam
    Owner

    Your workaround suggestion is exactly what shipped in v0.21.0: right-click a workspace → Status Indicator → Auto (detected) / Pin as Running / Pin as Idle. A pinned status wins over all auto-detection, and Auto switches back to the heuristics anytime. So when your coding tool idles while the shell still technically has a foreground process, you can pin the truth by hand.

    On the detection side, @tawman's point stands: make sure you're on v0.20.0+ — PR #79 reworked workspace status (coordinator-owned + self-healing), and v0.21.0 also clears a stuck "Running" badge when the PTY process actually exits. That should fix both the "immediately shows running" and the "went idle while firing shell commands" cases you saw.

    Longer term, your idea of letting tools hook into the state model is interesting — wmux already exposes a CLI (wmux set-status, wmux hook --event) that agents use to report activity, so a flag-file/CLI-based state protocol for arbitrary tools is a natural extension. If the manual pin + v0.21.0 detection still doesn't reflect reality for your setup, tell me which tool you're running and I'll look at wiring it up properly.

    Closing as shipped — comment and I'll reopen if it still misbehaves after updating.

  6. amirlehmam commented on Jul 22, 2026

    @amirlehmam
    Owner

    Update: v0.29.1 fixes a big part of this. Installed builds were missing resources/cli/wmux-hook.js — the script that reports Claude Code activity (tool use, turn finished) to the sidebar — so those signals never arrived and the status could only ever reflect "a process is running in the shell", which is permanently true for any interactive TUI. With the file shipped, Claude Code workspaces now flip to Idle the moment a turn ends.

    For non-Claude coding tools there's still no turn-level signal to read (the shell only tells us a process is in the foreground), so the manual status pin from this issue remains the fallback there — or the tool can push state through wmux set-status / the pipe like the OpenCode plugin does.

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions