Guide · Windows

AI coding agents on Windows: the complete setup guide

TL;DR

To run AI coding agents on Windows you need git (and Node.js or Python for some agents), then the agents themselves, like Claude Code or Codex. Keep projects that build natively on Windows in Windows, and put Linux-toolchain projects inside WSL, where file access is fast. Pane runs agents for both kinds of repo from one Windows app and gives every task its own worktree. This guide goes from a fresh machine to several agents running side by side.

This guide takes you from a fresh Windows machine to several AI coding agents running in parallel: prerequisites, the native-or-WSL choice, installing agents, and running them with Pane. If you already have git and Node.js, skip to installing agents.

Prerequisites

Git for everything; Node.js for Codex and npm installs; Python for Aider.

Git

Download it from git-scm.com or install with WinGet. Keep the default that makes git available from PowerShell. Git for Windows also gives Claude Code a Bash shell to work in.

winget install --id Git.Git -e --source winget

Node.js

Codex, OpenCode and other npm-installed agents need Node.js. Install the LTS version from nodejs.org or with WinGet, then check it with node --version in a new terminal.

winget install --id OpenJS.NodeJS.LTS -e

Python (optional)

Aider and a few other agents run on Python. Tick “Add Python to PATH” during installation.

winget install --id Python.Python.3.12 -e

Native Windows or WSL

Keep each repo on the side where its tools run; Pane handles both.

WSL gives you a real Linux environment inside Windows. Both work with agents; pick per project.

Native WindowsWSL
Best for.NET, Unity, PowerShell, anything that builds on WindowsDocker, bash-heavy projects, Linux-only toolchains
File speedFast for Windows pathsFast inside the Linux filesystem; slow across the boundary
In PaneAgents run in Git Bash, PowerShell or cmdAgents, terminals and git run inside the distro

If you're unsure, start native; you can add WSL later. To install it:

wsl --install

Installing agents

Install only the agents you'll use, then open a new terminal.

Claude Code

Anthropic's agent. Works with a Claude Pro or Max plan or an API key. See Claude Code in Pane.

irm https://claude.ai/install.ps1 | iex
# or: winget install Anthropic.ClaudeCode
claude

Codex

OpenAI's agent. Sign in with ChatGPT the first time you run it. See Codex in Pane.

npm install -g @openai/codex
codex

Aider

Open source pair programmer for almost any model. See Aider in Pane.

python -m pip install aider-install
aider-install
aider

OpenCode

Open source terminal agent for many providers. See OpenCode in Pane.

scoop install opencode
# or: npm i -g opencode-ai@latest
opencode

Run each command in a new terminal to check it works. “Not recognized as a command” usually means the terminal predates the PATH change; open a new one.

Installing Pane

One PowerShell line, or a guided setup through npx.

Pane is where your agents live: it handles worktrees, terminals, diffs and git. Install it with PowerShell:

irm https://runpane.com/install.ps1 | iex

Or use the guided setup, which also offers remote and headless options:

npx --yes runpane@latest

The installer picks the x64 or ARM64 build for your machine. The first time you run it, Windows SmartScreen may ask you to confirm; choose “More info”, then “Run anyway”.

Your first parallel session

Two panes, two agents, two branches.

Add your repo, then create two panes with Ctrl+N, one per task:

  • → Pane 1: Claude Code (Ctrl+Alt+3) refactoring the auth module.
  • → Pane 2: Codex (Ctrl+Alt+4) writing tests for the payment API.

Each pane has its own worktree and terminal. Move between them with Ctrl+Tab, review a pane's diff with Ctrl+Shift+B, and commit with Ctrl+Shift+K. When a task is done, archive the pane with Ctrl+Shift+W; Pane removes its worktree after checking nothing is left unsaved. More in how to run multiple AI agents in parallel.

Agents running in parallelEach pane runs the agent's real terminal UI, with several panes going at once.Pane 2.4.155 on Windows 11, repo inside WSL2

Common Windows issues

PATH, long paths, ports and the WSL boundary cause most problems.

"claude is not recognized as a cmdlet"

Open a new terminal first. If you installed with npm, run npm config get prefix and add that folder to your PATH. claude doctor checks the install.

Long path errors

Windows limits paths to 260 characters by default, which deep node_modules folders can hit. Turn long paths on in git:

git config --system core.longpaths true

And in Windows, under Settings, System, For developers, Enable long paths, or with:

reg add "HKLM\SYSTEM\CurrentControlSet\Control\FileSystem" /v LongPathsEnabled /t REG_DWORD /d 1 /f

Dev servers fighting over a port

Several worktrees running dev servers all want port 3000. Pane gives each pane its own block of ten ports in PANE_PORT; have your dev server read it. Without Pane, set the port yourself, for example PORT=3001 npm run dev.

Slow git across the WSL boundary

If a repo lives in WSL, run git from inside WSL. Reaching Linux files from Windows, or the other way round, is slow. Pane runs git inside the distro for WSL repos; in your own terminals, stay on one side.

출처

직접 실행한 내용
  • → Pane 2.4.155 on Windows 11 with Ubuntu 24.04 on WSL2; install commands checked against each tool's docs in October 2026
정정
틀렸거나 오래된 내용이 있으면 알려 주세요. 수정하고 맨 위의 날짜를 갱신하겠습니다. GitHub에 이슈 열기
출처

자주 묻는 질문

또는
다운로드*
Windows SmartScreen 경고Pane에 서명이 없는 동안 직접 다운로드하면 SmartScreen 경고가 표시될 수 있습니다. Pane은 완전한 오픈 소스입니다. 직접 코드를 확인하거나 소스에서 빌드할 수 있습니다.1. 추가 정보 클릭2. '그래도 실행' 클릭3. 설치 계속PowerShell 설치는 공식 릴리스를 바로 받습니다. 브라우저 다운로드에서 생기는 번거로움도 대부분 피할 수 있습니다.npm 전역 설치
PowerShell에 붙여넣으세요.Linux

작성자 Parsa Khazaeepoul, Pane 공동 창업자. .