Disk space and cleanup
How Neoo keeps its local data within a storage budget, what it trims or removes and when, and how to reclaim space right now.
Neoo keeps your conversations, plus several kinds of data that grow with use: the full output of every tool your agents ran, a browser profile per conversation, a snapshot repository per project, the screenshots and images your agents produce, and the session files of the Codex and Claude accounts connected in Neoo. Neoo keeps all of it within a storage budget (5 GB by default), and you can run the same cleanup yourself at any time.
See what is taking space
- Open Settings, then Storage.
- The first card shows your Storage budget, how much Neoo uses (Used by Neoo) and for how many days it currently keeps full detail.
- The cards below show the database (conversations, messages, runtime events) and the Files on disk, one line per category with its number of items and its size.
Storage budget and full detail
Neoo keeps full detail for 30 days: every tool output, file and session stays as it was. Past that window, older data is trimmed or removed as described below.
While Neoo's data is over the budget, each cleanup pass shortens that window one step: 14 days, then 7, 3 and finally 1 day. Once usage drops below 70 % of the budget, it lengthens again one step at a time. The budget counts the database (excluding free space it can reuse), the migration backup and every file category below.
To change it, pick 2 GB, 5 GB, 10 GB, 20 GB or No limit in Settings → Storage → Storage budget. With No limit, Neoo keeps the 30-day window whatever the size.
What is trimmed or purged, and when
The database is maintained every 15 minutes, and the files shortly after startup and then every six hours. "The window" below is the full-detail window: 30 days, or fewer while over budget.
| Category | What happens |
|---|---|
| Tool outputs in conversations | Older than the window, a long output (command logs, file reads, diffs, files written by an agent) is reduced to its first and last lines, with a note that Neoo trimmed it. |
| Conversation browser profiles | Caches are cleared an hour after the browser closes; cookies and site data stay. The profile is removed when its conversation no longer exists, or after the window without using its browser. |
| Checkpoint repositories | Snapshots older than 14 days (or the window, if shorter) are dropped. While under budget, the 20 most recent of each project are always kept; over budget, they follow the window too. Repositories are compacted automatically, and one with no snapshot left is removed. A project that no longer exists is removed after the window. |
| Screenshots and tool images | After the window. |
| Provider transcripts | Codex and Claude session files of accounts connected in Neoo, once idle longer than the window. Unfinished Codex plugin installs are removed after a day. Your own ~/.codex and ~/.claude folders are never touched. |
| Migration backup | Three days after an update that migrated the database, once an integrity check passes. |
The database file only shrinks after a compaction. Neoo runs one automatically, at most once a day, when it can reclaim at least 512 MB, no agent has run for 30 minutes and the disk has room for the temporary copy. After that first compaction, freed space is returned to the disk gradually. During a compaction, Neoo also checks the index used to search your conversation history and rebuilds it if it is damaged; on a large history this can take several minutes.
Reclaim space now
In Settings → Storage, click Optimize storage. The same button trims older tool outputs, cleans and compacts the database, and runs a disk pass, then reports how much it freed. Compaction waits until no agent is running.
If some items could not be removed — a file locked by another program, for example — Neoo says so and retries on its next pass. You don't have to do anything.
On other computers and Neoo Cloud
Every computer cleans up on its own: the pass is local, with no server involved. A desktop starts purging as soon as it runs a version that includes this cleanup.
A Neoo Connect runner — another computer of yours, or a Neoo Cloud machine — applies the same rules to the browser profiles it creates, 90 seconds after it starts and then every six hours, at most 20 profiles per pass. A browser that is open, or one another Connect process still holds a lease on, is never touched. Connect keeps no checkpoint repositories.
A Connect machine that runs team work in its own copies of a project (one Git worktree per job) also removes the copies it no longer uses, at most once an hour and only between two runs:
| Item | Removed when |
|---|---|
| Worktree of a finished job | It has no uncommitted or untracked file, no Git operation in progress, no run and no process inside, and it hasn't been used for 12 hours (1 hour when less than 15 % of the disk is free). On a Neoo Desktop computer, 7 days (1 day when the disk is almost full). |
| Its local branch | Only when every commit is already in the project's default branch on the remote. Otherwise the branch stays, and the next run resumes from it. |
| Lock left by a crashed run | The process that held it no longer exists on this machine. |
| Codex transcripts of the accounts Connect manages on a hosted runner | 14 days after their last write. A later message in that conversation starts a fresh thread. |
The next run of a job recreates its copy at the same place, from the local branch, the branch already pushed, or the default branch. Only installed dependencies and caches have to be rebuilt.
An administrator of the machine can change these delays with environment variables on the Connect service: VATO_TEAM_CHECKOUT_IDLE_HOURS (1 to 2160), VATO_PROVIDER_SESSION_RETENTION_DAYS (0 turns it off, otherwise 1 to 365) and VATO_BROWSER_PROFILE_IDLE_DAYS (1 to 365).
What you lose
The purge is deliberate about what it gives up:
- Tool outputs: an older conversation shows the beginning and end of a long tool output instead of all of it.
- Browser caches: pages load a little slower the first time the browser opens again.
- Browser profiles: the websites that profile was signed in to. The conversation's browser still works; it starts from a clean profile and you sign in again.
- Checkpoints: you can no longer revert that conversation to a message older than 14 days (or the window). While under budget, the 20 most recent snapshots of each project stay available.
- Images: an older conversation no longer shows the screenshots and generated images in its transcript.
- Provider transcripts: when you continue an older Codex or Claude conversation, Neoo starts a new provider session and hands it the conversation's history from Neoo, instead of resuming the provider's own session.
Conversations, messages and your project files are never removed by any of this.