# Terminal session persistence

Solo keeps process definitions in local state and keeps terminal output/history for the lifetime of the running process. The terminal pane can detach and [reattach](./reattach.md) to a running process without restarting it.

## What to expect

- Process definitions persist across launches - your commands are still there when you reopen Solo.
- When you return to a running terminal, Solo reconnects the view and refreshes it if the previous view cannot resume cleanly.
- Main-buffer history keeps up to 10,000 retained lines for the current run, subject to an independent 10 MiB raw-output cap. When raw output crosses 10 MiB, Solo removes the oldest raw output until 7.5 MiB remains.
- Runtime terminal output is not permanent archival history across app restarts.
- Selection and transient UI state can reset between launches.

## Agent resume

Agent conversations can outlive the agent process. When a stopped agent's tool supports resuming and Solo has a saved session, you can pick the conversation back up instead of starting fresh. This resumes the provider's agent session; it is separate from terminal frame reattach. See [Stopping and resuming agents](../agents/stopping-resuming-agents.md) for the available actions, saved resume IDs, and provider support.

## Related features

- Use [auto-start](../commands/auto-start.md) if you want processes to resume running automatically when Solo opens.
- If active output is important, copy or save it before quitting or [clearing output](./context-menu.md).

---

Are you a human? Read this doc on the web: https://soloterm.com/docs/terminal/persistent-sessions