Stale local branches stay visible after a fetch (f) in the TUI until restart. Reported 2026-09-19, not located: workspace sync marks commits stale per repository, and nothing found caches a branch list. Reproduce first and record the screen name.
Closed as fixed by #commit:ee5a6ec8 (the sync ancestry fix). The starved walk window meant a post-merge sync ingested and re-attributed nothing, so deleted branches lingered in the TUI until a restart happened to heal them; after the fix the migration walk re-ingested, and the merged branches' rows are now stale and hidden, matching the user's observation. Known cosmetic residue, not this bug: a fast-forward-merged branch whose hashes never changed keeps its old branch label on those live rows until a walk re-attributes them.
↩ Max Rakhimov · 2026-09-28
Investigated 2026-09-28, still not located; needs the screen name to go further. No TUI code caches a local branch list: the PR form reloads git branches on every open, and no view lists local branches today. The one process-lifetime cache in range is review's fetched-refs memo, which would show stale fork branches (not local ones) until restart. If the sighting was fork branches in the PR form's dropdown, that memo is the suspect; if it was local branches somewhere else, please name the screen and the action taken before f.