fix(desktop): handle EPIPE errors on stdout/stderr to prevent crash dialog

[UtkarshUsername]

What Changed

Added error event listeners on process.stdout and process.stderr at the very top of apps/desktop/src/main.ts. These listeners silently swallow EPIPE errors (broken pipe) while re-throwing all other stream errors.

Why

When the desktop app is launched from a terminal or parent process with piped stdout/stderr, the pipe can close while the app is still running. Effect's consolePretty logger writes to these streams. Once the pipe is broken, every subsequent write throws EPIPE, which surfaces as an Electron "A JavaScript error occurred in the main process" crash dialog.

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Low Risk
Narrow startup guard around broken-pipe writes; non-EPIPE stream errors still propagate.

Overview
Registers error listeners on process.stdout and process.stderr at the very start of the Electron main entrypoint, before any imports run.

EPIPE (broken pipe) is ignored so logging to closed terminal pipes no longer surfaces as an unhandled main-process exception and the “A JavaScript error occurred in the main process” dialog. Any other stream error is still rethrown.

^{Reviewed by Cursor Bugbot for commit f63cfe6. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Ignore EPIPE errors on stdout/stderr to prevent crash dialog in desktop app

Adds error event listeners to process.stdout and process.stderr in main.ts that silently swallow errors with code EPIPE and rethrow all others. EPIPE errors occur when a pipe closes before all data is written and previously surfaced as unhandled exceptions, triggering a crash dialog.

^{Macroscope summarized f63cfe6.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 780b47e8-43e0-4881-94a2-9801c67b51a3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved

This is a standard Node.js defensive pattern that handles EPIPE errors on stdout/stderr to prevent crash dialogs when pipes are closed. The 6-line addition is minimal, well-understood, and doesn't affect any business logic.

^{You can customize Macroscope's approvability policy. Learn more.}