> ## Documentation Index
> Fetch the complete documentation index at: https://trytilde.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Sessions

> Review every conversation an agent has had: messages, reasoning, tool calls, security decisions, logs, and traces.

A session is one conversation thread between an agent and the people, or other agents, it talks to. Tilde records each session, so you can review what an agent was asked, what it did, and why.

Tilde uses three related terms:

* A **session** is the whole conversation thread.
* A **run** is one objective the agent works on within a session. A run can pause and resume.
* An **invocation** is one active reasoning loop inside a run.

## Review a session

<Steps>
  <Step title="Open the Sessions tab">
    In the Agent Registry, open the agent and select **Sessions**. Tilde lists the agent's sessions with their channel, message count, and last activity.
  </Step>

  <Step title="Open a session">
    Select a session to read it as a conversation. Tilde shows the recorded messages, the agent's reasoning, and its tool calls in order.
  </Step>

  <Step title="Drill into a step">
    Open any step to see its trace. The waterfall shows each model call and tool call, with input, output, metadata, and latency.
  </Step>
</Steps>

## What a session records

| Record | What it contains |
| - | - |
| Messages | Every message in the thread, from every participant and channel. |
| Reasoning | The agent's working notes. They are recorded as activity, and are never sent to the user. |
| Tool calls | Each tool the agent called, with its input after [security middleware](/docs/security/middleware) screened it. |
| Goals and tasks | The objectives the agent set for itself, and their status. |
| Security decisions | Each flagged, redacted, or blocked message, with the guard, label, and score. Tilde Enterprise only, for now. |
| Attachments | Files exchanged in the conversation. Tilde encrypts attachment bytes. |
| Channel metadata | The provider, the connection, and the participants' identities. |

Tilde stores messages and immutable audit snapshots in your PostgreSQL database, so later edits do not rewrite history.

## Follow a session across tabs

The session ID ties the agent's tabs together.

* In **Logs**, filter by session, run, or invocation to read the agent's structured logs for that conversation. See [OpenTelemetry](/docs/integrations/opentelemetry).
* In **Tracing**, filter observations by session. See [Traces](/docs/traces).
* In **Inference**, see what the agent's LLM requests cost. See [Inference providers](/docs/inference-providers#usage-and-cost).

## Protect session data

Sessions contain your users' conversations. Restrict operator access through your identity provider, and encrypt the PostgreSQL disks and backups. See [Security overview](/docs/security/overview#audit-data-for-every-session).