Is Devpit safe? What it protects and what it sends
Devpit deletes files and switches the accounts your tools use, so the rules are strict. They are not settings and not advice. The code enforces them, and a test pins each one. Where a rule is decided but its test is still to come, this page says so.
How deleting is protected
Section titled “How deleting is protected”- You see a preview first. Nothing is deleted before you have seen the list and the sizes.
- You must confirm. Deleting only starts after you answer a question.
- The default answer is No. Pressing Enter on a fresh question answers No. There is no way to build a dialog that starts on Yes.
- Careful items need a typed word. You must type
DELETEfirst. Pressing y is not enough. - You are told how to get it back. Every confirmation says how, for example run
npm install.
What is never pre-ticked
Section titled “What is never pre-ticked”- Careful items.
- Projects you touched in the last 7 days.
- Folders Devpit could not fully verify.
- Cloud placeholder files (OneDrive, Dropbox). Devpit skips them and never downloads them.
What Devpit checks before it deletes
Section titled “What Devpit checks before it deletes”- The marker file. A folder only counts as junk when its marker sits beside it:
package.jsonfornode_modules,Cargo.tomlfortarget, a.csprojor.slnforbinandobj. Devpit checks again right before it deletes. - Links are never followed. Junctions, symlinks and other reparse points are treated as dead ends. Following them is the bug that made other cleaners delete real source code.
- Places that are always refused: drive roots, anything inside the Windows folder, network paths, and every folder on your never-touch list.
- Devpit’s own program file is always refused.
- Current app versions are never removed. For Scoop, Devpit leaves the version that
currentpoints to, and never touchespersist. - Docker volumes are never touched. Devpit does not run any Docker command that includes volumes, in any spelling.
How deleting works
Section titled “How deleting works”- Safe items are first renamed to a temporary name in the same folder. The rename is instant. It shows straight away that the space is freed, and it makes a crash harmless: you can never be left with a half-emptied folder that looks like a working one. A small marker file inside says which folder it was. Devpit finishes the removal later, from Resume interrupted deletes, and only for folders with that marker.
- Review and Careful items go to the Recycle Bin, so you can restore them.
Stopping is safe
Section titled “Stopping is safe”Press Esc during a delete. Devpit finishes the item it is on and shows what was done. Finished deletions stay done. Nothing is left half removed.
Nothing fails quietly
Section titled “Nothing fails quietly”A locked folder, a folder you cannot read, a cancelled scan: each one is counted, named and explained on the summary, with what to do about it. For example: “Couldn’t delete api\node_modules — it’s open in Code.exe. Close it and press R to retry.”
Other protections
Section titled “Other protections”- Processes. Devpit never stops PID 0 or 4, Windows services, or other programs in
C:\Windows\System32. The shellscmd, PowerShell andconhostare the one exception, because dev tools start them all the time. See Fix stuck ports and apps. - SSH keys. An existing key is never overwritten. A key Devpit makes for a GitHub account gets its own file name, and Devpit stops if a file is already there. See Git and GitHub accounts.
- Admin rights. The app you type into never runs as administrator. Jobs that need it, such as Chocolatey updates, run in a separate small helper that asks Windows for permission once. The helper only accepts a short list of jobs, and only deletes inside a short list of Windows temp folders.
- Settings file. A damaged file is renamed and kept, never silently thrown away. A file from a newer Devpit is refused, not half applied. Saving is done in a way that never leaves a half-written file.
Accounts
Section titled “Accounts”Accounts changes which account Claude Code, Git, GitHub and other tools use in a folder. These rules apply to it.
No tokens
Section titled “No tokens”- Devpit stores no token. Each tool keeps its own login where it always does. Devpit’s rules file,
%APPDATA%\devpit\accounts.toml, holds account names, emails and folder paths only. - No token is shown, copied, logged or put in
--jsonoutput. Who is signed in is read without the token, and everything Devpit shows or logs is checked for anything that looks like a secret. A test plants a fake token in fake tools and checks it never comes out. - The one token Devpit handles is a GitHub account’s, which it asks
ghfor when aghorgitprocess starts. It goes only to that process, in memory, and is never written anywhere. If anything goes wrong,ghstarts untouched with one warning. - No command that prints or moves a token is ever run: never
firebase login:list --json, nevergh … --show-token, nevergh auth switch. - Login files are never read, copied or linked: Claude Code’s
.credentials.jsonand Supabase’saccess-token. Only whether they exist is checked. Claude Code’s.claude.jsonis never copied or linked either; only its MCP server entries are read, when you choose to bring MCP servers over.
Every change can be checked and undone
Section titled “Every change can be checked and undone”- Every change has a preview, and the default answer is No. What is applied is exactly what you saw: if anything changed in between, Devpit stops.
- Undo is exact. Devpit records each change before it makes it, with what was there before. Undo puts it back. If a file Devpit wrote was changed by hand since, undo stops and changes nothing.
- A crash never leaves a change half made. A change that was not finished is put back at the next start.
- An account folder that holds a sign-in is never deleted by an undo, and a cancelled sign-in leaves nothing behind.
- Nothing you type can add lines to Git’s config. A name, email or path with a line break is refused.
- Without a terminal, nothing changes without
--yes. A script or an AI agent gets exit code 3 and the message “This would change … Re-run with –yes after the user agrees.” Variables such asCIorCLAUDECODEnever stand in for a person.
What it touches, and what it leaves alone
Section titled “What it touches, and what it leaves alone”- Login and account folders can never be selected in Free Up Disk Space:
.claude,.ssh,.devpit,.claude-switch, and thegh, Vercel, Wrangler, Supabase and Convex login folders. Account folders Devpit makes live inside.devpit. devpit accounts cleanupremoves only what Devpit added: folder rules, shims and their PATH entry, its Git files and include block, the Wrangler bindings it made and its agent skill. Never an account folder or a sign-in.- Sharing a Claude Code setup never overwrites anything in the other account: same-named items are kept beside it, renamed, or moved to a backup folder. Links are never followed when removing.
- Uninstalling never breaks an account. Shared links point at your own
.claudefolder, anddevpit accounts cleanup --copy-linksturns them into copies. - Careful items (MCP servers, which may hold API keys) are never ticked for you and are only copied on the Careful path. That they ask twice on screen is decided, but the screen’s test is still to come.
- Arguments reach a tool exactly, or not at all. A shim never passes your arguments through
cmd.exein a way that could change them: npm tools run asnode.exedirectly, and other batch files only get plain arguments. - A broken Devpit never blocks a tool. If the shim cannot work out the account, it starts the real tool untouched with one warning line.
- Claude Code’s idle accounts are not asked who they are unless you agree, because on some versions that check can sign an idle account out (Claude Code issue #95822).
No network of its own
Section titled “No network of its own”Accounts has no network code. The only connections are each tool’s own sign-in and “who am I” check, which the tool makes itself.
This PC (PC specs)
Section titled “This PC (PC specs)”PC specs in Settings reads what the PC is made of. These rules apply to it.
- It only reads. It changes nothing on the PC. The engine has no network code, so nothing is sent anywhere.
- Serial numbers and MAC addresses are shown on screen. Copying or saving the report asks “Include serial numbers and MAC addresses?” first, and the default answer is No.
- The Windows key stored by the PC maker is never read out. The page only says whether Windows is activated.
- Missing data is never judged. A value the PC does not report never becomes a Buyer’s check flag.
- A save never overwrites a file. Nothing is saved without a key press and a yes.
- The one admin prompt is optional. It reads the drive’s wear and power-on hours, runs a fixed read with no arguments, and you can say no.
Share Files and the direct hotspot
Section titled “Share Files and the direct hotspot”Share Files can start a Wi-Fi hotspot on the sharing PC so the other PC joins it directly. It starts one only when you pick it, and never when your hotspot is already on. It opens file sharing for the hotspot’s own network only, with one firewall rule that it removes by name when you stop. The password it makes for a temporary hotspot is 8 digits, which is weak on purpose, so use it only with people you trust nearby. If you use your own saved hotspot instead, its password is shown on the card and never saved, logged or sent to Devpit’s admin helper. On the other PC, Devpit deletes only the Wi-Fi entry it added and puts the PC back on its own network. Anyone who joins the hotspot also gets internet through the sharing PC while it is on. Devpit stops the hotspot it started, also after a crash, with one stated limit that the Share Files page explains.
Extract archive in place
Section titled “Extract archive in place”Extract a big archive in place runs the free tool hatchzip (by xevrion, MIT or Apache 2.0), which removes the archive as it writes the files. Devpit never touches the archive’s bytes itself. These rules apply to it.
- A check first, then a yes. hatchzip checks the space, and an extraction starts only after that check passed for exactly that archive and you answered yes. The answer is No by default, and the question says the archive is removed as it goes. If the check says no space, damaged or anything else, nothing is run and nothing changes.
- Devpit only looks at file sizes. While hatchzip works, Devpit never opens the archive or a file being written. It reads sizes and folder names, which is how it draws the progress.
- Only a local file. Network paths and mapped drives, links and junctions, the Windows folder, Program Files, ProgramData and login or account folders are refused. The output is a new folder beside the archive, never a drive root and never someone else’s non-empty folder.
- The passwords you type stay private. An archive password goes to hatchzip only through its own environment, for that one run. It is never on a command line, on screen, in a log, in Devpit’s own settings or saved anywhere, and Resume asks again.
- hatchzip’s own files are left alone. Devpit never deletes, moves or edits the small files hatchzip keeps beside the archive to resume. Full Scan never lists them, and deleting an archive with an unfinished extraction is refused with a plain reason.
- Pause before stop. Esc, Ctrl+C and quitting ask hatchzip to pause first, then ask again, and end it only after that. A stop Devpit caused is shown as stopped and resumable, not as a failure.
- Automatic resumes, and it says so. If hatchzip reports the disk full too early, a known hatchzip issue, Devpit resumes it by itself while each try makes progress, up to 20 times, and shows how many times it did. It never does after its own pause or stop.
- The exit code decides. hatchzip’s text only describes. An unknown line never changes a verdict, sizes say “about”, and the bar never reaches 100% before hatchzip has finished.
- Installing hatchzip asks first. It is installed with Scoop only after a yes (default No) on a screen that shows the exact commands. The Scoop bucket comes only from Devpit’s built-in list.
- Safe to stop, with a limit. hatchzip saves its progress, and pauses and a hard kill were both resumed on the one Windows 11 PC this was tested on. That is not a promise for every disk, and a power cut was not tested.
What Devpit sends
Section titled “What Devpit sends”Short version: usage stats are off until you turn them on.
Everything else runs on your PC: the scan, the sizes, the deleting, the port list and your settings. Devpit reads and writes these places, and nothing in them is uploaded:
| What | Where |
|---|---|
| Settings | %APPDATA%\devpit\config.toml |
| Account rules and the undo history | %APPDATA%\devpit\accounts.toml, %APPDATA%\devpit\accounts-journal.jsonl |
| Account folders Devpit made | %USERPROFILE%\.devpit\accounts\ |
| Git rule files | %USERPROFILE%\.devpit\git\ |
Caches and logs, and the list of unfinished extractions (extract-jobs.json, no passwords) |
%LOCALAPPDATA%\devpit\ |
Usage stats (off by default)
Section titled “Usage stats (off by default)”On first run Devpit asks, with the answer already on No:
Help show how much space Devpit saves? Only totals are sent — no file names or paths.
You can change your mind in Settings, then Usage stats.
If you turn it on, Devpit sends one small report after a clean-up that removed something. It is sent in the background to https://devpit.zubyr.dev/api/report. This is the whole report:
| Field | What it holds |
|---|---|
v |
The version of the report format (1) |
installId |
A random ID made on your PC. It is not made from your machine, user or network |
version |
The Devpit version, for example 0.2.0 |
os |
The operating system name, windows |
osVersion |
The Windows version number, for example 10.0.26100 |
freedBytes |
How many bytes were freed |
items |
How many items were removed |
types |
How many items of each kind were removed, by the short name of the rule that found them, for example node_modules. A name that is not a short plain name is dropped, not sent. At most 32 kinds |
What is never sent:
- File, folder or project names
- Any path
- Your user name, machine name or domain
- The contents of any file
- The apps or tools you have installed
- Anything at all when a scan finds nothing, or when you cancel
How it behaves. A report never slows you down. If you are offline or the server is slow, it is dropped quietly. It is not retried and not saved to disk. The server rejects impossible numbers. It keeps a hashed form of your IP address for at most one hour, only to limit how many reports one connection can send.
The totals are shown on the Devpit website as public counters: space freed, items by type and how many people use it.
Turn stats off for good
Section titled “Turn stats off for good”Any one of these:
- Leave Usage stats off in Settings.
- Set
DEVPIT_NO_TELEMETRY=1in your environment. - Set
DO_NOT_TRACK=1in your environment.
The two variables always win, even if the setting is on. Devpit never asks in a run without a screen, and never turns stats on by itself.
# for this terminal only$env:DEVPIT_NO_TELEMETRY = "1"
# for your user account, from now on[Environment]::SetEnvironmentVariable("DEVPIT_NO_TELEMETRY", "1", "User")Every other connection Devpit makes
Section titled “Every other connection Devpit makes”These are not usage stats. Each one happens only for the reason given.
| When | Where to | What it is for |
|---|---|---|
| Once a day, if the update check is on | api.github.com (public releases of Devpit) |
To see if a newer version exists. Nothing but the web request is sent. The answer is cached on your PC. Turn it off in Settings or with DEVPIT_NO_UPDATE_CHECK=1. A build made from source never checks |
| You open My IP addresses | api.ipify.org, then ifconfig.me |
To show your public IP address |
| You install the icon font | github.com (a fixed Nerd Fonts release) |
To download the icon font. The file is checked against a fixed SHA256 before it is used |
| You run the installer or update | github.com |
To download the release and its checksums |
| You use Install or Update, or install hatchzip for Extract in place | The sources of Scoop, winget, Chocolatey or npm | These tools contact their own servers. Devpit only runs their commands |
| You ping a host | The host you typed | That is what ping does |
| You add, check or use an account | That tool’s own servers | The tool’s own sign-in and “who am I” check, run by the tool itself (for example gh api user or vercel whoami) |
Devpit never downloads or replaces itself. When a newer version exists it only tells you the command to run.
Check what you download
Section titled “Check what you download”- The install script is short and readable at
devpit.zubyr.dev/install. - It checks the SHA256 of the zip against the
checksums.txtthat comes with the release. - Releases are built on GitHub Actions and carry a build attestation and a software bill of materials.
- Devpit is not code-signed yet, so Windows SmartScreen may warn about an unknown publisher. Devpit is never packed with UPX, because packed programs trip antivirus scanners.
To check a zip yourself, see Getting started.
Read the rules
Section titled “Read the rules”The full table of safety rules, and the test that pins each one, is in the repository:
If what Devpit collects ever changes, the privacy policy changes in the same release, the release notes say so, and anyone who had opted in is asked again.
Common questions
Can Devpit delete something by accident?
It is built so it cannot. Nothing is deleted without a preview and an explicit yes, the default answer is always No, and Careful items also need a typed word. Safe items are renamed before they are removed, and the other items go to the Recycle Bin.
Does Devpit store my tokens or passwords for Accounts?
No. Each tool keeps its own login where it always does. Devpit's rules file holds only account names, emails and folder paths. The only token Devpit ever handles is a GitHub account's, passed in memory from gh to the one gh or git process that needs it.
Does Devpit collect my data?
Not unless you turn usage stats on. They are off by default. If you turn them on, one small report of totals is sent after a clean-up that removed something. It never contains file names, paths, your user name or your machine name.
How do I make sure nothing is ever sent?
Set the environment variable DEVPIT_NO_TELEMETRY=1 or DO_NOT_TRACK=1. Either one turns usage stats off whatever the setting says. Keep Usage stats off in Settings too.
Does Devpit connect to the internet at other times?
Only for things you can see: a once-a-day check of GitHub for a new version, the public IP lookup when you open My IP addresses, the icon font download when you install it, and the package managers you run. The page lists each one.
Is Devpit code-signed?
Not yet. Windows SmartScreen may warn about an unknown publisher. Releases have SHA256 checksums and a build attestation so you can check that a file is the one GitHub built.
