Add Turn IDs/Labels to Conversation History for Easy Reference

Resolved 💬 3 comments Opened Jan 7, 2026 by raybenchen Closed Feb 20, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

---
Proposed Feature Request:

Title: "Add Turn IDs/Labels to Conversation History for Easy Reference"

Description:

Problem:
Currently, there's no easy way to reference specific turns in a conversation within the same session. When discussing complex topics that span many exchanges, users need to say things like "go back to what we discussed earlier" or copy/paste content, which is inefficient.

Proposed Solution:
Add a turn ID or label to each user/assistant exchange that:

  1. Is visible in the UI (e.g., small label like #15 or Turn 15)
  2. Can be referenced in subsequent messages (e.g., "continue from #15" or "/goto 15")
  3. Is preserved in session history for resumable sessions

Use Cases:

  • Long architectural discussions where user wants to backtrack to a specific decision point
  • Reviewing and continuing from a specific analysis in a previous exchange
  • Session logging and documentation (referencing specific turns in saved logs)
  • Collaborative work where external team members reference specific conversation points

Example UI:
[Turn 15] USER: Let's discuss the architecture
[Turn 16] CLAUDE: Here are three options...
[Turn 17] USER: Go back to turn 15 and take option 2 instead

Related:

  • Would integrate well with /resume functionality
  • Could enhance session export features
  • Useful for skills that process conversation history

---
Would you like me to:

  1. Submit this on your behalf? (I can't directly, but I can provide the exact text)
  2. Refine the request? (Add more details, use cases, etc.)
  3. Create an issue template file you can copy/paste to GitHub?

Also: This feature would be perfect for our session logging use case - we could reference turns by ID in the saved logs!

Proposed Solution

---
Proposed Feature Request:

Title: "Add Turn IDs/Labels to Conversation History for Easy Reference"

Description:

Problem:
Currently, there's no easy way to reference specific turns in a conversation within the same session. When discussing complex topics that span many exchanges, users need to say things like "go back to what we discussed earlier" or copy/paste content, which is inefficient.

Proposed Solution:
Add a turn ID or label to each user/assistant exchange that:

  1. Is visible in the UI (e.g., small label like #15 or Turn 15)
  2. Can be referenced in subsequent messages (e.g., "continue from #15" or "/goto 15")
  3. Is preserved in session history for resumable sessions

Use Cases:

  • Long architectural discussions where user wants to backtrack to a specific decision point
  • Reviewing and continuing from a specific analysis in a previous exchange
  • Session logging and documentation (referencing specific turns in saved logs)
  • Collaborative work where external team members reference specific conversation points

Example UI:
[Turn 15] USER: Let's discuss the architecture
[Turn 16] CLAUDE: Here are three options...
[Turn 17] USER: Go back to turn 15 and take option 2 instead

Related:

  • Would integrate well with /resume functionality
  • Could enhance session export features
  • Useful for skills that process conversation history

---
Would you like me to:

  1. Submit this on your behalf? (I can't directly, but I can provide the exact text)
  2. Refine the request? (Add more details, use cases, etc.)
  3. Create an issue template file you can copy/paste to GitHub?

Also: This feature would be perfect for our session logging use case - we could reference turns by ID in the saved logs!

Alternative Solutions

Add Turn IDs/Labels to Conversation History for Easy Reference

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗