Skip to content

[BUG] supertag and supertag-lite binaries exit 137 on macOS 26.4 (Sequoia, Apple Silicon) #84

@mvanders

Description

@mvanders

All pre-built binaries (supertag, supertag-lite, supertag-mcp) exit immediately with code 137 (SIGKILL) on macOS 26.4 (Build 25E246, Apple Silicon M1). Gatekeeper quarantine was removed, Security & Privacy "Allow Anyway" was
clicked, but no dialog appears and the binary is killed silently.

Environment

  • macOS: 26.4 (Build 25E246)
  • Arch: arm64 (Apple Silicon M1)
  • Binary: supertag-v2.5.7-macos-arm64 (both full and lite)
  • Bun: 1.3.12

What was tried

  • xattr -d com.apple.quarantine — no effect
  • System Preferences → Security & Privacy → Allow Anyway — dialog never appears
  • Running from Terminal directly — same SIGKILL

Workaround
Running from source works perfectly:
git clone https://github.com/jcfischer/supertag-cli.git ~/Tools/supertag-cli
cd ~/Tools/supertag-cli && bun install

wrapper script:

echo '#!/bin/bash\nexec bun run ~/Tools/supertag-cli/src/index.ts "$@"' > ~/.local/bin/supertag
supertag post (Input API) works this way. supertag-export not yet tested from source.

Notes
macOS 26.x may have stricter JIT/memory restrictions on Bun-compiled binaries. Could be related to the LanceDB native module even in the lite build, or a new entitlements requirement in 26.x.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions