Files
Maestro/docs/installation.md
2026-02-04 00:59:45 -06:00

102 lines
3.4 KiB
Markdown

---
title: Installation
description: Download and install Maestro on macOS, Windows, or Linux.
icon: download
---
## Download
Download the latest release for your platform from the [Releases](https://github.com/pedramamini/maestro/releases) page:
- **macOS**: `.dmg` or `.zip` (available for both Intel and Apple Silicon)
- **Windows**: `.exe` installer or portable `.exe` (no installation required)
- **Linux**: `.AppImage`, `.deb`, or `.rpm` (available for both x86_64 and arm64)
- **Upgrading**: Simply replace the old binary with the new one. All your data (sessions, settings, playbooks, history) persists in your [config directory](./configuration).
## Requirements
- At least one supported AI coding agent installed and authenticated:
- [Claude Code](https://docs.anthropic.com/en/docs/claude-code) — Anthropic's AI coding assistant (fully integrated)
- [Codex](https://github.com/openai/codex) — OpenAI's coding agent (fully integrated)
- [OpenCode](https://github.com/sst/opencode) — Open-source AI coding assistant (fully integrated)
- [Factory Droid](https://docs.factory.ai/cli) — Factory's AI coding assistant (fully integrated)
- [Gemini CLI](https://github.com/google-gemini/gemini-cli), [Qwen3 Coder](https://github.com/QwenLM/Qwen-Agent) — Planned support
- Git (optional, for git-aware features)
<Note>
Maestro is a pass-through to your provider. Your MCP tools, custom skills, permissions, and authentication all work in Maestro exactly as they do when running the provider directly—Maestro just orchestrates the conversation flow in batch mode.
</Note>
## WSL2 Users (Windows Subsystem for Linux)
<Warning>
When developing or running Maestro with WSL2, always clone and run from the **native Linux filesystem** (e.g., `/home/username/maestro`), NOT from Windows-mounted paths (`/mnt/c/...`, `/mnt/d/...`).
</Warning>
Using Windows mounts causes several critical issues:
| Issue | Symptom |
|-------|---------|
| Socket binding failures | `EPERM: operation not permitted` when starting dev server |
| Electron sandbox crashes | `FATAL:sandbox_host_linux.cc` errors |
| npm install failures | Timeouts, `ENOTEMPTY` rename errors |
| Git corruption | Missing index files, spurious lock files |
### Recommended WSL2 Setup
```bash
# Clone to Linux filesystem (not /mnt/...)
cd ~
git clone https://github.com/pedramamini/maestro.git
cd maestro
# Install dependencies
npm install
# Run in development mode
npm run dev
```
### Accessing Files from Windows
You can browse your WSL2 files from Windows Explorer using:
```
\\wsl$\Ubuntu\home\<username>\maestro
```
### Troubleshooting WSL2
If you encounter `electron-rebuild` failures, try setting the temp directory:
```bash
TMPDIR=/tmp npm run rebuild
```
For persistent issues, see [Troubleshooting](./troubleshooting) for additional WSL-specific guidance.
## Building from Source
If you prefer to build Maestro from source:
```bash
# Prerequisites: Node.js 22.0.0 or higher
node --version # Verify version
# Clone the repository
git clone https://github.com/pedramamini/maestro.git
cd maestro
# Install dependencies
npm install
# Run in development mode
npm run dev
# Or build for production
npm run build
npm run package
```
<Note>
Building from source requires native module compilation (node-pty, better-sqlite3). On Windows, you'll need the [Visual Studio Build Tools](https://visualstudio.microsoft.com/visual-cpp-build-tools/). On macOS, you'll need Xcode Command Line Tools (`xcode-select --install`).
</Note>