chippytea README

The project's README from github.com/richiemcilroy/chippytea. As one markdown file: README.md.

chippytea

Free up space on your Mac.

chippytea is an ultra-performant, native macOS app that clears space on your Mac. Built with SwiftUI and Rust, it helps you find app caches, developer tools, old build folders and downloads you may no longer need. Review their estimated sizes, see what removing them means, and choose what to keep or remove.
SwiftUI + Rust · macOS 14+ · Free and open source

Build it · How it works · Contribute · Security

Illustrated example: review an old node_modules folder, then turn 1.2 GB of credited space into 12 golden chips in a paper tray.

An illustrated cleanup, not a live scan. Animation respects reduced motion.

chippytea runs locally from your menu bar. No account, no telemetry, no automatic deletion.

How it works

  1. Find cleanup opportunities. Scan folders you choose, or use Scan my Mac for app and developer caches, logs, Xcode data, Python bytecode, build folders, downloads and large personal files. It also checks known system and tool-managed storage locations automatically.
  2. Check before you clean. Review the files, estimated size, and consequences. Git and activity checks vary by category; personal files and caches without an identified owning app still need your judgment.
  3. Choose what to remove. Move files to Trash, or permanently remove eligible developer caches, build files and dependencies. Review the outcome and any credited space in the cleanup history.

Check duplicate files compares already-indexed old/large personal-file suggestions when you ask. It verifies contents, lets you choose one copy to keep and one to review, and rechecks both before moving the selected copy to Trash. This is a bounded check, not a whole-Mac duplicate search; ordinary scans never hash personal-file contents.

Moving files to Trash does not free storage. App caches, logs, Python bytecode, Xcode DerivedData, downloads and personal files are review/Trash-only; they never earn chips. Verified developer caches, build files and dependencies can be deleted permanently after their ownership, activity and contents are rechecked.

Known npm, npx, Corepack, Bun, pip, uv, mise, Cargo, SwiftPM, Zig, Expo, Homebrew download and AWS CLI caches appear in the same cleanup list, with the same checkboxes and review action. Only recognized cache directories are eligible; active tools, shared files and unrelated configuration stay protected. Blocked caches stay in the list with their reason and cleanup disabled. Installed toolchains, container data and system locations appear alongside cleanup findings with their relevant review steps. Their measured size does not establish how much is removable; some system locations need administrator access.

Use Settings → Scan locations & access to add a folder or mounted drive, reconnect an unavailable location, or redo access setup. Saved volume identities handle macOS device-number changes without renewing a valid folder grant. Older grants that are already invalid need one explicit reconnection; Keep choices and cleanup history are preserved.

This is early software that can permanently delete files. Start with a disposable test folder and keep backups. Full Disk Access is optional.

About the chip counter

The chips are a decorative counter for space saved. Eligible permanent cleanup adds one chip per 100 MB of conservatively credited space. Smaller amounts carry forward.

Chips stay on your Mac and have no monetary value. Moving files to Trash adds no chips; estimated sizes never update the counter.

Build and run

You'll need an Apple Silicon Mac, macOS 14 or later, Xcode with its command-line tools, Python 3, and a Rust toolchain.

git clone https://github.com/richiemcilroy/chippytea.git
cd chippytea
./scripts/build.sh
open build/chippytea.app

Local builds are ad-hoc signed by default, not notarized releases. Quit the running app before rebuilding.

env -u CARGO_TARGET_DIR -u CARGO_BUILD_TARGET_DIR cargo test --locked
cargo clippy --all-targets --locked -- -D warnings

Working on the landing page? See site/README.md.

Project structure

Part What's inside
Rust engine Bounded discovery, SQLite index, safety checks, cleanup, and a durable reward ledger
Native app SwiftUI interface, menu-bar panel, Finder and Trash integration, hand-drawn fish and chips
Landing page The same drawing paths and chip-shop style, built with Next.js
Tests and benchmarks Disposable fixtures, native integration checks, and reproducible performance tools

Contributing

Bug reports, careful safety tests, clearer docs, and small fixes are welcome. Read CONTRIBUTING.md before changing cleanup behaviour. Please keep personal paths, logs, and credentials out of public issues. Security problems belong in a private report.

MIT licensed.

chippytea (richiemcilroy/chippytea)

Searching Database…

What is this?chippytea is a native macOS app that finds and clears app caches, developer tool caches, old build folders, logs and downloads to free up disk space, built with SwiftUI and Rust.
Is this a system cleaner app, not just a scanner script?It is a full desktop app with a SwiftUI menu-bar interface backed by a Rust engine that handles scanning, safety checks, a SQLite index, and cleanup logic.
How do I get it running?You build it from source: you'll need Xcode with command-line tools, Python 3, and a Rust toolchain, then build and run the app, which is ad-hoc signed locally rather than a notarized release.
Is it safe to just let it delete things automatically?No — this is early software that can permanently delete files, so you should start with a disposable test folder and keep backups; only verified developer caches and build files can be permanently removed, while personal files and unidentified caches require your judgment.
Is this for regular Mac users or mainly developers?It targets developers in particular, since it specializes in finding developer tool caches (npm, Cargo, Homebrew, Xcode DerivedData, Python bytecode, etc.) alongside general caches and downloads.
Does it phone home or need an account?No — it runs entirely locally from your menu bar with no account and no telemetry.
What happens to files it finds — are they deleted right away?No, you review estimated sizes and consequences first, then choose to move files to Trash or permanently remove eligible developer caches, build files and dependencies; Trash moves do not free space immediately.
What are the chips about?Chips are a purely decorative counter: eligible permanent cleanup credits one chip per 100 MB conservatively saved. They have no monetary value and stay on your Mac.
Can it find duplicate files?Yes, a bounded 'check duplicate files' feature compares already-indexed old/large personal files, verifies contents, and lets you pick which copy to keep, but it is not a whole-Mac duplicate search.
Does it need Full Disk Access?Full Disk Access is optional, though some system locations it detects may require administrator access to actually clean.
Size
6 MB
Stars
234
Age
1mo
Commits · 90 Days