Manage CodeSpace Tabs and Unsaved Changes
Switch between open CodeSpace files, read modified indicators and choose Cancel, Don't Save or Save and Close without losing pending edits.
Each open file has a tab and its own in-memory editor model. Click a tab to activate it. The breadcrumb identifies its path; a ● marker indicates the file has been marked modified, and the active file's status can show Unsaved.
Switching tabs retains pending changes during the current workspace session. It does not save them. Reopening an already-open file uses its existing model, so it is not a disk reload. Save controls and Undo/Redo operate according to the active model or modified-file set.
Close a tab
Use the tab's close button. An unmodified tab closes directly. For a modified tab, Unsaved Changes offers:
| Choice | Result |
|---|---|
| Cancel or dialog close button | Dismisses the dialog and keeps the file open. |
| Don't Save | Discards pending edits and closes the tab; the saved disk file remains as it was. |
| Save & Close | Attempts to save that file and closes only after a successful response. |
If Save & Close fails, the file remains open. Preserve its pending text and resolve the error using Saving. Closing the active tab activates a neighboring tab if available; closing the last file returns to the empty editor.
Protect pending work
Tab prompts are not recovery storage
The current application does not implement autosave, draft restoration or a browser-unload guard. Closing the browser tab, reloading, following Dashboard or Logout, or losing the session can lose pending text without the file-tab dialog. Save deliberately and verify the result before leaving.
The active Saved status does not prove every open tab is saved. Check modified markers or use Save All. Editor change events mark a file dirty; undoing to earlier text may still leave a dirty marker, so it is not a byte-for-byte comparison with disk. Preserve sensitive drafts privately when recovering from a failure.