devpit
Everything devpit keeps is in ~/.devpit, on this computer — %USERPROFILE%\.devpit on Windows. Your work is never uploaded, and sync between machines is not built. That folder belongs to you and not to the package, so reinstalling devpit — in any format — opens exactly where you left off.
What is in it
| Path | What it holds |
|---|---|
~/.devpit/state.db |
The store: projects, boards, cards, runs, notifications and settings. |
~/.devpit/projects/<name>-<suffix>/ |
One per project: its conversations, terminal history, pasted pictures, capability files and artifacts/. None of it is in the repository. |
~/.devpit/orchestrator/<name>/ |
One per orchestrator: its brief, your CLAUDE.md, and what it keeps in context/, decisions/, docs/ and artifacts/. |
~/.devpit/worktrees/ |
Card checkouts, one folder per project and card, unless Settings → Worktrees puts them elsewhere. |
~/.devpit/browser/ |
The browser pane's named sessions: cookies, storage and logins. |
~/.devpit/agents/ |
Your own agent files. They are read first, so one of yours shadows a plugin's of the same name. |
~/.devpit/repos/ |
Where Clone a repository puts a clone, unless you choose somewhere else. |
~/.devpit/account-token |
The device token, if you signed in. Readable only by you, and never shown on screen. |
~/.devpit/hooks.json |
The hook settings devpit hands to the agents it starts, so it can show their status. It is not written when Agent status hooks is off. |
~/.devpit/gemini-hooks.json |
The same, for Gemini CLI in devpit's terminals. |
~/.devpit/remote-devices.json |
The devices paired for Remote, with what each may do. |
~/.devpit/remote-log.jsonl |
Who connected through Remote and what they did, never what was on screen. |
~/.devpit/transcribe-key |
The key of a transcription service for voice messages, if you chose one. Readable only by you. |
~/.devpit/logs/errors.jsonl |
devpit's own errors, kept only while Error reports is on. |
The sidebar's Files row browses this folder from inside devpit, starting at the open project's folder, with a name filter and sorting. Resources → Workspace folder shows what it holds and how much room each part takes.
What is not in it
- Your code. A project is read where it is and never moved, and removing a project from devpit leaves the folder, the git repository and the history untouched.
- Your agent CLI's own configuration. Agents, skills and MCP servers are read live from wherever your tooling keeps them. devpit references them, never copies them, so there is no second copy to go stale.
- The transcript of a session. The agent CLI writes it; devpit writes down where it is.
Card checkouts land in ~/.devpit/worktrees/ by default, and Settings → Worktrees can put them anywhere else. See Worktrees.
Error reports
Error reports, in Settings → General under Updates and privacy, is off unless you turn it on. With it on, devpit keeps its own errors — panics, internal errors of its commands, background routines that fail, errors the window did not catch — and sends them anonymously to devpit.app so bugs can be found and fixed:
- what is kept is cleaned as it is written: no paths, no credentials or tokens, no names quoted by git or the shell, no text from your cards, prompts or terminals;
- a report carries the error and devpit's version, OS, architecture and package type — no account, even when signed in, and no install id;
- reports go out only while devpit sits idle, five at a time, and pause when you come back;
- Show what would be sent shows the exact request the next report would send;
- turning it off deletes everything kept, at once. Kept errors never grow past 200 entries or 256 KB, and are dropped after fifteen days, on the server too.
Secrets
Secrets devpit handed out are taken out of a run's output before it is stored: a profile's environment, the account token, the hook secret. This is not detection. A secret a command read from a file or fetched itself is one devpit never saw, and it passes through.
A profile's environment variables whose names look like secrets are masked on screen until you ask to see one. See Profiles.
Deleting things
To remove one project's data, remove it in Settings → Projects and tick Also delete this project's devpit workspace. Your code is still not touched, and this cannot be undone.
Uninstalling devpit removes the app and nothing else:
.deb:sudo apt remove devpit- AppImage:
rm ~/.local/bin/devpit ~/.local/share/applications/devpit.desktop ~/.local/share/icons/hicolor/*/apps/devpit-desktop.png - macOS:
rm -rf /Applications/devpit.app - Windows: Settings → Apps → devpit → Uninstall
To erase everything, remove ~/.devpit (or %USERPROFILE%\.devpit) as well — and ~/.devpit-dev, if you ever ran a development build.