Entire web UI shows empty Cursor session panel even though the checkpoint contains a valid transcript

[shurkanTwo]

What happened?

Summary:
When using Cursor with Entire, the transcript is captured correctly and is readable via the CLI, but the Entire web UI renders the Cursor session section as empty. In the affected checkpoint, the UI shows the Cursor card with 0 steps and no transcript content, even though the checkpoint metadata points to a valid transcript file and entire explain --checkpoint --full prints the conversation successfully.

Environment

• Entire CLI with Cursor integration enabled
• Entire CLI 0.5.3 (f2ddf9f)
• Go version: go1.26.1
• OS/Arch: linux/amd64
• Agent: Cursor
• Model: gpt-5.4

Actual Behavior

In the Entire web UI:

• A Cursor session section is shown
• That section is blank
• The UI shows 0 steps
• No transcript text is displayed, even though the session has transcript content

Expected Behavior

The Entire web UI should display the same transcript content that is available via the CLI for the same checkpoint, or at minimum provide a readable transcript view for Cursor sessions instead of showing an empty panel.

Why This Looks Like a UI / Rendering Bug

The transcript is present in checkpoint storage and is not missing at capture time.

Verified facts

1. The raw Cursor transcript file exists in Cursor’s local session storage.
2. Entire copies that transcript into its local metadata during session processing.
3. Entire stores transcript data in the checkpoint branch.
4. The CLI can render the transcript successfully.

CLI proof

This command shows the transcript correctly:

entire explain --checkpoint <checkpoint-id> --full --no-pager

The output includes:

• the original user intent
• assistant responses
• tool events such as file reads and edits

So the transcript exists and is parseable by Entire.

Checkpoint Storage Evidence

The checkpoint metadata stored on entire/checkpoints/v1 contains transcript references for the Cursor session.

The metadata points to a valid transcript file and prompt file, and the corresponding session metadata correctly identifies the agent as Cursor.

Important Additional Detail

The checkpoint appears to contain multiple session entries, including one for Cursor.

That may be relevant to the bug.

Likely Root Causes

Most likely possibilities:

1. Cursor renderer bug in the web UI

   • The UI appears to treat Cursor sessions as step-based structured data.
   • It shows 0 steps and then renders nothing.
   • Cursor sessions may need transcript-based rendering instead of step-based rendering.

2. Wrong session selection in checkpoints with multiple session entries

   • The UI may be selecting or partially merging the wrong session payload.

3. UI is not following the transcript path for Cursor sessions

   • The metadata references a valid transcript.
   • The CLI follows it correctly.
   • The web UI may not.

Impact

• Makes it appear that Cursor transcripts were not captured
• Reduces trust in the Cursor integration
• Causes confusion because the CLI and web UI disagree
• Makes checkpoint review less useful for Cursor-authored changes

Steps to reproduce

Reproduction Outline

1. Enable Entire with Cursor in a Git repository.
2. Use Cursor to make a small change.
3. Commit the change so Entire creates a checkpoint.
4. Open the checkpoint in the Entire web UI.
5. Observe that the Cursor section is empty or shows 0 steps.
6. Run:

entire explain --checkpoint <checkpoint-id> --full --no-pager

7. Observe that the transcript is present in CLI output.

Entire CLI version

Entire CLI 0.5.3 (f2ddf9f)

OS and architecture

OS/Arch: linux/amd64

Agent

Cursor

Terminal

No response

Logs / debug output

Additional context

No response

[shurkanTwo]

[gtrrz-victor]

Thanks for reporting this, @shurkanTwo, really thorough writeup. I'm looking into it now.

[shurkanTwo]

Thank's I appreciate it! 👍👍 @gtrrz-victor