When a project ends, do not close windows by age or application. Classify each window by what would be lost and whether a real next action remains. The result should be a smaller desktop and a durable project record outside the window manager.
Sort windows into three outcomes
Use three questions:
| Question | Action |
|---|---|
| Is this the only place an unsaved change exists? | Save or export in the source app first |
| Will I need this information later, but not now? | Store the file, link, or note durably, then close |
| Is there an agreed next action that needs this live state? | Keep it open and write the action |
Old previews, duplicate exports, resolved feedback, and exploratory tabs normally belong in the close set. Final deliverables, decisions, and approved sources belong in durable storage. A live terminal or authenticated web state may be convenient, but convenience is not archival durability.
Close at the right level
Closing a document window is not always the same as quitting its application. A browser tab, browser window, and browser process also have different scopes. Read the confirmation prompt and check unsaved indicators before using a bulk close command.
If a tool offers a saved layout, verify what it records. Window positions, app identities, document links, processes, and in-app state are separate capabilities. Do not delete the durable source because a layout or window group appears to remember it.
Finish the project group
Remove windows that no longer belong, mark the final task state, and retain only any explicit follow-up. In Wallo, hiding goals without unfinished tasks is a view filter rather than an archive format. Deleting a goal does not mean the underlying files have been preserved.
A good cleanup leaves evidence where it belongs and no unexplained live state on the desktop.