Code editor: auto-save + auto-refresh external file changes (VS Code-like behavior)

[diastidean]

Problem

Warp's code editor does not currently auto-save edited files or auto-refresh open files when those files change on disk.

For workflows where files are edited by external tools (formatters, generators, git operations, etc.), this creates friction versus editors like VS Code.

Current behavior

• File saves are manual only.
• External on-disk updates are not always auto-reflected based on a user-configurable setting.

Requested behavior

Add editor settings for:

1. Auto-save mode

   • off
   • after_delay
   • on_focus_change
   • after_delay_and_focus_change

2. Auto-refresh files changed on disk

   • boolean toggle to automatically refresh open files when external file changes are detected.

UX / Settings placement

• Expose controls in Settings → Code under editor/code-review section.
• Auto-save should behave similarly to VS Code expectations:
  • debounce for delay-based save
  • focus-change trigger when configured
  • avoid noisy manual-save toasts for auto-save events

Why this matters

• Reduces friction for users coming from other editors.
• Prevents stale editor state when external processes modify files.
• Improves reliability for agent-assisted and tool-assisted coding workflows.

Notes

I already have a local implementation prototype ready and can contribute it once this issue is triaged through Warp's feature/spec process.

[oz-for-oss]

@diastidean

This issue appears to overlap with existing issues:

• [Feature Request] Auto Save for built-in Code Editor #8899 — [Feature Request] Auto Save for built-in Code Editor
• File synchronization/update feature for splitter screen #6921 — File synchronization/update feature for splitter screen

If this report is meaningfully different, please comment with the additional context or distinguishing behavior so a maintainer can review it. Otherwise, a maintainer may close it as a duplicate after review.

Maintainer details

I concluded that feature request for VS Code-like code-editor auto-save and auto-refresh substantially overlaps existing open auto-save and file-sync issues..

Duplicate reasoning

• [Feature Request] Auto Save for built-in Code Editor #8899: Requests the same built-in Code Editor auto-save capability, including VS Code-like modes such as off, after delay, and focus/window change, to avoid running tools against stale unsaved edits.
• File synchronization/update feature for splitter screen #6921: Requests automatic or manual synchronization when an open file is modified externally by another app, agent, git operation, or other process, matching the auto-refresh portion of this report.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

[diastidean]

@oss-maintainers I have an implementation prototype ready locally and would like to contribute this. Could you please triage this feature request for readiness ( / ) per the contribution process?

[diastidean]

Correction: requesting triage for readiness labels ready-to-spec or ready-to-implement per CONTRIBUTING.md. I have an implementation prototype ready locally and can open the appropriate spec/code PR once triaged.

[zachlloyd]

I would like this feature for sure. @alokedesai @kevinyang372 do you have concerns here or could we move this into the ready-to-spec state?

[kevinyang372]

We already have auto-reload

No concerns on moving auto-save to ready-to-spec