How to run Claude Code on Windows without WSL (2026)
Guide · · Maciej Głuszak · .md version · Polski
In short: Claude Code runs natively on Windows: install Git for Windows, run the official installer in PowerShell, then start it in your project folder. You do not need WSL.
Paste into Claude Code:
Look at this folder and tell me what is in it. Then create a CLAUDE.md with three rules: reply in short sentences, never send anything outside this computer without asking, and name files without spaces or non-ASCII characters.
Updated: · tested on: Claude Code 2.1, Windows 11
Claude Code is an AI assistant from Anthropic that works in your terminal and does the work itself: it reads and writes files, runs commands and keeps track of the steps. Bolek, our AI assistant for Windows, is built on it, so everything below was tested in daily use on a plain Windows machine, not in a Linux layer.
What you need
- a computer with Windows 10 or 11,
- a paid Claude plan (Pro or Max) or an account billed by usage – the free plan does not include Claude Code,
- Git for Windows – Claude Code uses the shell that ships with it to run commands.
Step by step
- Install Git for Windows with the default settings.
- Install Claude Code with the official installer from Anthropic – one command pasted into PowerShell.
- Open a terminal in the folder the assistant should work in and type claude.
- Log in with your Claude account in the browser window that opens.
- Type your first instruction, for example: "look at this folder and tell me what is in it".
- Create a CLAUDE.md file in that folder with your working rules – the assistant reads it at the start of every conversation.
If `claude` is "not recognized" after installing, close the terminal and open a new one so the PATH refreshes, then check with `where.exe claude`.
The rules file: the most important five minutes
Claude Code does not remember the previous conversation. It remembers what you write in the rules file. For us it started with a few lines and is now the foundation of everything. Three things are enough at the start:
- what language and tone to use – "reply briefly, no preamble",
- what not to do without asking – for example sending anything outside your computer,
- how to name files – see the first trap below.
Five traps we hit on Windows
- Non-ASCII characters in file and folder names. Text in any language works, but names with accented letters can break inside commands. A rule "file names in plain ASCII, no spaces" saves hours.
- Garbled characters in a saved file. Older Windows PowerShell saves files in an encoding that loses non-English letters by default. Ask the assistant to always save files as UTF-8 and put that in the rules file.
- Two shells, two command languages. On Windows the assistant has both PowerShell and the Git shell. A command written for one fails in the other. When something "fails for no reason", first ask which shell ran it.
- Paths with spaces. "My Documents" in a command without quotes is two separate words. Keep projects in folders without spaces.
- One long conversation about everything. The longer the conversation, the more the assistant has to hold in its head and the worse it does. Our rule: one task, one conversation. Whatever must survive goes into the rules file or a note.
What next
Once the first prompts work, teach the assistant repeatable tasks with skills, and see how to write a rules file it actually follows in our guide on CLAUDE.md.
Install this as a skill (one line in a terminal, from our plugin marketplace on GitHub):
claude plugin marketplace add MokebeGluszak/bolekrobot-skills; claude plugin install windows-shell-rules-en@bolekrobotPreview SKILL.md. A skill is a single instructions file - nothing to execute.