Skip to content

Installation

Shell installer

On Linux or macOS, install the latest stable release with the cargo-dist installer:

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/cookie-agent/cookie-agent/releases/latest/download/cookie_agent-installer.sh | sh

The installer selects the archive for the current platform, verifies its SHA256 checksum, and installs cookie under $CARGO_HOME/bin (normally ~/.cargo/bin).

PowerShell installer

On Windows x86_64 or ARM64, install the latest stable release with the cargo-dist PowerShell installer:

powershell -ExecutionPolicy Bypass -c "irm https://github.com/cookie-agent/cookie-agent/releases/latest/download/cookie_agent-installer.ps1 | iex"

The installer selects the matching MSVC ZIP archive, verifies its SHA256 checksum, and installs cookie.exe under %CARGO_HOME%\bin (normally %USERPROFILE%\.cargo\bin).

Release archives

Stable and nightly GitHub releases provide an archive and .sha256 checksum for:

  • Linux x86_64 with glibc
  • Linux x86_64 with musl
  • Linux aarch64 with glibc
  • macOS Apple silicon
  • macOS Intel
  • Windows x86_64 (MSVC), as a ZIP archive
  • Windows ARM64 (MSVC), as a ZIP archive

Linux and macOS archives use tar; Windows archives use ZIP. Download the archive for your platform, verify its checksum, extract it, and place cookie or cookie.exe on your PATH.

Nightly builds

Every push to main creates a timestamped v*-alpha.<timestamp> prerelease with archives for all seven targets. Nightly prereleases are retained for about two weeks, with at least the newest three always kept. They are intended for testing; run cookie --version to see the source commit hash embedded in the binary.

Open the prerelease list and select a nightly to download an archive or use its generated installer command. Each prerelease provides PowerShell (irm ... | iex) and shell (curl ... | sh) installers pinned to that prerelease.

Connect a model

Change to the workspace where the agent should operate and start the terminal UI:

cookie

No configuration file is required. When no provider is available, the TUI opens in setup mode. Use /connect to choose a managed provider and enter its setup and credentials, or configure a custom model in config.toml.