Sessions
Sessions - where work happens
A session is one focused work period. You open it, work with your AI, then seal it. That's the entire cycle from your side.
Behind that simplicity: everything you did was captured, organized, and made available to the next session.
Opening a session you named months ago brings all that prior context back into frame. Sessions are never auto-deleted - full history preserved for continuity.
The session lifecycle
Open
Run fai (or fai --continue to resume your last session).
Name your session after what you're working on. Your AI orients with
context from all previous sessions.
Work
Everything that happens - AI conversations, file changes, terminal commands - is captured automatically. You don't trigger captures. They happen continuously.
Seal
When you're done, seal the session. Your captures merge into the pending branch. The next session will inherit everything.
What carries over
After you seal, your work becomes part of the project vault through synthesis. The next session starts knowing:
- What you built and the decisions you made
- Which files changed and why
- Patterns you applied during this session
- Where you said you'd pick up next
Multiple sessions
You can have multiple sessions open at once - one per working context. Each session captures independently. When any session seals, its knowledge propagates to all other active sessions on the project.
This is how team members share context: not through real-time communication, but through the vault. You seal, they inherit.
Sessions list
fai sessions list
Shows all sessions with their current status: active, sealed, or archived.
Next
- → How sessions work - the branch model under the hood
- → Vaults - where session captures go
- → Knowledge flow - how captures become intelligence