Manage local storage
Open Settings → All projects → Storage for retention, cleanup, running processes, and backup and restore. Database inspection and JSON export are under Privacy & data.
Keep finished worktrees longer
Section titled “Keep finished worktrees longer”In Retention → Keep Done worktrees for, set the number of days. This controls when Volli can reclaim an eligible, clean worktree folder. It keeps the ticket, branch, commits, and pull-request link.
Use Keep worktree on a ticket to exempt its folder. See Clean up worktrees for eligibility and the difference between removal and archiving.
Inspect leftover processes
Section titled “Inspect leftover processes”- In Running processes, select Look for processes no Session owns.
- Review each result’s ticket, command, age, and memory information.
- Use Reap to stop an eligible process or Reap all for the eligible results.
Some processes appear without a removal action. Reap under memory pressure controls automatic cleanup of eligible leftovers. Stopping a process does not delete its files.
Remove build artifacts
Section titled “Remove build artifacts”In Clean up, Scan unused files shows a summary. Select Review cleanup to inspect and confirm individual cleanup actions.
In that dialog’s Build artifacts section, use Scan for build artifacts to inspect ignored dependency folders, build output, and caches. Review the results before Trim. Volli protects local configuration and active or dirty worktrees. A trim keeps the checkout and branch, but you may need to reinstall dependencies before working there again.
Trim when a ticket is done controls automatic build-artifact trimming.
Remove orphaned logs and worktrees
Section titled “Remove orphaned logs and worktrees”The Review cleanup dialog also contains:
- Pi session logs, where Scan for orphaned Pi logs finds logs no longer referenced by a Session. Saved tool output shows the bounded store of larger tool results.
- Orphaned worktrees, where Scan for orphaned worktrees checks for checkout folders that no ticket owns.
Scans cover the local installation, not only the selected project. Review the results before confirming cleanup. If retention or the folders change after a scan, scan again before acting.
Back up local data
Section titled “Back up local data”Volli creates local profile backups daily while it is running. In Storage → Backups, Last backup shows the latest completed backup and its size. Select Back up now for another snapshot, or Show in Finder to open the backup directory.
Automatic retention keeps up to seven recent daily snapshots and an older weekly snapshot. A failed or skipped attempt appears beside its recovery action; it does not replace the last successful backup.
Backup bundles include board and Session history, saved Automations, settings, attachments, and transcript artifacts. They do not include:
- Repository files or worktree folders, including uncommitted changes.
- Credentials, provider sign-ins, or MCP tokens.
- Browser captures and replay files, diagnostic logs, or runtime scratch.
- Personal Command files in the current version of the bundle format.
Keep repositories, personal Skills and Commands, and the backup directory in your normal Mac backup plan. Local bundles on the same disk do not protect against losing that disk. See Local data and network access for storage locations.
Restore a backup
Section titled “Restore a backup”Restoring replaces local history with the selected backup. It leaves project files in place. Keep any newer history you need before proceeding.
- In Storage → Backups, select Restore… beside a bundle, or use the Restore row to choose a backup file.
- Volli checks the bundle. Review any reported problems before continuing.
- For each project, use Choose… to confirm its repository directory, then select Prepare restore.
- When the dialog says Ready to restore on restart, review the credential notice and select Restart and restore.
Use Cancel restore to stop before restarting. After a restore, Previous profile → Show in Finder reveals the profile Volli replaced.
Credentials already stored in the destination profile stay there. Credentials that existed only on the source machine must be supplied again. A backup does not restore live processes or the source machine’s worktree paths.
Export records for inspection
Section titled “Export records for inspection”- Open Settings → All projects → Privacy & data.
- In Database → Export data as JSON, select Export….
- Read the confirmation and choose a location.
The JSON export contains readable project, ticket, comment, Session, and label records. It excludes attachments and transcript files and cannot be restored. Use the backup bundles above for restoration.
Reveal in Finder shows the database location without copying it. If you make a manual copy of the application-data folder, quit Volli first. Copying only the SQLite file can miss recent writes and related files.