Diagnostics

Main-process logs live in the logging folder. The renderer reports errors through log:write. In Settings, a user can reveal the log file or enable detailed logging.

Protect feed data

Keep feed URLs and content behind the existing log redaction when you add diagnostics.

Follow a failure

Expected failures return a tagged Result to the caller. An unexpected IPC failure gets an incident ID, which the renderer can show beside a retry action and a link to the log. Startup has a separate health result; the error components handle a database reset or failed startup.

To investigate a report, reproduce the action and note its incident ID. Find that ID in the log, then test the operation at the boundary that owns it. Use an Electron end-to-end test when the result depends on the packaged window, preload bridge, or filesystem layout. The repository’s contribution instructions list focused test commands.