Skip to content

[Request] Auto-refresh editor when files change on disk (with conflict prompt for unsaved local edits) #1331

Description

@leolelego

Use case / Example:

  1. Open a project on an SSH/SFTP-mounted filesystem.
  2. 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.
  3. 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions