acp-bridge EPIPE loop fills disk with 9.8GB crash log at 93% CPU

[jmvl]

Bug Report

Process: acp-bridge (Node.js)
Location: /Applications/omi.app/Contents/Resources/acp-bridge/dist/index.js

What happened

The acp-bridge Node.js process started spamming Caught EPIPE (pipe closed) errors thousands of times per second into /private/tmp/acp-bridge-crash.log, resulting in:

• 9.8 GB log file in /private/tmp/
• 93%+ CPU across two simultaneous acp-bridge processes
• Major disk space loss with no warning or self-recovery

Fix applied

kill -9 <pids> && rm /private/tmp/acp-bridge-crash.log

App restarted cleanly after.

Expected behavior

acp-bridge should handle EPIPE errors gracefully, not loop infinitely and fill the disk.

Environment

• OS: macOS
• App: Omi.app

[wukkeen]

Same issue, curious to know if you're using BYOK or Omi's subscription, since I'm encountering issues with the my own Claude key not being used at all through Omi which I'm guessing is via ACP.

[prominentkyle]

Same issue here, it filled 86GB of logs on my machine with no warning or self-recovery