Desktop: file viewer side panel never reloads a file the agent edits — stale content until tab is closed and reopened

Resolved 💬 2 comments Opened Jun 12, 2026 by LevonMartirosyan Closed Jun 16, 2026

Bug

The file viewer side panel in the Claude Desktop app does not reload a file when it changes on disk. When Claude (the agent) edits or rewrites a file that is currently open in the panel, the panel keeps showing the stale content indefinitely. There is no refresh button or keyboard shortcut; the only workaround is to close the file tab and re-open the file via a link in chat.

Steps to reproduce

  1. In a Claude Desktop local-agent session, have Claude write a markdown file inside the project and output a clickable link to it.
  2. Click the link — the file opens in the right-side panel.
  3. Ask Claude to rewrite the file (Write/Edit tool on the same path). The tool reports success and the chat shows the diff (e.g. "+68 −61").
  4. Look at the panel: it still renders the old version. Waiting does not help.

Expected

Either auto-reload when the file changes on disk (the agent editing an open file is the core workflow), or at minimum a visible refresh control on the panel.

Impact

This made an agent-and-user "shared document" workflow (user reads/discusses a doc in the panel while the agent updates it from the conversation) very confusing — the user repeatedly saw stale content and thought the agent had not done the work. Several rounds of "where is it?" before we found the close-and-reopen workaround.

Environment

  • Claude Desktop app 1.12603.1 (darwin), local agent mode (Claude Code harness)
  • macOS Darwin 25.5.0
  • File inside the session's project directory (gitignored subfolder); opening it worked, only reloading is the problem
  • Also observed: opening a file OUTSIDE the project folder shows "File could not be read. It may have been deleted or moved, or it lives outside the session folder." — fine as a restriction, but the reload issue applies to in-project files

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗