Incorrect repository name in AI Edits report for Azure DevOps Server On-Premises

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The “AI Edits by Repository” report incorrectly identifies repositories hosted on Azure DevOps Server On-Premises.

The repository remote follows this path structure:

SERVER / COLLECTION / PROJECT / _git / REPOSITORY

The report displays:

COLLECTION / PROJECT

instead of:

PROJECT / REPOSITORY

The actual repository name after the “_git” segment is ignored.

Normal Git operations such as fetch, pull, and push work correctly. The issue only affects the repository label in the “AI Edits by Repository” analytics report.

Steps to Reproduce

  1. Open a Git repository in Cursor.
  2. Use an Azure DevOps Server On-Premises origin remote with this structure:
    SERVER / COLLECTION / PROJECT / _git / REPOSITORY
  3. Make AI-generated code changes.
  4. Commit the changes.
  5. Open the Cursor Team Dashboard.
  6. Navigate to “AI Edits by Repository”.
  7. Check the displayed repository name.

The report displays COLLECTION / PROJECT instead of PROJECT / REPOSITORY.

Expected Behavior

Cursor should correctly parse Azure DevOps Server On-Premises repository remotes.

For a remote structured as:

SERVER / COLLECTION / PROJECT / _git / REPOSITORY

the repository label should be:

PROJECT / REPOSITORY

The repository name after the “_git” segment should not be ignored.

Operating System

Windows 10/11

Version Information

Version: 3.13.10 (system setup)
VS Code Extension API: 1.128.0
Commit: 4f02290ccd9304f0e6bf8ee85f6e9106f02ac1f0
Date: 2026-07-23T21:41:07.333Z
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.256
OS: Windows_NT x64 10.0.26100

Additional Information

The repository is hosted on Azure DevOps Server On-Premises.

Cursor appears to use the collection and project path segments as the repository label while ignoring the actual repository name.

Git repository detection and normal Git operations work correctly. Only the repository label in the analytics report is affected.

No relevant console errors were observed.

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey @Sajad_Hamreh,
You’ve diagnosed it correctly, and this is on our side, not your setup. For Azure DevOps Server (on-premises) remotes, the “AI Edits by Repository” label drops the repo name after _git (cloud remotes keep it). It only affects that analytics label, so your Git operations and edit tracking aren’t impacted.

This isn’t intended behavior - we’ve let the team know and it’s an issue we’re tracking. I’ll post back here when there’s an update.