GitHub issue #59955 in zed-industries/zed, opened 2026-06-26 by lixiaoyan, records a report that Zed always displays stale cached content for files under .git instead of the version on disk, demonstrated by writing "a" to .git/COMMIT_EDITMSG, opening it in Zed, closing the tab, writing "b" to the same file, and reopening it in Zed; that the issue significantly affects users who configured VISUAL="zed --wait", since every commit or interactive rebase can potentially show stale file content; and that Zed should always display files under .git using the latest content. The report was filed against Zed v1.9.0+preview on macOS 26.5.1.
Verbatim Excerpts from Cited Records
“In Zed's integrated terminal, run the following in sequence:”
·
zed-industries/zed (issue 59955 opening body, Reproduction steps section)
·
2026-06-26T12:14:38Z
·GitHub Issue ↗
“This issue significantly affects users who have configured `VISUAL="zed --wait"`. Every commit or interactive rebase can potentially show stale file content.”
·
zed-industries/zed (issue 59955 opening body, Reproduction steps section)
·
2026-06-26T12:14:38Z
·GitHub Issue ↗
“Zed should always display files under `.git` using the latest content.”
·
zed-industries/zed (issue 59955 opening body, Current vs. Expected behavior section)
·
2026-06-26T12:14:38Z
·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 8 comments were read. lixiaoyan (2026-06-26) notes the .git problem is reproducible essentially 100% of the time, unlike occasional desyncs from external agents modifying files, and distinguishes it from #58389. phw (2026-07-09) confirms it as a regression and reports git commits or rebases frequently show old content, with rebase showing commits from a previous rebase able to drop commits; the only workaround found was closing and restarting Zed between commits. mjkang-estrella (2026-07-30) reproduced 2/2 on current Zed stable 1.13.1 with a fresh repository and marker strings. phw (2026-08-20) reports `zed --wait --new` as a workaround that shows non-stale content. nickbeth (2026-11-09) reports still being affected. No maintainer fix and no retraction of the report appear in the surveyed thread. The claim documents only the original report, not a verified current state.
Falsification probe: If GitHub issue #59955 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.