fix(vcs): list-mode status without remote pollers for row UIs - #170
Merged
Conversation
Break the O(N) always-on VCS poller model for sidebar/board/thread lists: subscribe with mode=list loads local (+ one coalesced remote) but does not retain the automatic remote poller. Active git chrome keeps full mode.
List mode no longer drops live remote/PR updates. A single shared sweep refreshes all list-interested worktrees on a 60s cadence with concurrency 2, skipping cwds that already have a full-mode poller. Per-row 30s pollers stay gone so O(N) storms do not return.
patroza
force-pushed
the
t3code/vcs-list-mode-no-poller
branch
from
July 29, 2026 09:32
61e4809 to
825db39
Compare
4 tasks
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
1 participant
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
Structural fix for the VCS storm root cause — without dropping live PR/git freshness on list UIs.
Problem
Every sidebar/board row used full
subscribeVcsStatus→ one remote poller fiber per worktree → O(N) git/fetch/gh → thrash → disconnects. That model is upstream; fork amplifies via board.What we do not do
We do not leave list rows one-shot/stale. PR badges and remote state stay up to date.
Structural model
listgit fetchon sweep). No per-cwd poller.fullList subscribers still receive pubsub updates when the shared sweep (or a full subscriber / explicit refresh) updates their cwd.
Details
VcsStatusInput.mode: "full" | "list"vcsEnvironment.listStatus(forces list, 60s idle TTL)Tests
Test plan
retainRemotePollerstorms