Packaging

The current packaging command builds the app and installs the finished bundle in build/bmux.app:

pnpm package

The command replaces the previous bundle only after the new build succeeds. It doesn't restart a running app. The release/ directory is temporary packaging output.

The package step signs with bmux's Developer ID identity when it is installed in Keychain and verifies the complete bundle after installation. Set BMUX_SIGNING_IDENTITY to use another certificate hash. Builds without the bmux identity remain local unsigned builds and are not notarized. See Platform notes for host requirements and the status of other platforms.

Custom output folder

BMUX_OUTPUT_DIR chooses the folder containing bmux.app. Relative paths resolve from the checkout.

BMUX_OUTPUT_DIR="$HOME/workspace/_tools" pnpm package

Use the same signing identity for each installed build so macOS recognizes updates as the same application and preserves Keychain access. Other files in that folder are preserved. Keep BMUX_OUTPUT_DIR set when using the CLI, or point BMUX_APP at the bundle:

export BMUX_APP="$HOME/workspace/_tools/bmux.app"
bmux attach-session -t main

Without an override, the CLI checks build/bmux.app and then ~/workspace/_tools/bmux.app.

Package after local merges

The repository includes a tracked post-merge hook that packages the primary checkout into ~/workspace/_tools/bmux.app. Enable it once after cloning:

pnpm hooks:install

Git does not enable repository-provided hooks automatically. The setting is shared by this repository's linked worktrees, but the hook skips merges inside task worktrees so only a merge into the primary checkout replaces the installed application. It also skips non-macOS systems and never restarts a running app.

Set BMUX_OUTPUT_DIR to change the installation folder. Set BMUX_SKIP_POST_MERGE_PACKAGE=1 for a merge that should not create a package.

Verification

Run pnpm test:package after packaging. See Local verification for the full test setup and current results.