Install Buddies

Packages are distributed through the project’s GitHub releases. The repository is currently private: an authorized GitHub account is required to view and download these versions. The website does not automatically grant repository access.

View releases and access requirements

macOS

The native app requires macOS 14 or later. Choose Apple Silicon for M1 or newer chips, or Intel for an Intel Mac. Extract the archive and move Buddies into Applications.

Packages are signed locally, but are not notarized by Apple. macOS may ask for confirmation before opening them. Check their origin and the SHA-256 checksum provided with the release; do not globally disable macOS protections.

Linux

Builds target Ubuntu 24.04 or a distribution compatible with its glibc, on x64 and ARM64. Use the AppImage or the tar.gz archive. AppImage requires FUSE2; use the archive if FUSE is unavailable.

After extracting the archive, launch the Buddies executable. Install Claude Code or Codex in the same user environment.

Windows with WSL2

The interface opens as a Windows app. The engine, agents and projects run in the default Linux WSL2 distribution, not as native Windows processes.

Install WSL2 and Ubuntu 24.04 from a Windows terminal:

wsl --install -d Ubuntu-24.04

Finish creating your Linux account and restart if Windows asks you to.
In Ubuntu, install and sign in to Claude Code or Codex. Check that its command works in that terminal.
Install Buddies using the release’s Windows .exe package.
Choose a Linux folder, preferably under /home/, for better Git performance.

Buddies copies its engine into the Linux filesystem. Files and sessions stay in your distribution. If WSL is unavailable, the interface explains the missing setup.

If startup displays Untrusted IPC sender, the interface’s internal communication is blocked: this does not mean WSL is incorrectly installed. The 0.37.1 fix handles paths with special characters, including short Windows names such as RUNNER~1. Check release availability before replacing your installation; no security setting needs to be disabled.

Updating

Close the interface, install the new package and reopen it. Closing the interface does not stop managed agents. Read the release notes for any additional steps.

Each release is built after integration into main, only if checks and all five packaging targets succeed. Use SHA256SUMS.txt to verify downloads.