Empty conversations in /analytics/ai-code/commits/:commitHash endpoint

Support Bug Reports
1

The conversations array in the response is consistently returning empty ([]) across 4 orgs. We tested on commits with high composer line counts — some with 1,000–3,000+ composer lines — and the conversationId UUIDs are correctly showing up inside rangeAnnotations[].groups[], but the corresponding conversation metadata (title, tldr, overview, summaryBullets) is never hydrated in the conversations array.

I know this api is still in beta phase but can we request somehow to get this enabled because api is working only the fields are missnig

API : AI Code Tracking API | Cursor Docs

conversations array is empty

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

6

Hey, thanks for the detailed report. The fact that conversationId shows up in rangeAnnotations[].groups[] while conversations[] is consistently empty is a really useful detail.

The most likely reason it’s empty across all 4 orgs is Privacy Mode NO_STORAGE / NO_TRAINING. Conversation metadata title / tldr / overview / summaryBullets is built from conversation summaries, and with Privacy Mode enabled those summaries aren’t stored. In that case, conversations[] will stay empty even if the IDs are correctly present in the range annotations.

Can you confirm whether Privacy Mode is enabled in all 4 orgs? That’ll help pin down the cause.

Also worth noting, this endpoint is currently in limited alpha. Hydrating conversations[] on the API path has known limitations, and the response shapes may still change. I’ve logged this case internally, but I can’t share an ETA yet.

If Privacy Mode is off and conversations[] is still empty, let me know and we’ll dig deeper.

7

hey,

We get the file names reflected properly in the Code tracking api’s which are restricted if privacy mode is on
Only the conversations[] is something we do not get right now

Happy to help with more details if needed

8

Hey, thanks, that’s a helpful clarification. If the file-level metrics are coming through correctly in the Code Metrics API, then Privacy Mode for those orgs is most likely off, since those fields would be stripped with Privacy Mode on. So I can drop my privacy hypothesis, thanks for checking.

In that case, the empty conversations[] comes down to a known limitation of this API path in the current limited alpha. conversationId is correctly returned in rangeAnnotations[].groups[], but metadata hydration (title / tldr / overview / summaryBullets) on this endpoint isn’t guaranteed yet. The response shapes for this API may still change.

If you spot any other mismatches between the API and the in-product data, send them over, it’ll help.