Sweepling v0.2.0

Crash reports you send yourself: if Sweepling crashes, it shows you the report at the next launch, and sends nothing.

Try it

1. Leave Sweepling running. It updates itself within 4 hours, or a minute after it next starts.
2. If Sweepling ever crashes, start it again: a window shows the report it made.
3. Press Report on GitHub to open a filled-in issue in your browser, read it, and submit it or not.

What's changed

• Crash reports through Oopsling: each one is written to %APPDATA%\Sweepling\crashes, with your home folder, user name and token-like strings masked, and reaches GitHub only if you file it. The update check is still the only network call.
• An update waits for the crash report, as it does for the review window, so a restart never closes the report before you've read it.
• A broken rules file names the line your editor shows, not the one before it, and an empty one says it's empty.
• A group that couldn't be closed says why: Windows didn't allow it.

Heads-up

• There's no email option for a crash report. Copy puts it on the clipboard if you'd rather send it another way.
• Still tested on Windows 11 only, and still the Claude Code CLI only.

Sweepling v0.1.1

A privacy fix and clearer names: your user name stays out of what Sweepling shows and logs, and groups say what they are.

Try it

1. Leave Sweepling running. It updates itself within a minute of starting.
2. When the brush shows a count, click it. An Angular dev server started with npm start now says "Angular dev server".
3. Run Sweepling.exe --scan > scan.json and look: your user name no longer appears in Claude Code's temp paths.

What's changed

• Your user name is masked in Claude Code's project folder names, such as C--Users-<name>-…, in the window, the close log and --scan. Before, only the usual C:\Users\<name> form was.
• Angular dev servers are named when the Angular CLI runs as ng.js serve, instead of showing as "npm start".
• No more "conhost": a group with no known kind is named after one of its own processes, never a protected one outside it.

Heads-up

• Lines 0.1.0 already wrote to %APPDATA%\Sweepling\closed.log keep your user name. Sweepling never rewrites old lines; delete the file if you want them gone.
• Still tested on Windows 11 only, and still the Claude Code CLI only.

Sweepling v0.1.0

The first release: the tray app, its review window, and a signed installer that keeps Sweepling up to date.

Try it

1. When the straw brush in your tray shows a count, click it.
2. Untick anything you still want. Leftovers of ended sessions start ticked; strays of a session that's still running never do.
3. Press Close. Sweepling checks each process again right before closing it, and logs what it closed.

What's in it

• Finds leftovers of ended Claude Code sessions, such as dev servers, task output watchers and scripts, and says what each one is in words.
• Leaves alone anything with an open TCP connection or a window, anything on the protect list, and the sessions themselves.
• Closes carefully: parents first, after a fresh connection check of the group and a PID and start-time check of each process.
• Notifies you when the count rises, and keeps a local log of every close, with command lines masked.
• Starts at login and updates itself from GitHub Releases; both are ticks in the tray menu.
• Light: about 14 MB of private memory while it waits in the tray.

Heads-up

• While the release is new, Windows may say "Windows protected your PC". The publisher is Hazel Granados.
• Tested on Windows 11. Windows 10 should work but hasn't been tried yet.
• Claude Code CLI only for now; the Claude desktop app, Codex and Cursor come later.
• The owner's dogfooding week runs to 2026-10-28. If Sweepling offers something you were still using, please report it with the "A leftover I've seen" form.

Thanks

To everyone who documented Windows orphans in anthropics/claude-code#62659.