Skip to content
Claudette

Installation

Download

Section titled “Download”

Claudette is available as a pre-built binary from GitHub Releases.

PlatformArchitectureFormat
macOSApple Silicon (aarch64).dmg
macOSIntel (x86_64).dmg
Linuxx86_64.AppImage, .deb
Linuxaarch64.AppImage, .deb
Windowsx86_64.zip
WindowsARM64.zip
  1. Download the appropriate binary for your platform from the latest release
  2. macOS: Open the .dmg and drag Claudette to your Applications folder
  3. Linux: Run the .AppImage directly or install the .deb package
  4. Windows: Extract the .zip archive and run claudette.exe

Prerequisites

Section titled “Prerequisites”

Before using Claudette, ensure you have Claude Code installed and authenticated:

Terminal window
# Install Claude Code if you haven't already
# See: https://docs.anthropic.com/en/docs/claude-code


# Authenticate with your Anthropic account
claude /login

Build from Source

Section titled “Build from Source”

If you prefer to build from source, you’ll need:

  • Rust (stable toolchain, edition 2024)
  • Bun (JavaScript runtime and package manager)
  • Tauri CLI: cargo install tauri-cli --version "^2"

Platform dependencies:

Terminal window
xcode-select --install

Build steps:

Terminal window
# Clone the repository
git clone https://github.com/utensils/Claudette.git
cd Claudette


# Install frontend dependencies
cd src/ui && bun install && cd ../..


# Build optimized release binary
cargo tauri build

The compiled binary will be in target/release/ at the workspace root (Claudette uses a Cargo workspace, so the src-tauri crate’s outputs share the workspace target dir, not its own).

Run from source

Section titled “Run from source”

Pick the launcher that matches your platform — they share the same flag surface (--clean, -h/--help):

Terminal window
# Full-feature dev launcher (required for macOS voice input)
./scripts/dev.sh


# Same, but with a per-PID empty $CLAUDETTE_HOME for first-run UX
./scripts/dev.sh --clean


# Plain Tauri (no port probing, no signed bundle, no voice on macOS)
cargo tauri dev

Both launchers do a few things cargo tauri dev doesn’t:

  • macOS only: wraps the binary in a signed Claudette Dev.app bundle so macOS’s privacy system (TCC) grants Microphone and Speech Recognition permissions. A bare Mach-O binary will be killed by TCC the moment the prompt appears.
  • Probes free Vite + debug-eval ports so multiple dev instances can run side by side.
  • Stages the claudette-cli sidecar binary so the in-app CLI install path works in dev.

Windows-only details the PowerShell launcher handles for you:

  • Forces Vite to bind on 127.0.0.1 (IPv4). The default localhost resolves to ::1 first on Windows, but WebView2 navigates IPv4-first, so a mismatch surfaces as a blank webview with HRESULT 0x80070057.
  • Defaults to the same feature set as scripts/dev.sh — devtools,server,voice,alternative-backends. On aarch64-pc-windows-msvc the launcher appends -C target-feature=+fullfp16 to $env:RUSTFLAGS so the gemm-f16 ARMv8.2 inline asm in the voice feature compiles. Existing RUSTFLAGS are kept (rustc concatenates -C target-feature directives), so any flags you already set continue to apply.
  • Skips tauri/custom-protocol. With it on, import.meta.env.DEV is false in the webview, which leaves window.__CLAUDETTE_INVOKE__ unset and breaks the /claudette-debug eval server.
  • Stages the claudette-cli sidecar at the path Tauri’s bundle.externalBin expects — tauri.conf.json’s beforeDevCommand shell script can’t run on Windows.

Headless / sandboxed Linux

Section titled “Headless / sandboxed Linux”

If you’re on a Linux host without ALSA (containers, CI, sandboxed environments), build without voice support:

Terminal window
cargo tauri build --no-default-features --features tauri/custom-protocol,server

The server feature keeps the embedded WebSocket server for remote workspaces; drop it too if you don’t need that.