DevSweep
Download

Changelog

Every release, what changed in it, and what the change was for.

0.0.10Current

3 October 2026

  • The size map on Overview shows what can be removed by default, coloured safe or review, with a switch to include protected data. Every item is named, on its tile when the name fits and otherwise in a short numbered list under the map. The age map uses one colour, darker with age, so green again means only safe.
  • Clean up's inspector says what an item is, where it is, what Clean does to it and how it comes back. The facts, the measurement and the evidence behind the recommendation are under Why?. In Projects, anything that blocks a cleanup stays in view and the reassurances move under Why?.
  • Projects, Duplicates and the cleanup sheets say the same in about half the words.
  • History shows your cleanups beside the detail of the one you select, with totals by outcome under the list. Settings is laid out in two even columns with half the text, and the privacy section still lists every request DevSweep makes.
  • Project names and ages are no longer cut short in the Projects list, and at the narrowest window the detail moves under the list. Duplicates counts skipped locations and identical files with the right singular and plural.
  • German, Portuguese and French use the same formal address throughout.
  • On the website, the demo shows these screens as the app does, including a project's worktrees, History's search and the privacy section.

0.0.9

2 October 2026

  • Sizes and counts are written in the same typeface as the text around them, with every digit the same width. In the monospaced face the decimal separator took a whole character, so large figures read "467 , 1".
  • Projects counts the same projects as Clean up: those without activity for a month. Its headline used three months, and said 467 MB where Clean up listed 9.3 GB.
  • Green is kept for what is safe to remove. A project whose cleanup is blocked, the menu bar total and a selection that includes items to review are no longer green, and the disk bar in the sidebar shows safe and review in their own colours.
  • In Settings, protected names such as Keychains and the name of the interface language are shown in full.
  • The size map names narrower tiles instead of leaving them blank.
  • The command line indents every path of an item under the first, and a dry run says what would go to the Trash instead of saying it went.

0.0.8

2 October 2026

  • DevSweep opens on Overview, which replaces Storage and Developer data. It leads with what can go now and a button that cleans exactly that, shows beside it how much is worth reviewing, and lists what can go from largest to smallest, each item marked Safe or Review. Protected items are listed too, and can never be selected.
  • Overview says what happens before you press Clean: safe folders are deleted outright, folders to review go to the Trash, and a tool's own command decides what it removes.
  • A partial scan is a one-line notice on every screen, with the locations that could not be measured a click away. It used to be a card above everything the scan had found.
  • Buttons and the Safe and Review labels are darker in light mode, so their text is easier to read.
  • On the website, the demo opens on Overview too, and its cleanup summary no longer says every item would go to the Trash: safe items are deleted outright.

0.0.7

2 October 2026

  • The command for putting a dependency folder back comes from the lockfile nearest it: pnpm install, bun install, yarn install, uv sync, poetry install or bundle install. It used to say npm install in a pnpm workspace, and pip install beside a uv.lock.
  • Putting a project back starts with reinstalling its dependencies, with every package manager it uses, instead of naming only its biggest folder.
  • Homebrew downloads measures only what brew cleanup removes. Homebrew's own index and the cache it runs from were counted as space the cleanup would free, and it does not free them. When a command is among the items to clean, the confirmation no longer says nothing else is touched: the tool decides what it removes.
  • Rust, Python and Go are recognised by their toolchains as well as their caches, so cleaning a cache no longer makes Settings say the tool is not installed.
  • Commands shown for copying are quoted for the shell, so a commit message with spaces is pasted as one message.
  • The time since a project was last changed reads as a duration in every language, and counts read correctly in the singular: one commit, one worktree.
  • History is fully translated, including its headline, its outcome filter and how each item was removed. The Portuguese app addresses you the same way throughout, and several Portuguese and German phrases are corrected.

0.0.6

28 September 2026

  • DerivedData and the Cargo registry are cleaned now, as the scan offers them. Both were skipped for safety because of a .git or a .env inside: the copies of Swift packages that Xcode checks out, and a crate published with a .env. Those belong to the package, not to you, and a .git or .env anywhere in your own projects still stops removal.
  • When another uv process is using uv's cache, such as a uv run that is still running, the cleanup says so straight away and says what to stop. It used to wait three minutes and then report only that the command had timed out.
  • The pip cache is removed as the folder the scan measured, so it is cleared whichever pip filled it. The older pip in Apple's developer tools cannot see the cache newer versions write, and reported that there was nothing to remove.
  • When a tool fails, the reason shown is the error it gave, not the first warning it printed. Homebrew prints a warning for every outdated formula before the error that stopped it.
  • The cleanup summary counts what a tool actually removed. A command that stops part-way is credited with what it did remove, and one that frees nothing is no longer credited with the scan's estimate.

0.0.5

28 September 2026

  • The purchase screen shows the launch offer while it lasts: the reduced price, the full price struck through, and how many licences are left at that price. It asks devsweep.app when the screen opens, and shows the full price if there is no answer.
  • Prices are written the way your Mac writes money, with the decimal separator your region uses.
  • Settings says exactly when DevSweep contacts devsweep.app: an update check, activating or releasing a licence, and opening the purchase screen. It used to call update checks the only request, which was not true.
  • The purchase screen no longer says a licence can be activated offline. Activating needs the internet once; DevSweep works offline after that.

0.0.4

28 September 2026

  • 0.0.2 and 0.0.3 were built from the code of 14 September. A packaging step took the app from a folder the compiler had stopped writing to, so both put new version numbers on old code, and most of what they list reached nobody. It all arrives with this version, and packaging now refuses to ship an app it has not just built.
  • As 0.0.3 announced, the scan stays free and removing needs a licence: the 5 GB of free cleaning ends with this version. Nothing you have already cleaned is affected.
  • The scan shows how far it has got: a ring that fills as each tool finishes, with the tools listed underneath and ticked off as they report back, in the middle of the window.
  • The parts of the app that still appeared in English in the other languages are translated: the scan summary, the cleanup results and the reasons an item was skipped, the purchase screen, and the window titles.
  • Settings has a Language section, so DevSweep can use a different language from the rest of your Mac.
  • In the menu bar, Review what would go opens the window, and Scan again shows that a scan is running instead of the previous total.
  • The cards in the right-hand column of Settings are all one width.

0.0.3

26 September 2026

  • Scanning is free forever, and a licence is what removing is for. The 5 GB of free cleaning is gone. Nothing you have already cleaned is affected, and the scanner still shows every location, every classification and every path without paying.
  • One purchase can cover several Macs. Buying more than one lowers the price of each, and a seat can be released from Settings under Plan to move it to another machine.
  • The permissions card now tells the truth about Full Disk Access. On macOS 27 it reported the access as off however many times you granted it, because it was checking a folder that version of macOS no longer creates. It asks several locations now, and one of them answering is enough.
  • Settings offers to reopen DevSweep after you grant that access. macOS hands an app this permission only as it starts, so granting it to a running DevSweep changes nothing until it opens again.

0.0.2

25 September 2026

  • Opens on the first double-click. A copy downloaded in a browser used to be held by macOS before it started: the icon bounced in the Dock, nothing was written to the log, and the only way through was buried in System Settings. That no longer happens, and the install window no longer has to warn you about it.
  • Offers to back up a project that exists only on this Mac — creating a private repository, or pushing what you have already committed. It asks first, and it never decides what goes into a commit.
  • Says what removing a whole project folder would cost. A folder counts as recoverable only when every commit is already somewhere else and nothing is uncommitted, untracked or stashed. Anything else is refused, with what would be lost listed item by item. DevSweep does not remove project folders.
  • Lists the other checkouts of a repository and what each one is holding, so removing one folder cannot quietly orphan another.
  • Says why each item is on the list. Every removable finding carries the reason it was offered: the threshold it crossed, the tool that reported it unused, or what makes it reproducible.
  • Finds leftovers from AI coding tools, including Claude Code and Codeium: working caches, the plugin marketplace cache, and downloaded browser binaries. Session transcripts and file history are measured and never offered for removal.
  • Links project folders that hold versions of the same work, with the reason attached. Nothing becomes removable because it resembles something else.