FEATURE | ChatPrompt V2: Historical turn view and revert functionality
Resolved π¬ 2 comments Opened Feb 27, 2026 by drdzey Closed Mar 3, 2026
π Description
Add ability to view and revert to historical conversation turns in ChatPrompt V2 extraction panel.
π― Context
When user selects a non-final turn in conversation history:
- Currently shows intermediate result with grayed overlay
- Need to add action buttons for viewing/reverting
β Requirements
UI Changes (ExtractionDetailView)
Add 3 buttons in top-right corner when viewing historical turn:
- ποΈ View This Result
- Removes gray overlay
- Hides buttons 1) and 2)
- Keeps only button 3) visible
- Read-only view of intermediate result
- βͺ Revert to This Result
- Calls new backend API to delete all turns with index > selected turn
- Refreshes entire thread state after successful deletion
- Updates conversation bubbles and result display
- βοΈ View Final Result
- Switches back to the latest/final turn
- Restores normal view (no overlay, no special buttons)
Backend API (new endpoint needed)
DELETE /api/chat/threads/{threadId}/turns?afterIndex={turnIndex}
- Deletes all turns with index greater than specified
- Returns updated thread state
State Management
- Track
IsViewingHistoricalTurnin ViewModel - Track
SelectedHistoricalTurnIndex - Handle overlay visibility based on state
π¨ UI Mockup
βββββββββββββββββββββββββββββββββββββββββββββββ
β [View This] [Revert to This] [View Final] β’ β <- new buttons
βββββββββββββββββββββββββββββββββββββββββββββββ€
β βββββββββββββββββββββββββββββββββββββββββββ β
β βββ Historical result (grayed overlay) ββββ β
β βββββββββββββββββββββββββββββββββββββββββββ β
βββββββββββββββββββββββββββββββββββββββββββββββ
π Files to Modify
src/ViewModels/Panel/ChatPrompts/ExtractionDetailViewModel.cs- state & commandssrc/SVIViews/Panel/ChatPrompts/ExtractionDetailView.xaml- buttons UIsrc/AppraisalData/Abstractions/IChatServiceProvider.cs- new methodsrc/AppraisalData/Logic/ChatServiceProvider.cs- API call implementation- Backend: new endpoint for turn deletion
---
~ Lili
This issue has 2 comments on GitHub. Read the full discussion on GitHub β