fix(web): restore thread-header AI usage + host resource gauges - #208
Merged
omegent-app[bot] merged 2 commits intoJul 30, 2026
Merged
Conversation
Stack product rejoin re-landed HostResourceStatus and ai-usage helpers but dropped the ChatHeader wiring, so conversation-level usage dots and remote CPU/MEM/Load disappeared while settings still showed host metrics. Re-wire both surfaces and add anti-stack-drop existence tests.
Classic sidebar already rendered provider usage markers on thread rows; Threads V2 only showed the provider icon. Wire the same ai-usage snapshot + statusDot markers (and tooltip stats) so both list modes stay parity.
patroza
pushed a commit
that referenced
this pull request
Jul 30, 2026
Restore conversation-level AI usage status and host CPU/MEM/Load in ChatHeader, add usage dots to Sidebar V2 thread rows (classic sidebar already had them), and add anti-stack-drop existence tests so these surfaces cannot vanish on product rejoin.
patroza
pushed a commit
that referenced
this pull request
Jul 30, 2026
Restore conversation-level AI usage status and host CPU/MEM/Load in ChatHeader, add usage dots to Sidebar V2 thread rows (classic sidebar already had them), and add anti-stack-drop existence tests so these surfaces cannot vanish on product rejoin.
patroza
pushed a commit
that referenced
this pull request
Jul 31, 2026
Restore conversation-level AI usage status and host CPU/MEM/Load in ChatHeader, add usage dots to Sidebar V2 thread rows (classic sidebar already had them), and add anti-stack-drop existence tests so these surfaces cannot vanish on product rejoin.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
AiUsageStatstooltip) in the thread header next to the title.HostResourceStatus) in the thread header.ChatViewto passactiveThreadDriverKind,activeThreadModel, andisPreparingWorktree.Root cause
The stack product rejoin (
feat(web): sidebar lists, composer, timeline, and chrome fork product/8ac8ce739) re-landed:HostResourceStatuscomponent…but never re-attached
HostResourceStatusor the conversation-level usage marker toChatHeader. That is a classic fork stack conflict / provenance rewrite failure mode (same class as #154 remote Open in VS Code): helpers and settings survived; thread chrome did not.Provider-icon dots and model-picker selection-box stats were still present in code; they only appear when the
ai-usagedaemon feed has items (and warn/critical/outlook markers for dots). The missing thread-top CPU/MEM/Load and conversation usage status were pure wiring drops.Test plan
vp test runChatHeader + forkSurfaceExistence + aiUsage + hostResourcePresentationvp check