Skip to main content

Downloads

Download the Customertimes Bridge for Windows, macOS, and Linux from this gateway, verify the checksum, and run the Linux one-line installer.

Every file below is served by this gateway. The same files are attached to the matching GitHub Release of the platform, and the copy here is byte-identical: the release pipeline bakes them into the image, so the version you download always matches the gateway you connect to.

Platform File Checksum
Windows x86_64 customertimes-bridge-windows.exe .sha256
macOS, universal (Apple Silicon and Intel) customertimes-bridge-macos.dmg .sha256
Linux x86_64 (glibc 2.35 or newer) customertimes-bridge-linux-x86_64.tar.gz .sha256
Linux aarch64 (glibc 2.35 or newer) customertimes-bridge-linux-aarch64.tar.gz .sha256
Linux installer install.sh

Linux: one command

The installer downloads the right tarball for your CPU, verifies it, installs the bridge, links it to your account, and configures Claude Code. Get a code from your Profile page after signing in, then:

curl -fsSL https://gateway.example.com/files/downloads/install.sh | sh -s -- \
  --download-base https://gateway.example.com/files/downloads --code <code>

Replace gateway.example.com with this gateway's hostname. The full walk-through, including WSL, is in Install the Desktop Bridge.

Windows and macOS

Download the file, verify it, run it, and approve the device link in your browser. Step by step: Install the Desktop Bridge.

Until the binaries carry an OS code-signing certificate, the first launch is challenged: Windows SmartScreen shows More info → Run anyway; macOS Gatekeeper blocks the first open (right-click → Open, or xattr -d com.apple.quarantine /Applications/CustomertimesBridge.app). Verify the checksum before you accept either prompt.

Verify a download

Each binary has a .sha256 file beside it. Compare before running:

# Linux
sha256sum -c customertimes-bridge-linux-x86_64.tar.gz.sha256
# macOS
shasum -a 256 -c customertimes-bridge-macos.dmg.sha256
# Windows (PowerShell)
(Get-FileHash .\customertimes-bridge-windows.exe -Algorithm SHA256).Hash

Assets published by the release pipeline are also signed with Sigstore, and carry .sig and .pem files alongside them in the GitHub Release.

Where .sig and .pem files are present, verify with cosign:

cosign verify-blob --signature customertimes-bridge-windows.exe.sig \
  --certificate customertimes-bridge-windows.exe.pem \
  --certificate-identity-regexp='https://github.com/systempromptio/systemprompt-customertimes/' \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  customertimes-bridge-windows.exe