Where does the bug appear (feature/product)?
Cloud Agent (GitHub, Slack, Web, Linear)
Describe the Bug
I’m having an issue using Cursor Cloud Agents through Slack with my company’s Azure DevOps repositories.
My Azure DevOps account is already connected to Cursor, and Cursor is able to discover and list my Azure DevOps repositories correctly. However, when I try to launch a Cloud Agent from Slack against a repository whose Azure DevOps project name contains a space, Cursor fails to recognize or validate the repository.
For example, using redacted/example values, this repository fails:
https://dev.azure.com/example-org/Example%20Project/_git/App
When I use the repository as my default Slack repository, Cursor instead tells me to connect a GitHub, GitLab, Azure DevOps, or Bitbucket account, even though my Azure DevOps account is already connected.
I tested another Azure DevOps repository in the same organization using the same Cursor account and Slack integration, but under a project whose name does not contain a space:
https://dev.azure.com/example-org/ExampleProjectNoSpace/_git/App
That repository successfully launches a Cloud Agent from Slack.
Based on this comparison, the issue appears to be related to Slack Cloud Agents handling Azure DevOps project names containing spaces / %20.
Steps to Reproduce
Connect an Azure DevOps account to Cursor.
Connect Cursor to Slack.
Have an Azure DevOps repository under a project whose name contains a space.
Example:
Organization: example-org
Project: Example Project
Repository: App
Repository URL:
https://dev.azure.com/example-org/Example%20Project/_git/App
Confirm that Cursor can discover the repository in its repository picker.
Configure that repository as the default repository for the Slack Cloud Agent.
In Slack, send:
@Cursor hello
Cursor responds with a message similar to:
Connect a GitHub, GitLab, Azure DevOps, or Bitbucket account to access Example Project/App
even though Azure DevOps is already connected.
I also tried explicitly passing the repository URL:
@Cursor repo=https://dev.azure.com/example-org/Example%20Project/_git/App hello
Cursor rejects the URL as invalid. Slack appears to convert it into its formatted link representation, and Cursor responds that it is not a valid repository URL.
As a control test, I used a repository in the same Azure DevOps organization where the project name has no spaces:
https://dev.azure.com/example-org/ExampleProjectNoSpace/_git/App
Run:
@Cursor repo=https://dev.azure.com/example-org/ExampleProjectNoSpace/_git/App hello
The Cloud Agent launches successfully.
So from what I am experiencing:
Same Azure DevOps organization
Same Azure DevOps account
Same Cursor account
Same Slack workspace/integration
Project name without spaces → works
Project name containing a space / %20 → fails
Expected Behavior
I expect Cursor’s Slack Cloud Agent integration to support Azure DevOps repositories whose project names contain spaces.
A valid Azure DevOps repository URL such as:
https://dev.azure.com/example-org/Example%20Project/_git/App
should resolve and launch a Cloud Agent in the same way as:
https://dev.azure.com/example-org/ExampleProjectNoSpace/_git/App
I should not be prompted to connect my Azure DevOps account when that account is already connected and Cursor is already able to discover the repository through its repository picker.
Operating System
Windows 10/11
Version Information
Version: 3.16.29 (system setup)
VS Code Extension API: 1.128.0
Commit: 6246455961129c32969845e00aa25d87ae926ec0
Date: 2026-08-18T01:26:26.285Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.26200
Additional Information
This appears related to a previously reported Azure DevOps issue involving project or organization names containing spaces:
From that thread, my understanding is that Cursor previously identified and fixed an issue where Azure DevOps repository URLs containing %20 caused problems for Cloud Agents.
What I am seeing suggests that the fix may not have been fully applied to the Slack Cloud Agent repository resolution / access validation path.
In my case, Azure DevOps itself appears to be connected correctly:
Cursor can authenticate against Azure DevOps.
Cursor can discover my repositories.
The repository with the space in its project name appears in Cursor’s repository picker.
Slack successfully launches a Cloud Agent against another Azure DevOps project that does not contain spaces.
The only meaningful difference between my working and failing test cases is that the failing Azure DevOps project name contains a space.
Could the team check whether the previous Azure DevOps %20 / project-name spacing fix is also being applied to repositories launched through the Slack Cloud Agent integration?
All organization, project, and repository names in this report have been replaced with example values for privacy, but I can provide the actual details privately to Cursor staff if needed.
Does this stop you from using Cursor
No - Cursor works, but with this issue
