Before submitting
Area
apps/desktop
Problem or use case
When I switch between sessions in the desktop app, the transcript opens at the end and files opened in the right panel return to the top instead of keeping the positions where I was reading.
I often split a long plan or roadmap across several sessions, with each session implementing a specific part. I keep the relevant plan or source file open beside the transcript and switch between those sessions repeatedly. Losing both reading positions means I have to find the same transcript turn and the same part of the file again on every switch.
Proposed solution
Remember and restore the last transcript viewport for each session, and the last viewport for each open file in that session. A session that was following the live end should still return to the live end; a session where I had scrolled up should return to that reading position.
Why this matters
This would make multi-session roadmap work feel continuous. The transcript and side panel are my working context, so restoring them removes repeated navigation and makes it practical to move between parallel implementation sessions without losing my place.
Smallest useful scope
In-memory restoration while the desktop app remains open. Restore transcript position by session and file position by session plus file path. Persistence across app restarts is not required for a first version.
Alternatives considered
I currently search the transcript again and reopen or scroll through the roadmap file manually after each session switch.
Related work addresses different scroll behavior: #145 stabilizes sticky-bottom behavior and virtualization across thread switches, and #5234 preserves transcript position when the composer grows. Neither restores the previous per-session transcript and file positions.
Risks or tradeoffs
Transcript restoration needs to cooperate with virtualized variable-height rows, paginated history, and live-follow behavior. Explicit file line-reveal requests should take precedence over a saved file viewport.
Examples or references
Contribution
Before submitting
Area
apps/desktop
Problem or use case
When I switch between sessions in the desktop app, the transcript opens at the end and files opened in the right panel return to the top instead of keeping the positions where I was reading.
I often split a long plan or roadmap across several sessions, with each session implementing a specific part. I keep the relevant plan or source file open beside the transcript and switch between those sessions repeatedly. Losing both reading positions means I have to find the same transcript turn and the same part of the file again on every switch.
Proposed solution
Remember and restore the last transcript viewport for each session, and the last viewport for each open file in that session. A session that was following the live end should still return to the live end; a session where I had scrolled up should return to that reading position.
Why this matters
This would make multi-session roadmap work feel continuous. The transcript and side panel are my working context, so restoring them removes repeated navigation and makes it practical to move between parallel implementation sessions without losing my place.
Smallest useful scope
In-memory restoration while the desktop app remains open. Restore transcript position by session and file position by session plus file path. Persistence across app restarts is not required for a first version.
Alternatives considered
I currently search the transcript again and reopen or scroll through the roadmap file manually after each session switch.
Related work addresses different scroll behavior: #145 stabilizes sticky-bottom behavior and virtualization across thread switches, and #5234 preserves transcript position when the composer grows. Neither restores the previous per-session transcript and file positions.
Risks or tradeoffs
Transcript restoration needs to cooperate with virtualized variable-height rows, paginated history, and live-follow behavior. Explicit file line-reveal requests should take precedence over a saved file viewport.
Examples or references
Contribution