Every conversation you have with Pi is a session. Sessions have their own history and context — the model remembers everything said within a session, but starts fresh in a new one. A single project can have as many sessions as you like.
Where sessions live
Sessions auto-save to ~/.pi/agent/sessions/, organized by working directory. Each one is a JSONL file with a tree structure — more on the tree part in the next lesson.
Starting a new session
Type /new in the prompt to start fresh. The current session stays in your history; you can always come back to it.
Naming and resuming sessions
Give a session a name so it’s easier to find later:
/name Refactor auth moduleOr set it at startup:
pi --name "Refactor auth module"To pick up a past session:
/resume— opens an interactive picker of past sessions for the current project.pi -r— opens the same picker, but at startup from your terminal.pi -c— skips the picker and continues your most recent session directly.
Type /session any time to see info about your current session: file path, session ID, message count, tokens used, and cost.
Saving and sharing a session
Two different commands, for two different needs:
/export [file]— writes the session to HTML or JSONL, saved locally. No account needed. Good for keeping a record or reviewing a session outside the terminal./share— uploads the session as a private GitHub gist with a shareable HTML link. This needs GitHub authentication, which we haven’t set up yet — you’ll get to the full git/GitHub setup in the “Use Git and GitHub” exercise later in the course. For now, just know the command exists.
Exercise: read your own session file
Session files aren’t locked behind a special export command — they’re just JSONL, readable directly.