Sessions

A session is a durable agent conversation associated with one project location. Its transcript contains user prompts, assistant turns, reasoning, tool calls, results, errors, permissions, and usage data.

​

Lifecycle

1. A draft tab collects project, workspace, agent, model, prompt, and attachments.
2. The first prompt creates the session and is durably admitted.
3. The runner resolves the model, tools, permissions, and context for the location.
4. Provider turns and tool settlements are persisted and projected into the timeline.
5. Follow-ups can steer or queue work at safe boundaries.

Closing a tab does not delete its session. Sessions can be reopened from home, search, or recently closed history.

​

Manage sessions

Session actions support rename, pin, archive, restore, delete, fork, export, and summarize where available. Inactive sessions are grouped separately after extended inactivity. Deleting a session removes its durable history and should not be confused with closing a tab.

​

Recovery

TurenOS stores prompt admission separately from model execution. Exact retries reconcile by message ID, while conflicting reuse fails. Process-local execution can be interrupted; durable history remains available after restart.