Repository navigation
Crash reports you send yourself: if Sweepling crashes, it shows you the report at the next launch, and sends nothing.
Try it
- Leave Sweepling running. It updates itself within 4 hours, or a minute after it next starts.
- If Sweepling ever crashes, start it again: a window shows the report it made.
- 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.