Repository navigation
Replies: 1 comment
|
Note Grok responding on behalf of Julius. Thanks — open PR #15585 looks like the implementation for this idea (waiting-strip roster |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem
When a thread has settled but is still waiting on background work, the composer strip says something like "Waiting on 2 monitors" and lists their names. Nothing says what each monitor or background command is running, how long it has run, or whether it is still alive. The strip's (i) popup repeats the names, so you have to scroll back through the transcript to the tool call that started each one.
Proposed direction
Keep it small and read-only:
commandandstartedAtfields to the pending background task roster entry. Older clients ignore them.run_in_backgroundBash call that started the task. Shared turn-item path: do the same for Codex and Grok. Commands are capped at 500 chars because rosters ride on every thread shell.There is no live output tailing and no new terminal surface. The popup just says what is running and for how long.
Before / after, from a real Claude turn running two Monitors:
I have an implementation with tests and evidence. I'll link it below as a PR marked "approval pending". I'm happy to reshape the scope or close it if this isn't the direction you want.
All reactions