Sessions & persistence
Run multiple agent sessions per project and never lose a conversation — Open Free Max resumes each tab from the CLI's own durable store.
An agent session is one running CLI in its own tab. A project can host several at once — same provider or different ones.
Multiple sessions
Open as many sessions as you need per project. Each runs in its own embedded terminal (PTY). Two Claude sessions in the same project are numbered so you can tell them apart. From Mission Control you can see and steer all of them across every project.
Why a conversation can’t be lost
This is the bug other tools can’t fix, fixed by design. OFM never owns the transcript. The agent CLI already writes every message to its own store on disk. OFM keeps only a tiny map of which sessions are open.
- Close the app → the session map is saved.
- Reopen → each tab is relaunched via the CLI’s own
--resume, and the full transcript replays. - Map lost or corrupt? → OFM rescans the CLI’s project history on disk and rebuilds it.
Because the durable history lives in the CLI (not a re-implemented store), it can’t be corrupted by OFM.
Resume semantics
Resume support depends on the provider: Claude Code resumes a specific session by id
(--resume <uuid>); others resume the most recent (resume --last, --continue). OFM uses
the best available per provider. See Supported agents.
A note on boot
At startup OFM clears any orphan PTYs from a previous run and then restores your session from the saved snapshot — so a reload or crash never leaves zombie agent processes behind.