Windows Cursor CLI: agent.ps1 fails with "No version directories found" when version directory includes timestamp

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Environment:

Error:
Running agent --version fails with:

agent.ps1 : No version directories found in C:\Users\Genta_Oyadomari\AppData\Local\cursor-agent

Actual version directory exists:

C:\Users<UserName>\AppData\Local\cursor-agent\versions\2026.06.12-19-59-36-f6aba9a

It looks like the launcher regex expects:

YYYY.MM.DD-commit

but the installed version directory is:

YYYY.MM.DD-HH-MM-SS-commit

Temporary workaround:
I backed up agent.ps1 and cursor-agent.ps1, then updated the regex to match the timestamped directory format:

^\d{4}.\d{1,2}.\d{1,2}-\d{1,2}-\d{1,2}-\d{1,2}-[a-f0-9]+$

After that, agent --version works.

Steps to Reproduce

Steps to reproduce
On Windows 11, open PowerShell.
Install Cursor CLI using the official Windows install command:
irm ‘Cursor CLI — Run Agents in Terminal, GitHub Actions and Automations & Scripts’ | iex
Restart PowerShell.
Run:
agent --version
The command fails with the following error:
agent.ps1 : No version directories found in C:\Users<username>\AppData\Local\cursor-agent
Check the installed version directory:
Get-ChildItem “$env:LOCALAPPDATA\cursor-agent\versions” -Directory
A version directory exists, for example:
2026.06.12-19-59-36-f6aba9a
In agent.ps1, the version directory appears to be matched using this regex:
^\d{4}.\d{1,2}.\d{1,2}-[a-f0-9]+$

This seems to match YYYY.MM.DD-commit, but the actual installed directory format is YYYY.MM.DD-HH-MM-SS-commit.

Operating System

Windows 10/11

Version Information

2026.06.12-19-59-36-f6aba9a

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi!
This is a known regression on our side, not your setup. Your patch is exactly the right fix. For anyone hitting this who’d rather not edit the script, the other quick workaround is to rename the version folder to drop the time segment, e.g.:

...\cursor-agent\versions\2026.06.12-19-59-36-f6aba9a...\versions\2026.06.12-f6aba9a

We’re already tracking this and a fix is on the way. I’m merging this into our main thread for the same issue so everything stays in one place — follow Agent.ps1 failed to launch for updates.