Unofficial Intel (x86_64) builds of get-bb/bb desktop. Upstream ships arm64-only on purpose (PR #1627, reverting PR #1137); the codebase is arch-agnostic, so a small patch is enough.

.github/workflows/build-x64.yml runs on macos-26-intel:

1. resolves the latest stable desktop-v* upstream release (or a tag given via workflow_dispatch);
2. clones upstream at that tag, applies bb-intel-local.patch;
3. pnpm install → pnpm --filter @bb/desktop dist:x64;
4. verifies the Electron executable and every darwin native addon (better-sqlite3, node-pty, @parcel/watcher, fs-native-extensions) is Mach-O x86_64, and loads better-sqlite3/node-pty under packaged Electron;
5. ad-hoc signs the bundle (codesign -s -, upstream entitlements + hardened runtime) and repacks dmg/zip around the signed app;
6. publishes a x64-<tag> release here with the dmg/zip + SHA256SUMS.

Cron runs twice a day; a build happens only when a new desktop-v* tag appears and no x64-<tag> release exists yet.

Download bb-*-x64.dmg (or the .zip) from Releases, copy bb.app to /Applications (replace the old one if present), then clear quarantine once:

xattr -dr com.apple.quarantine /Applications/bb.app

Or without a terminal: launch once → macOS blocks it → System Settings → Privacy & Security → "bb was blocked" → Open Anyway → launch again.

Builds are ad-hoc signed (Signature=adhoc — no Developer ID, so Gatekeeper still warns once). Ad-hoc signing avoids macOS provenance-tracking every exec in the app's process tree. Auto-update is disabled inside the build — the upstream feed only ships arm64, which cannot launch on Intel. Updating = downloading the next x64-* release and replacing bb.app; data lives in ~/.bb and survives replacement.

Actions → "Build bb desktop for Intel Mac" → Run workflow → optional tag (e.g. desktop-v0.43.4) / force to rebuild.

./scripts/build-x64.sh desktop-v0.43.4
# artifacts: $BB_INTEL_WORKDIR/bb/apps/desktop/release/ (or /tmp/bb-intel-*)

Requires Node ≥22.19 and corepack (pnpm 9.15 is pinned by upstream's packageManager field).