[Bug] Open files don't refresh when modified externally

[Valeron2206]

Pre-submit Checks

• I have searched Warp issues and there are no duplicates
• I have searched Warp docs

Describe the bug

Files already open in Warp's built-in code editor do not refresh when modified externally (by a CLI tool, another editor, or an AI agent). The editor continues to show the stale version until you manually close and reopen the file.

Steps to reproduce

1. Open a file in Warp's code editor (e.g. main.ts)
2. In the terminal (or via an external tool like Claude Code / Agent Mode), modify that same file
3. Switch back to the editor tab

Expected: The editor detects the external change and reloads the file content (like VS Code, JetBrains, Zed, etc.)
Actual: The editor still shows the old content. The only way to see the updated file is to close the tab and reopen it.

Impact

This is critical for terminal-first workflows where CLI agents (Claude Code, Codex, Aider) frequently write to files that are simultaneously open in the editor. Without automatic reload, the developer is always looking at stale code, which leads to confusion and mistakes.

Expected behavior

The editor should watch for fs events on open files and:

• If the file has no unsaved local changes — reload silently
• If the file has unsaved local changes — show a prompt ("File changed on disk. Reload?") or a merge indicator

This is standard behavior in VS Code, Zed, Neovim, JetBrains IDEs, and Sublime Text.

Environment

• OS: macOS 15.5 (Sequoia)
• Warp version: latest stable (as of 2026-03-18)