Sessions
Sessions represent a conversation with an agent. Each session has its own message history, configuration state, and working directory.
How sessions work
Section titled “How sessions work”Sessions are managed by the agent, not the terminal UI. Local Aether startup asks the agent to create a new session. A remote client either resumes the server’s session (if one exists), or creates a new session.
Starting a new session
Section titled “Starting a new session”/clearThis tells the agent to create a fresh session. The conversation history is cleared. When the new session exposes the same configurable options, Wisp restores the selections you were using before the clear.
Resuming a session
Section titled “Resuming a session”/resumeThis asks the agent for a list of previous sessions. A picker appears listing available sessions — type to fuzzy-search by title or path. When the terminal is wide enough, a preview panel shows each session’s path, last-updated time, model, mode, tool-call count, and recent messages. Select one to restore it — the conversation history and configuration for that saved session are loaded from the agent.
Session state
Section titled “Session state”Each session tracks:
| State | Description |
|---|---|
| Session ID | Unique identifier |
| Title | Agent-generated summary |
| Working directory | The directory the session was started in |
| Config selections | Model, reasoning effort, mode, etc. |
| Conversation history | Full message history (stored by agent) |
When you switch sessions, the configuration options that were active in that session are restored.
Multiple sessions
Section titled “Multiple sessions”You can have many sessions stored by the agent. Use /resume to switch between them. Only one session is active at a time.