Skip to main content
The installer detects your platform, downloads a release, and verifies its SHA-256 checksum before installation. Use Git alongside Gat to commit metadata.
1

Install gat

Run the installer in your shell:
Supports Apple silicon and Intel Macs, and ARM64 and x86_64 Linux including Alpine. On Linux, the installer selects the GNU build for glibc 2.28 or newer and the static musl build otherwise.
By default, gat is installed to ~/.local/bin on macOS/Linux and %USERPROFILE%\.local\bin on Windows. The installer tells you if that directory is not currently on your PATH.
2

Verify the installation

Open a new shell if needed, then run:
If this prints a version, gat is installed and ready to use.
3

Continue with your first repository

gat works inside Git repositories. Continue to the Quickstart to initialize a repository, track a file, and push it to storage.To use the docs from your AI assistant, follow Use Gat MCP in AI tools.

​
Installation options

Choose an option for a pinned version, custom location, or source build.
On macOS/Linux, the installer needs POSIX sh, Bash 3.2+, curl, tar, awk, grep, uname, mktemp, mkdir, rm, install, mv, cat, sleep, and sha256sum or shasum. Linux uses getconf when available to detect glibc; missing or unrecognized detection selects static musl. On Alpine, install the prerequisites with apk add bash curl if needed.Downloads need HTTPS access to GitHub and a working certificate store. The installer verifies and runs the new binary before replacing an existing installation. A failed download or compatibility check leaves it in place. If the new binary cannot start, the installer also prints its startup error.The destination must be a regular file or absent, not a directory or symlink. On Windows, close running Gat processes if the executable is locked.
The installers use the latest release by default. Pin an exact release when you need reproducible environments. Both 0.1.0 and v0.1.0 are accepted.
You can also set the GAT_VERSION environment variable before running the installer.
--libc auto is the default. The installer prints its selection:GNU is the default on supported glibc systems. The musl executable includes its C runtime and does not require a system glibc or musl installation. Git, SSH when used, and CA certificates are still provided by your system.To explicitly choose musl:
--libc gnu explicitly selects GNU. Overrides still undergo the startup check; selecting GNU does not make an incompatible binary runnable. --libc gnu and --libc musl are Linux-only. Combine either with --version to pin the release.
Set GAT_INSTALL_DIR before running the installer.
Make sure the chosen directory is on your PATH.
The release workflow builds the following platform matrix. Check the assets of a pinned release: older releases may not include every variant.Download the archive for your target from the latest GitHub release.Releases include a single SHA256SUMS file containing the SHA-256 checksum of every platform archive.
The example below shows Linux x86_64 with glibc 2.28+. For Alpine or older glibc, use x86_64-unknown-linux-musl. Change the architecture and platform as needed.
A release is published only after all supported targets are built, packaged, checksummed, and acceptance-tested from the packaged binaries.
Release archives are covered by GitHub artifact attestations. With the GitHub CLI installed, verify a downloaded archive with:
On Windows, pass the downloaded .zip archive instead.
gat is not currently published to crates.io. Install it directly from the Git repository:
Building from source requires Rust 1.91 or newer.
This installs gat to Cargo’s binary directory, usually ~/.cargo/bin.
Contributors can also run task install. Development-only helper binaries are installed with task install:dev-tools.

Start the Quickstart

Initialize a repository, track your first file, and move its bytes to storage.

Browse release downloads

Download platform archives, checksums, and release artifacts directly.