The Best Claude Code Setup for Windows: Terminal, Shell and Workflow

The recommended stack at a glance

• Terminal: Windows Terminal (free, in the Microsoft Store) with PowerShell 7 or Git Bash profiles.
• Claude Code install: native installer, which auto-updates in the background.
• Shell for Claude: Git Bash via Git for Windows, for much better compatibility with bash-style commands.
• Optional: WSL 2 for Linux-first projects or sandboxing.
• Scaling up: CodeAgentSwarm to supervise multiple sessions at once.

Pick the right terminal: Windows Terminal

Claude Code works in plain PowerShell, CMD, Git Bash and WSL shells. But the terminal application you run those shells in matters for day-to-day comfort, and on Windows the clear winner is Windows Terminal: tabs, panes, proper Unicode rendering and sane copy-paste.

• Install Windows Terminal from the Microsoft Store if you do not have it.
• If you want a newer shell, install PowerShell 7+ from aka.ms/powershell; Claude Code works fine with the built-in Windows PowerShell too.
• Add a Git Bash profile to Windows Terminal once you install Git for Windows, so you can choose per tab.

Install Git for Windows and let Claude use Git Bash

This is the single highest-impact tweak in this guide. Without Git for Windows, Claude Code uses PowerShell to execute the commands it runs while working on your code. That works, but a huge share of developer tooling, scripts and one-liners assume a bash-like shell. With Git for Windows installed, Claude Code automatically uses Git Bash instead, and far fewer commands need translating or fail in odd ways.

• Download Git for Windows from git-scm.com and install it with the default options.
• Restart your terminal. Claude Code detects Git Bash automatically.
• You also get git itself, which Claude Code needs for anything version-control related anyway.

If Claude Code does not pick up Git Bash (for example with a custom Git install path), point it there explicitly in your settings.json:

{
  "env": {
    "CLAUDE_CODE_GIT_BASH_PATH": "C:\\Program Files\\Git\\bin\\bash.exe"
  }
}

Keep it updated (and pick a release channel)

• If you used the native installer, you are done: it auto-updates in the background and applies the update on next launch.
• If you installed via WinGet, updates are manual (winget upgrade Anthropic.ClaudeCode), or set CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE=1 to opt into auto-updates.
• Claude Code ships fast. If you prefer fewer surprises over day-one features, switch the release channel from "latest" to "stable" in your settings; stable lags about a week and skips major regressions.

When WSL 2 earns a place in your setup

For most Windows-native work you do not need WSL at all. Two cases justify it:

• Linux-first projects: if your stack assumes Linux (Docker-heavy backends, deployment scripts, Makefiles full of Linux-isms), run Claude Code inside WSL 2 where the project actually behaves like production.
• Sandboxing: Claude Code's sandboxed command execution works on WSL 2 only. Native Windows and WSL 1 do not support it. If you want stronger isolation when letting Claude run commands freely, WSL 2 is the way.

Native and WSL installs coexist fine on the same machine, so you can keep native as your default and use WSL 2 for the projects that need it. More detail in our guide on running Claude Code on Windows.

Project hygiene: CLAUDE.md and permissions

Two habits make every Claude Code session noticeably better, on any OS:

• Keep a CLAUDE.md in your repo. Run /init once in a project and Claude generates one: build commands, conventions, structure. Every future session starts with that context for free.
• Tune permissions instead of approving everything by hand. Allow the safe, repetitive commands (your test runner, your linter) and keep confirmation for the destructive ones. If you are tempted to just turn everything off, read our guide on using YOLO / Turbo mode safely first.

The real upgrade: from one session to several

Once your single-terminal setup is smooth, the bottleneck becomes Claude itself: while it works, you wait. The developers getting the most out of Claude Code on Windows run several sessions in parallel: one fixing a bug, one writing tests, one on a refactor.

You can do that with raw Windows Terminal tabs, but you lose visibility fast: no notification when an agent finishes, no overview of what each one changed, history scattered per session.

CodeAgentSwarm is a Windows (and macOS) desktop app built exactly for this: up to 6 Claude Code terminals side by side, desktop notifications when an agent finishes or needs input, searchable history across all sessions, live per-terminal diffs and a kanban board the agents themselves keep updated. It runs on top of your existing Claude Code install, so everything in this guide still applies.

To plan that workflow, see how to use multiple Claude Code terminals.

Conclusion

A good Claude Code setup on Windows is not complicated: Windows Terminal for comfort, the native installer for zero-maintenance updates, Git Bash so commands just work, WSL 2 only when the project demands it, and a multi-session tool when one terminal stops being enough.

Set it up once and Claude Code on Windows feels every bit as smooth as on a Mac.