Reference
Where the files live
Everything Deck keeps sits in a single folder on your computer. Knowing the path helps you back it up, fix problems and walk away without leaving anything behind.
The data folder
| System | Path |
|---|---|
| macOS | ~/Library/Application Support/Deck |
| Windows | %APPDATA%\Deck |
That folder belongs to Deck alone. Deleting it takes the app back to a freshly installed state, without touching your repositories.
What is inside
| Item | What it is |
|---|---|
deck-state.json | The app state: projects, contexts, sessions, pane layout and preferences. |
backups/ | A daily copy of the state, in case the main file is lost. |
window-state.json | Window size and position. |
prompts/ | The prompts you saved to reuse. |
goals/ | The goals written for each project. |
themes/ | Your own themes, on top of the ones that ship with the app. |
rascunhos-editor/ | What you typed in the built-in editor and have not saved yet. |
github/ | Preferences, cache and pull request review folders. |
deck-tarefas.json | The tasks pulled in from ClickUp and from GitHub. |
segredos.json and conta/ | Connection tokens and the account credential, encrypted by the system keychain. |
worktrees/ | The isolated work folders, when you choose to keep them here. |
| Scripts and logs | The notification scripts for the agents and the logs of the service that keeps sessions alive. |
The files that hold secrets are encrypted by the macOS Keychain or by Windows DPAPI. Copying those files to another machine does not carry the token along: it does not open outside the computer that encrypted it.
What the app reads outside it
To build the status line and to know when an agent is asking permission, Deck reads what the agents themselves already write in your home folder:
- The conversation history and the Claude Code configuration file, in
~/.claude. - The Codex session logs, in
~/.codex.
Deck also writes to the Claude Code configuration file to register the notifications and the status line, keeping a copy of the previous state next to it. You can undo that in Settings, and it is explained in Agents.
Worktrees
The isolated work folders do not have to sit in the data folder. In Settings you choose between keeping them there, next to the repository, inside it or at a path of your own. Whichever you pick, they are plain git folders: deleting Deck deletes none of them.
How they are created and how they are removed is covered in Isolated tasks.
Backup
To keep the way you have your Deck set up, copy the data folder with the app closed. What matters is in the state and in the prompts, goals and themes folders.
# macOS
cp -R ~/Library/Application\ Support/Deck ~/Desktop/backup-deckRestoring is the same path in reverse, also with the app closed. The credential and the tokens do not cross over to another machine, so there you sign in again and reconnect.
Start from scratch
- Close Deck.
- Rename the data folder instead of deleting it, until you are sure you will not need it.
- Open the app again. It comes up clean, asking you to sign in.
On macOS, sessions that were in the Deck tmux stay up even after that, because they do not live in this folder. If the idea is a real reset, end the sessions first.