Agent.ps1 failed to launch (2026.06.11-03-15-00-241fc09)

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Just installed the latest version in Windows 11.
type ‘agent’ in a powershell, it fails with an error, “No version directories found”.

Steps to Reproduce

In a powershell, type agent
agent.ps1: No version directories found in C:\Users\xxxxxx\AppData\Local\cursor-agent

Expected Behavior

It should launch the CLI with no errors

Operating System

Windows 10/11

Version Information

2026.06.11-03-15-00-241fc09

Additional Information

It turns out the regex in agent.ps1 is not correct. It misses the HH-mm-ss portion.
On line 48 change the regex to ‘^\d{4}.\d{1,2}.\d{1,2}-\d{2}-\d{2}I-\d{2}-[a-f0-9]+$’

Does this stop you from using Cursor

Yes - Cursor is unusable

Hi @My2CentsTX Thank you very much for reporting, I replicated this behavior and filing a bug report so we can patch this asap.
So that change you made solved it right? You’re unblocked? I made that quick fix you did to the launcher and I was unblocked

Yes, I did the quick fix locally and fixed the issue. Yes, I’m unblocked.

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

“Why does the version number checking logic in cursor-agent.ps1 not match the version naming rule of the downloaded file? Previously it was 2026.06.11-02d5312, but now it’s 2026.06.11-23-48-49-02d5312 (with extra hour-minute-second fields). Has the packaging naming rule been updated?”

Steps to Reproduce

powershell open input cmd : cursor-agent --version Also, even after a successful update, every time I reopen Cursor it still asks to update again. The version number is probably not being recognized correctly, likely because the directory naming rule has changed.

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

can’t use agent / cursor-agent command:

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

Steps to Reproduce

install cursor cli: irm ‘Cursor CLI — Run Agents in Terminal, GitHub Actions and Automations & Scripts’ | iex
then enter ‘agent help’ or any ‘agent’ command
error occurs

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

CLI:
CLI Version: 2026.06.12-19-59-36-f6aba9a

Additional Information

Just rename “AppData\Local\cursor-agent\versions\2026.06.12-19-59-36-f6aba9a” to “AppData\Local\cursor-agent\versions\2026.06.12-f6aba9a”.
Bug will be fixed

Does this stop you from using Cursor

Yes - Cursor is unusable

I can reproduce this on Windows. The versions folder exists, but agent.ps1 can’t find it because the regex doesn’t accept folder names with timestamps.

Generated:
2026.06.12-19-59-36-f6aba9a

Expected:
2026.06.12-f6aba9a

Renaming the folder makes the agent launch successfully, so it looks like a mismatch between the installer and the launcher’s regex.

I tested this again today, and the issue is still there. Hope this helps.

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

Describe the Bug

Description:
When running the Windows installation script (irm 'https://cursor.com/install?win32=true' | iex), the payload downloads successfully, but the wrapper script (agent.ps1) throws the following error:
No version directories found in C:\Users\...\AppData\Local\cursor-agent

Root Cause:
The installer downloads the payload into a timestamped directory format (e.g., 2026.06.19-20-24-33-653a7fb), but the regex in agent.ps1 used to validate the version directory is too strict and doesn’t account for the time/hour hyphens.

In agent.ps1:
$name -match '^\d{4}\.\d{1,2}\.\d{1,2}-[a-f0-9]+$'

Because of the extra -20-24-33 in the folder name, the regex fails, returning no valid directories, even though the Node payload is sitting right there.

Proposed Fix:
Update the regex in agent.ps1 to handle the timestamp variables before the commit hash. For example:
$name -match '^\d{4}\.\d{1,2}\.\d{1,2}.*-[a-f0-9]+$'

Environment:

  • OS: Windows 11
  • Shell: PowerShell 7 / Windows PowerShell

Steps to Reproduce

irm ‘Cursor CLI — Run Agents in Terminal, GitHub Actions and Automations & Scripts’ | iex

agent

Expected Behavior

launch agent file

Operating System

Windows 10/11

Version Information

2026.06.19-20-24-33-653a7fb

Does this stop you from using Cursor

No - Cursor works, but with this issue

when are we getting a fix for this?
due this issue agent is downloading the new version every time I invoke agent cli, which is quite frustrating.

Getting this same issue here on a new install :upside_down_face:

Here’s my app data folder

EDIT: Fixed with the workaround listed above

This seems to be fixed on2026.06.24-00-45-58-9f61de7

Hi @here, Hi all, good news: this is fixed. The Windows CLI launcher wasn’t recognizing the newer version-folder naming (builds started adding a timestamp to the folder name), so it couldn’t find the installed version and errored with “No version directories found”. The latest published Windows CLI build (2026.06.24-00-45-58-9f61de7 or newer) includes the fix.

To pick it up, reinstall with the Windows command (irm ' Cursor CLI — Run Agents in Terminal, GitHub Actions and Automations & Scripts ' | iex); that pulls the fixed build and replaces the launcher, so the manual rename/regex workaround is no longer needed. Thanks to everyone who reported this and shared workarounds while we tracked it down. If you still hit it after reinstalling, reply here, and we’ll dig back in.