After switching back to a long session, can process history stay intact and open more lightly?

This release group focuses on restoring long sessions and reducing the work required when opening them. Expanded process history should not disappear after switching sessions, and a very long session should not need to load its entire history up front.

The short answer

Yes. Expanded process history now restores more reliably after switching back, while very long sessions load only the process content needed around the current message range, making the initial open lighter.

Process history stays with the session

When you switch away and come back, previously expanded process history is restored more reliably, so you do not have to find and reopen the same parts again.

Long sessions load what you need first

For very long sessions, FinchStory no longer loads all historical process content into the first screen at once. Instead, it loads alongside the messages you are currently viewing. This keeps the history available while reducing unnecessary work during the initial open.

Older sessions recover safely too

If an older session does not contain all of the newer restoration information, FinchStory falls back safely instead of allowing missing state to destabilize the interface.

What's new

Expanded process history restores more reliably after switching sessions.
Previous expanded state is retained.
Long sessions load process content around the current message range.
Very long sessions do less work on initial open.
Older sessions fall back safely when restoration information is unavailable.
FinchStory 1.0.41–1.0.42 · September 13, 2026