Installation

Jimothy ships as a desktop app for macOS, Windows and Linux. Jimothy is free. Get the installers from the download page.

Downloads

Platform	Architectures	Formats
macOS	Apple silicon (arm64) and Intel (x64)	.dmg (drag to Applications) and .zip
Windows	x64	-setup.exe installer
Linux	x64	.AppImage, .deb (Debian/Ubuntu), .pacman (Arch and Arch-based distros such as Omarchy, EndeavourOS, Manjaro)

Direct links

These URLs always serve the newest release, which is handy for scripts and install docs:

Platform	URL
macOS, Apple silicon	https://downloads.jimothy.dev/latest/Jimothy-mac-arm64.dmg (.zip also available)
macOS, Intel	https://downloads.jimothy.dev/latest/Jimothy-mac-x64.dmg (.zip also available)
Windows	https://downloads.jimothy.dev/latest/Jimothy-windows-x64.exe
Linux AppImage	https://downloads.jimothy.dev/latest/Jimothy-linux-x86_64.AppImage
Debian / Ubuntu	https://downloads.jimothy.dev/latest/jimothy-linux-amd64.deb
Arch / Omarchy	https://downloads.jimothy.dev/latest/jimothy-linux-x86_64.pacman

A specific version lives at https://downloads.jimothy.dev/releases/<tag>/. https://downloads.jimothy.dev/latest.json lists the current version with file sizes and SHA-256 checksums.

Builds are currently unsigned

Release builds are produced without code-signing certificates, so macOS Gatekeeper and Windows SmartScreen warn the first time you open the app. The steps below get you past that warning.

macOS

Homebrew (picks the right build for your Mac):

brew install --cask echelonone-io/tap/jimothy

Update later with brew upgrade --cask jimothy. The first launch still needs the Gatekeeper step below (step 4).

Manual install:

1. Download the .dmg for your Mac: arm64 for Apple silicon (M-series), x64 for Intel.

2. Open the .dmg and drag Jimothy into Applications.

3. Open Jimothy. macOS blocks it with a message that the app can’t be verified.

4. Open System Settings → Privacy & Security, scroll to the security section, and click Open Anyway next to the message about Jimothy. Confirm with your password. You only need to do this once per installed version.

Alternatively, remove the quarantine attribute from a terminal:

xattr -dr com.apple.quarantine /Applications/Jimothy.app

Windows

1. Install Git for Windows if you don’t have it. Shell steps run in its Git Bash, so the same pipelines work on every OS.

2. Download Jimothy-windows-x64.exe. Edge may say the file isn’t commonly downloaded: in the downloads panel, hover the file and choose … → Keep → Show more → Keep anyway.

3. Run the installer. SmartScreen shows Windows protected your PC. Click More info → Run anyway. You only need to do this once per downloaded version.

4. Choose whether to install for just you or for all users, and where. Jimothy then appears in the Start menu.

Install your agent CLIs, gh and your project’s toolchain on Windows itself. Besides your PATH, Jimothy looks for CLIs in %APPDATA%\npm, ~\.local\bin, ~\.bun\bin and ~\.cargo\bin.

Linux

AppImage (any distro):

chmod +x Jimothy-*.AppImage
./Jimothy-*.AppImage

Debian / Ubuntu:

sudo apt install ./jimothy_*.deb

Arch / Omarchy / EndeavourOS / Manjaro:

sudo pacman -U jimothy-*.pacman

The pacman package depends only on official-repo packages: gtk3, nss, alsa-lib, libxss, libnotify, libsecret and xdg-utils. libsecret backs the encrypted credential store, and xdg-utils opens links and folders.

On Wayland compositors such as Hyprland, the window is matched to jimothy.desktop by its app id, so window rules can target jimothy.

Windows via WSL2

You can also run the Linux build inside WSL2, for example to keep your repositories and toolchain in Linux. Install the .deb in your distro, along with gnome-keyring for the encrypted credential store, and start it with jimothy. WSLg shows the window on your Windows desktop:

curl -LO https://downloads.jimothy.dev/latest/jimothy-linux-amd64.deb
sudo apt install ./jimothy-linux-amd64.deb gnome-keyring

In that setup, install git, gh and your agent CLIs inside WSL, and keep repositories in the Linux filesystem (for example ~/code) rather than under /mnt/c.

What else you need

Jimothy orchestrates tools that are already on your machine. Which of these you need depends on your pipelines.

Tool	Needed for
git	Workspaces in Git worktree or Fresh clone mode, and any pipeline that commits or pushes. On Windows, install Git for Windows: shell steps run in its Git Bash.
An agent CLI or API key	Agent steps. The built-in Simulator harness needs nothing, so you can try the app first.
GitHub CLI (gh), authenticated	Shell steps that open pull requests with gh pr create, as the built-in Feature and Bug fix templates do.
Your project’s toolchain	Shell steps such as npm test or pytest run in the run’s workspace (/bin/sh on macOS and Linux, Git Bash on Windows).

Install agent CLIs

Install whichever agents you want to use and sign in to them once in a terminal, the way you normally would. Jimothy runs them non-interactively, so they must already be authenticated. Common ones:

npm install -g @anthropic-ai/claude-code   # Claude Code  -> command: claude
npm install -g @openai/codex               # Codex CLI    -> command: codex
npm install -g @google/gemini-cli          # Gemini CLI   -> command: gemini

Then open Harnesses in Jimothy. Installed CLIs are detected automatically (click Re-detect after installing something new). Detection uses your login-shell PATH, plus common install locations such as ~/.local/bin, ~/.claude/local, ~/.npm-global/bin, ~/.bun/bin, ~/.cargo/bin, ~/.volta/bin, /opt/homebrew/bin and /usr/local/bin. If a CLI still isn’t found, add its folder under Settings → Extra PATH entries.

For the API harnesses (Claude API, OpenAI-compatible), add an API key on the Harnesses page or set ANTHROPIC_API_KEY / OPENAI_API_KEY. See Harnesses overview for every built-in harness and Custom harnesses to add any other CLI.

Agents run unattended with your permissions

Most built-in harnesses are configured for unattended operation (--dangerously-skip-permissions, --full-auto, --yolo). Prefer Git worktree workspaces and approval gates before anything that pushes or deploys. Claude Code refuses --dangerously-skip-permissions when running as root; if you run as root, edit the harness to use --permission-mode acceptEdits instead. See Data & security.

Where data lives

Jimothy stores its data (pipelines, runs, logs, encrypted secrets) in the Electron userData folder under Jimothy/factory. Per-run workspaces go in a workspaces folder inside it unless you change Settings → Workspaces folder. Set the FACTORY_DATA_DIR environment variable to use a different data folder. The exact location is shown at the top of the Settings page. See Data & security.

Next

Continue with the Quickstart.