Bug Report: `zsh: trace trap` on launch — macOS 15.3.1 Apple Silicon

[sjagadee]

Description

Summary

opencode crashes immediately on launch with zsh: trace trap on macOS 15.3.1 (Apple Silicon). The crash is an EXC_BREAKPOINT / SIGTRAP caused by a pointer authentication (PAC) trap in a Bun Worker thread.

Environment

Field	Value
OS	macOS 15.3.1 (24D70)
Architecture	ARM64 (Apple Silicon)
Install method	Homebrew
Binary path	/opt/homebrew/bin/opencode
Binary arch	arm64 (confirmed via file)
Rosetta	No (translated: false in crash report)

Steps to Reproduce

1. Install opencode via Homebrew on an Apple Silicon Mac running macOS 15.3.1
2. Run opencode in any terminal
3. Observe immediate crash: zsh: trace trap opencode

Expected Behavior

opencode launches normally.

Actual Behavior

Crashes instantly with zsh: trace trap. No output is produced before the crash.

Crash Analysis

Exception type: EXC_BREAKPOINT (SIGTRAP)
Signal: SIGTRAP (signal 5)
Faulting thread: Worker (Bun Worker thread)
ESR description: (Breakpoint) pointer authentication trap IB

The crash is a PAC (Pointer Authentication Code) failure on ARM64e. This occurs in a Bun Worker thread during startup. The binary itself is a valid arm64 Mach-O executable with no missing dependencies (all linked libs are standard macOS system libraries).

Linked libraries (all present)

/usr/lib/libicucore.A.dylib
/usr/lib/libresolv.9.dylib
/usr/lib/libc++.1.dylib
/usr/lib/libSystem.B.dylib

Faulting thread stack (Worker)

opencode.exe  imageOffset: 39956492
opencode.exe  imageOffset: 47469900
opencode.exe  imageOffset: 3292556
opencode.exe  imageOffset: 25084452
opencode.exe  imageOffset: 25085444
opencode.exe  imageOffset: 14598856
opencode.exe  imageOffset: 16186364
...
_pthread_start  (libsystem_pthread.dylib)
thread_start    (libsystem_pthread.dylib)

Crash report excerpt

{
  "app_name": "opencode.exe",
  "os_version": "macOS 15.3.1 (24D70)",
  "platform": 1,
  "bug_type": "309",
  "translated": false,
  "cpuType": "ARM-64",
  "procName": "opencode.exe",
  "procPath": "/opt/homebrew/*/opencode.exe",
  "exception": {
    "codes": "0x0000000000000001, 0x000000010294f00c",
    "type": "EXC_BREAKPOINT",
    "signal": "SIGTRAP"
  },
  "termination": {
    "code": 5,
    "namespace": "SIGNAL",
    "indicator": "Trace/BPT trap: 5"
  },
  "faultingThread": 26
}

The faulting thread ESR: "(Breakpoint) pointer authentication trap IB" — a PAC-B instruction authentication failure on Apple Silicon.

Additional Context

• The crash log shows Bun runtime threads (Bun Pool 0–7), JIT threads (JIT Worklist Helper Thread), and JavaScriptCore threads (JSC Heap Collector Thread, Heap Helper Thread) — all consistent with a Bun-based binary
• A JIT-compiled dylib is loaded from a temp path (/private/var/folders/.../.3dfceaff779f7df6-00000000.dylib), which may be relevant to the PAC failure
• SIP is enabled on the affected machine
• No other processes or injected libraries appear involved

Workarounds Attempted

• Confirmed binary is native arm64 (not x86_64 running under Rosetta)
• Confirmed no com.apple.quarantine attribute on the binary
• All linked system dylibs are present and valid

Plugins

Homebrew

OpenCode version

stable 1.17.3 (bottled)

Steps to reproduce

Install opencode via Homebrew on an Apple Silicon Mac running macOS 15.3.1
Run opencode in any terminal
Observe immediate crash: zsh: trace trap opencode

Screenshot and/or share link

No response

Operating System

macOS 15.3.1 (24D70)

Terminal

Ghostty

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• zsh: trace trap opencode #6988: Same zsh: trace trap opencode error on macOS
• Bun v1.3.13 panic on macOS: NAPI FATAL ERROR napi_create_error and zsh: trace trap opencode #24148: Bun runtime crash with zsh: trace trap on macOS (ARM64), also involving a PAC/SIGTRAP in Bun Worker threads
• Hangs & crashes with SIGTRAP (Pointer Authentication) on macOS 15.5 #1659: SIGTRAP (Pointer Authentication) crash on macOS 15 Apple Silicon — same EXC_BREAKPOINT / PAC trap root cause

Please review those issues to see if your problem is already tracked or if there are known workarounds.

[sjagadee]

Workaround:

Run: opencode debug paths

Then delete these folders

rm -rf ~/.local/share/opencode
rm -rf ~/.cache/opencode
rm -rf ~/.config/opencode
rm -rf ~/.local/state/opencode
rm -rf /var/folders/k2/_2tzp1wn59nfwlm6_1_5f6wr0000gn/T/opencode

Opencode Started working, not the ideal fix, as I lost all the prior setup, but it started working