Use case / Example:
- Open a project on an SSH/SFTP-mounted filesystem.
- Edit a file externally — for example via a terminal session, or an AI coding agent like Claude Code / Claude Remote making changes directly on disk.
- Switch back to Code App: the editor still shows the old, stale content. Changes made outside the app aren’t picked up automatically.
Proposed behavior:
- When a file is modified on disk (detected via filesystem watcher / SFTP polling), the open editor tab should automatically refresh to reflect the new content — as long as there are no unsaved local changes.
- If the local buffer has unsaved changes that conflict with the on-disk version, prompt the user with options such as:
- Keep local changes (overwrite disk)
- Load disk version (discard local changes)
- View diff / merge manually
Why this matters:
This is increasingly common with AI coding assistants and remote dev workflows that edit files directly on disk outside the editor’s control. Without auto-refresh, users risk working on stale files or unknowingly overwriting external changes when they save.
Use case / Example:
Proposed behavior:
Why this matters:
This is increasingly common with AI coding assistants and remote dev workflows that edit files directly on disk outside the editor’s control. Without auto-refresh, users risk working on stale files or unknowingly overwriting external changes when they save.