[Windows] Install script (install.ps1) may not append semicolon to PATH, causing PATH resolution

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

The [claude] command is unavailable in any terminal.
After installing Claude Code via the official PowerShell install script, the PATH entry added by the script was missing a trailing semicolon. This caused
PATH resolution to fail silently — the PATH looked correct in the Windows UI (System Properties > Environment Variables), making the root cause very difficult to identify.

Expected behavior
The install script should ensure the PATH entry is correctly delimited (semicolon-separated on Windows).

Note
Python was also reinstalled around the same time, so it's possible Python's installer is the root cause. However, the PATH entry added by install.ps1 is a likely candidate at some situation and worth reviewing.

What Should Happen?

Improvements to the use of semicolons (;) in installation scripts. Alternatively, resolution of conflicts when conflicting with other environment variables.

Error Messages/Logs

Steps to Reproduce

Steps to reproduce

1. Run irm https://claude.ai/install.ps1 | iex on Windows
2. Open a new terminal and run claude
3. Command is not found despite the install directory appearing in PATH

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.81 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_