fix(frontend): a pending interaction anywhere in the tab counts as awaiting - #5913
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 6 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
dosubot
Bot
added
size:S
…aiting hitlPending reads only the LAST assistant message, so when a new turn starts streaming (or hydration reshapes the transcript) a still-pending interaction in an earlier message stopped counting: status collapsed to idle, the settle stamp landed, and the running-elsewhere strip flickered in the very tab that owned the parked widget (session e627d80a). The status publisher now scans the whole transcript for pending interactions.
093bd82 to
b670e85
Compare
Railway Preview Environment
Updated at 2026-08-10T16:51:30.431Z |
1 participant
Context
In session e627d80a territory: the "running somewhere else" strip flickered in the very tab that owned a parked connect card whenever a new turn started. The status publisher derives "awaiting" from
hitlPending, which reads only the LAST assistant message; the moment a new turn begins streaming (or hydration reshapes the transcript), a still-pending interaction in an earlier message stops counting, status collapses toward idle, the settle stamp lands, and the #5857 strip logic sees "settled locally, running remotely" — the exact signature of another tab.Changes
The status publisher scans the whole transcript: any pending client-tool interaction this tab renders means this tab owns the run, so the session publishes "awaiting" and the strip stays suppressed. One memo plus one condition; the strip's own derivation is untouched.
Tests
Type-check clean; the AgentChatSlice suite runs in CI. Live behavior is part of the compound-flow QA below.
What to QA