Display summaries chronologically within session timeline #96

New issue

Closed

opened 2026-01-22 21:45:22 +00:00 by jack · 0 comments

jack commented

2026-01-22 21:45:22 +00:00

Owner

Problem

A session can have multiple summaries. Currently these summaries appear only at the top of the session view, but they should appear chronologically between the steps where they were actually created.

Current Behavior

Summaries are grouped/displayed at the top of the session
No visual indication of when during the session a summary was created

Desired Behavior

Summaries should appear inline within the session timeline
Position them chronologically based on their creation timestamp
This shows the natural flow: work → summary → more work → another summary → etc.

Why This Matters

Seeing where summaries occur helps understand session structure
Users can follow the progression of work more naturally

Implementation Notes

Summaries have timestamps like other observations
Sort all observations (including summaries) by timestamp
Consider visual distinction for summary entries (different card style, divider, etc.)
TODO: Review summary trigger schema before implementation

## Problem A session can have multiple summaries. Currently these summaries appear only at the top of the session view, but they should appear chronologically between the steps where they were actually created. ## Current Behavior - Summaries are grouped/displayed at the top of the session - No visual indication of when during the session a summary was created ## Desired Behavior - Summaries should appear inline within the session timeline - Position them chronologically based on their creation timestamp - This shows the natural flow: work → summary → more work → another summary → etc. ## Why This Matters - Seeing where summaries occur helps understand session structure - Users can follow the progression of work more naturally ## Implementation Notes - Summaries have timestamps like other observations - Sort all observations (including summaries) by timestamp - Consider visual distinction for summary entries (different card style, divider, etc.) - **TODO**: Review summary trigger schema before implementation