Storage and Cleanup

Use Settings → Storage to inspect workspace folders across projects. Switch to General scope if you have a project selected.

Choose the action for the data you want to remove:

Action	Removes	Keeps
Delete a workspace	The workspace entry and its Tarsk-managed folder, subject to the project-root rules below	External folders, remote repositories, and other workspace folders
Clear history	Conversation records and agent sessions across projects, plus unreferenced stored observation files	Workspace files, project and thread entries, settings, and logs
Delete Account	The local Tarsk database and its SQLite sidecars; clears the log feed and removes the file log	Workspace folders and other files outside those deletion targets

Save work and export conversations you need before deleting them. Tarsk has no undo for these actions.

Delete a Workspace

1. Open Settings → Storage.
2. Find the workspace by Project, Path, or Branch. Click a column heading to sort. Click the path to open it in Finder or Explorer.
3. Click the row’s trash button, then confirm Delete in Delete workspace?.

Tarsk hides the row’s delete button during processing or deletion, and while the thread has a completion indicator. Manual workspace deletion does not require a clean working tree. You can lose uncommitted files and commits that exist in that clone.

Folder and History Scope

Tarsk checks the workspace path against its managed data directory:

• For a thread-specific clone inside that directory, Tarsk removes the folder and its contents, including the clone’s Git data.
• For a workspace that shares the project-root path, Tarsk keeps the folder while other threads remain. If you delete that root workspace with no remaining threads, Tarsk removes the project entry and deletes the project folder if it lies inside the managed data directory.
• For a path outside the managed data directory, Tarsk keeps the folder and its files. This includes an external folder you chose through Open Folder. Tarsk removes its workspace entry and, if this was the root workspace with no remaining threads, its project entry.

Tarsk does not delete remote branches or remote repositories through workspace deletion.

For a thread deletion that keeps the project, Tarsk marks the thread and its conversation records as deleted and removes its agent sessions. The conversation records remain in tarsk.db. The project-root deletion described above also removes the project’s conversation records and collects its unreferenced observation files. Use Clear History to purge conversation records across projects.

External Open Folder paths

In the chat’s Workspaces menu, Tarsk warns that it did not create the external project-root folder. The server keeps that external folder if you confirm deletion. In Storage, you see a generic warning about deleting files; Tarsk keeps external folders through this delete control too.

Cleanup Stale Workspaces

Open the branch picker in the chat window footer and click Cleanup stale branches (the refresh icon). Tarsk checks workspaces in that project and deletes qualifying entries without a per-workspace confirmation.

A workspace qualifies through either condition:

• Merged pull request: Tarsk finds a merged PR for the recorded branch and a working tree with no uncommitted changes. Unpushed commits do not protect a workspace in this case. Review commits you made after the merge before using cleanup.
• Missing local branch: The recorded local branch ref no longer exists, the checkout has a detached HEAD, and the Git operations button has no action available. Tarsk keeps workspaces with uncommitted changes, unpushed commits, an open PR, commits ahead of the default branch without a PR, pending synchronization with the default branch, or a Create Repo action.

Tarsk keeps a workspace if you have switched or renamed its checked-out branch so it differs from the recorded branch. It skips missing branch names, unresolved Git roots, unavailable Git status, and checks that exceed ten seconds. Cleanup excludes the external Open Folder project-root workspace and uses the same deletion path as manual workspace deletion for the remaining candidates.

Uncommitted changes are the most common keep-reason, so the branch picker dots those workspaces in the same list and names the reason on hover. Other keep-reasons still only appear in the logs.

Check the result toast for deletion failures. Open Logs for failure details and skipped-workspace warnings.

Clear History

1. Open Settings → History in General scope.
2. Open the ⋯ menu labeled Choose columns.
3. Select Clear history, then confirm Clear.

Tarsk clears conversation history across all projects, including records that thread deletion marked as deleted. The action covers more than the rows on screen. Tarsk disables the menu item when the history list has no conversations.

Tarsk deletes the conversation records and agent sessions, including their stored session entries and usage data. It attempts to remove stored observation files that have no remaining references. Tarsk uses these files for large tool results and messages; it logs file-removal failures and keeps those files.

Your workspace files, project and thread entries, project notes, settings, and logs remain. Tarsk keeps tarsk.db; clearing history does not promise a smaller database file or a secure disk wipe. See Conversation History for export instructions.

Delete Account

Open Settings → Account, click Delete Account, and confirm. If Tarsk lists workspace folders in Storage, you see a warning and a Go to Storage button. The warning does not block account deletion. Delete unwanted managed workspaces first if you want to reclaim their disk space.

Tarsk closes its database connection and attempts to remove:

• tarsk.db from its data directory, including the records and settings you stored in that database.
• SQLite sidecars tarsk.db-wal and tarsk.db-shm.
• tarsk-logs.txt from its application-support directory, if an older version left one behind. Tarsk also clears the in-memory log feed.

Tarsk leaves workspace folders, external Open Folder directories, and other filesystem data in place. This includes stored observation files under the data directory’s observations/ folder. Use Clear history before account deletion if you want Tarsk to collect unreferenced observation files. Account deletion does not run that cleanup, delete remote repositories, or cancel purchases with a billing provider.

After deletion, Tarsk requests that the desktop app quit or the browser window close. You can relaunch the app; Tarsk creates a database on the next database access. Browsers may refuse to close the window. File-removal errors go to the logs and may leave deletion targets on disk, so do not treat Delete Account as a verified disk wipe.