Azure DevOps repos with space in URL

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

We are able to run cloud agents against some of our Azure Devops repos but not others, we receive the below error message, however access to the repo has been confirmed. The differentiating factor seems to be some of our organisations/project have a space in the name so the repo name results in having %20 in the git URL.


Bad Request
You do not have access to this repository.

Steps to Reproduce

Create a repo underneath an Azure Devops project that has a space in the name.
In the cursor cloud agents web ui, try to run a prompt against this repo.

Expected Behavior

Environment is set up and cloud agent runs

Operating System

Windows 10/11

Version Information

Version: 3.6.31 (user setup)
VS Code Extension API: 1.105.1
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60
Date: 2026-05-31T17:46:29.630Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Windows_NT x64 10.0.26200

Additional Information

We can successfully run cloud agents with other repos without the %20 in the URL.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey @krisogi!

Thanks for sharing this! This is a known bug, and we’re fixing it!

Will come back to this thread once it’s resolved!

Hey @krisogi!

We’re deploying a fix here. Can you try again later this afternoon and let us know if it’s resolved?

This seems to be working great now!

Thanks for the quick turnaround.