Save CodeSpace Files and Resolve Disk Conflicts
Use Save and Save All, interpret partial failures and recover from CodeSpace modification-time conflicts while preserving both pending text and current disk content.
CodeSpace saves explicitly. Use Save or Ctrl+S / Command+S for the active modified file. Use Save All or Ctrl+Shift+S / Command+Shift+S for all modified open files. Demo servers block writes.
Save a file
- Confirm the active file's breadcrumb and preserve a recovery copy if needed.
- Finish the edit and click Save.
- Wait for the response before continuing to edit or starting another save.
- Check Output, the tab's modified marker and the active Saved/Unsaved indicator.
- Test affected application behavior separately.
Save is enabled for an active file marked modified. Save All is enabled when any open file is modified. A success message means the service returned a successful save; text merely appearing in the editor is not confirmation.
Avoid editing during an in-flight save. The current success handler clears the file's dirty flag without checking whether newer edits were made while the request ran. A Saved indicator can therefore be misleading in that situation; preserve the latest text and compare the disk file if uncertain.
Save All
Save All processes modified files sequentially, rather than as one transaction. Successful files stay saved even if another fails. Output can report saved and failed counts; inspect remaining modified tabs and retry only after resolving their errors. The current success translation can say All files are already saved after a successful batch as well as when there was nothing to save. Check file state and errors rather than treating that wording as a distinct operation state.
External changes and conflicts
CodeSpace sends the file modification timestamp received when opening it and updates that timestamp after a successful save. The service compares it with the current disk timestamp and can reject a save with File has changed on disk. The UI may show only Unable to save file while the detailed response is in browser developer tools.
- Preserve your unsaved text privately before closing, reloading or signing in again.
- Inspect or download the current disk file through File Studio.
- Compare and merge the two versions deliberately.
- Close the stale editor tab after protecting its text, then reopen to get a fresh disk copy.
- Apply the intended merged changes and save again.
Explorer Refresh and clicking an already-open file do not refresh its disk timestamp or editor contents. There is no force-overwrite or merge-conflict dialog. The timestamp check reduces accidental stale saves; it is not collaborative editing or a permanent lock.
Write requirements
The file must already exist, be an eligible account-owned regular file, and pass protected-path and symbolic-link checks. Content is saved as UTF-8 and must fit the configured edit-size limit (source default 5 MiB). The backend replaces one file through a temporary file while preserving its owner and mode; this is not version history or a rollback copy. A failure after replacement or a lost response still requires checking disk state before retrying.