This page is for teammates using the Team Cereus build of Smithbox. It covers sending a bug report by hand, what happens after a crash, how to turn automatic crash reports off, and what leaves your PC.
The code for this is not on the mcp-bridge branch, so it cannot be listed in sources: above. It lives on the
branch claude/dist-autoupdate-3f8cb4 (worktree S:\Smithbox\.claude\worktrees\dist-autoupdate-3f8cb4) in
src/Smithbox.Program/Updater/Feed/TeamReports.cs, BugReportWindow.cs and CrashWatch.cs. This page was read
against those files at commit 9134b50fc. If you change them, update this page by hand: check.py will not flag it.
Who has this
Only the team build: a Smithbox folder that has update-channel.json next to the exe. A build you compiled
yourself has no such file, so it shows none of these menu items and sends nothing.
Send a bug report
Use this for a problem that is not a crash: something drawn wrong, a tool misbehaving.
- Help > Send a bug report...
- In the window Send a bug report, write what happened and what you were doing. Steps to make it happen again help most. The Send button stays grey until you write something.
- Leave Include crash logs from the last week ticked unless you have a reason not to.
- Press Send.
- You get: "Sent. Your report's code is ...: quote it when you talk to Team Cereus." Give that code to whoever looks at it.
If it cannot be sent you see "Not sent (...). It's kept in Crash Logs\Pending reports and goes the next time Smithbox starts."
What happens when Smithbox crashes
- A normal Smithbox error (a .NET exception): Smithbox shows its own crash message and writes its own crash log. With automatic reports on, the report is then sent without another message.
- A hard crash (graphics driver, a native library, out of memory): Smithbox just closes. The team build
catches this, writes
Crash Logs\Log <time>.txt, keeps a crash dump when one was written, and shows a Windows message box titled Smithbox Crash - <version> with the paths. With automatic reports on, the report is sent while that box is up, and the box says so. - A report that could not be sent waits in
Crash Logs\Pending reports(the newest 5 are kept) and goes out the next time Smithbox starts, up to 3 per start.
Crash Logs is the folder next to the exe. The 3 newest dumps are kept; older ones are deleted when Smithbox
starts.
Turn automatic crash reports off
- Help > Send crash reports automatically. It is on by default. Click it to turn it off. The choice is saved in
Crash Logs\reports.json. - Or set the environment variable
SMITHBOX_NO_REPORTS=1before starting Smithbox.
With it off, nothing is sent after a crash. The crash log and dump stay in Crash Logs for you to send yourself.
Send a bug report still works when you choose to use it. One catch: waiting reports in Pending reports are
only retried at start while automatic sending is on, so a bug report that failed to send stays there.
To run without the crash catcher at all (no dump, no notice), set SMITHBOX_NO_CRASH_WATCH=1.
What is sent
One zip per report, to the Eclipse server (https://server.nightseed.app/eclipse/smithbox/report):
| File in the zip | What it is |
|---|---|
info.json |
Smithbox version, report kind (crash, dotnet-crash or bug-report), exit code, time (UTC), Windows version, the GPU line from the log, and your note |
crash-log.txt, crash-log-1.txt ... |
Crash logs, at most 4. For a crash: the logs of that crash. For a bug report: last week's, if ticked |
output.log |
What Smithbox printed this session (at most the last 4 MB) |
output-previous.log |
The same for the session before. Bug reports only |
crash.dmp |
The crash dump, for crashes, when one exists and is at most 200 MB. Left out if the zip would pass 60 MB |
Nothing else is sent: no project files, no maps, no params, no screenshots.
What is scrubbed
Before the text files go into the zip:
- Your Windows user folder path becomes
%USERPROFILE%. - Your Windows user name becomes
<user>and your PC name becomes<pc>, wherever they stand as a whole word. Names shorter than 3 characters are left alone, because replacing them would damage ordinary words.
What is not scrubbed:
- Your note. It is sent as you wrote it. Do not put anything private in it.
- The crash dump. It is a memory snapshot and is sent as it is. Paths inside it can hold your user name, and it can hold whatever Smithbox had in memory.
- Paths outside your user folder (such as a project on another drive) stay readable in the logs.
The server also sees the address the upload came from, like any web server.
Limits
- The server takes at most 6 reports per hour from one address and refuses a zip over 64 MB.
- Stored reports are capped at 1 GB in total. The oldest are deleted first.
The team reads them from the report store on the hosting machine.