Windows & WSL Installation
Guide for installing and running aitasks on Windows via WSL
macOS prerequisite: Homebrew is required. Install it first if you haven’t —
ait setupuses it to install bash 5, Python 3, coreutils, and CLI tools.
Important: Run from your project root. The curl command (and
ait setup) must be run from the root directory of your project — the directory that contains the.gitfolder. aitasks stores task files, plans, and configuration inside your repository, and relies on git for task IDs, locking, syncing, and archival. Installing in a subdirectory or a non-git directory will not work correctly.
Install into your project directory (the git repository root):
curl -fsSL https://raw.githubusercontent.com/beyondeye/aitasks/main/install.sh | bash
Windows users: Run this inside a WSL shell, not PowerShell. See the Windows/WSL guide.
Upgrade an existing installation:
ait install latest
Or for fresh installs without an existing ait dispatcher:
curl -fsSL https://raw.githubusercontent.com/beyondeye/aitasks/main/install.sh | bash -s -- --force
After installing, run ait setup to install dependencies and configure supported agent integrations. See ait setup for details.
Already have the global ait shim? If you’ve previously run ait setup on another project, the global shim at ~/.local/bin/ait is already installed. You can bootstrap aitasks in any new project directory by simply running:
cd /path/to/new-project # Must be the git repository root
ait setup
The shim detects that no aitasks project exists, downloads the latest release, installs it, and then runs the full setup — all in one command. Make sure you are at the root of the git repository (where .git/ lives), not in a subdirectory.
Windows/WSL users: See the Windows/WSL Installation Guide for step-by-step instructions including WSL setup, agent installation examples, and terminal configuration.
Agent caveats: See Known Agent Issues for current Claude Code and Codex CLI workflow limitations.
| Platform | Status | Notes |
|---|---|---|
| Arch Linux | Fully supported | Primary development platform |
| Ubuntu/Debian | Fully supported | Includes Pop!_OS, Linux Mint, Elementary |
| Fedora/RHEL | Fully supported | Includes CentOS, Rocky, Alma |
| macOS | Fully supported | Requires Homebrew; ait setup installs bash 5, coreutils, and other dependencies |
| Windows (WSL) | Fully supported | Via WSL with Ubuntu/Debian (see Windows guide) |
Per-project files (committed to your repo):
ait — CLI dispatcher script.aitask-scripts/ — Framework scripts (task management, board, stats, etc.).claude/skills/aitask-* — Primary skill definitions (used directly by Claude Code and as the source for wrappers)aitasks/ — Task data directory (auto-created)aiplans/ — Implementation plans directory (auto-created)Optional: Codex CLI support (when ait setup detects Codex CLI):
.agents/skills/ — Codex CLI skill wrappers.codex/instructions.md — aitasks instructions for Codex.codex/config.toml — created or merged with aitask settingsOptional: OpenCode support (when ait setup detects OpenCode):
.opencode/skills/ — OpenCode skill wrappers.opencode/commands/ — OpenCode command wrappers.opencode/instructions.md — aitasks instructions for OpenCodeopencode.json — merged with aitask settingsOptional: Gemini CLI support (when ait setup detects Gemini CLI):
.gemini/skills/ — Gemini CLI skill wrappers.gemini/commands/ — Gemini CLI command wrappersGEMINI.md — aitasks instructions for Gemini CLIGlobal dependencies (installed once per machine via ait setup):
fzf, gh (for GitHub), glab (for GitLab), or bkt (for Bitbucket), jq, git~/.aitask/venv/ with textual, pyyaml, linkify-it-py (plus optional plotext when enabled for ait stats --plot)ait shim at ~/.local/bin/ait.claude/settings.local.json (see Claude Code Permissions)Next: Getting Started
Guide for installing and running aitasks on Windows via WSL
Known integration caveats for ai code agents used with aitasks
Multi-tab terminal workflow and monitoring during implementation
Authenticate with GitHub, GitLab, or Bitbucket