# Chat & Sessions

### How Sessions Work

Every conversation with the Operator Agent is a **session** (also called a thread). A session preserves the full context of your conversation — messages, uploaded files, generated outputs, and the agent's working memory.

You can:

* **Start a new session** at any time from the agent home screen
* **Continue an existing session** by selecting it from the session list in the sidebar
* **Run multiple sessions** for different tasks or topics

### Session Privacy

Sessions are scoped to your user account. Other users in the same project cannot see your sessions, and you cannot see theirs. Each person's agent conversations are private by default.

> 💡 Admin-level visibility of all sessions may be added in the future, but is not currently available.

### Session List

The sidebar shows your recent sessions. Each entry displays the session topic or first message, making it easy to find and resume previous conversations.

### Context Within a Session

The agent remembers everything within a session — previous messages, file uploads, skill results, and generated outputs. You can refer back to earlier parts of the conversation naturally:

* *"Use the same format as the report you generated earlier"*
* *"Now do the same thing for the second file I uploaded"*
* *"Actually, change the date column to DD/MM/YYYY"*

For very long sessions, the agent manages its context window automatically to stay within model limits.

### Starting Fresh

If you want to start a task from scratch without any prior context, open a new session. Each session is independent — the agent does not carry context between sessions.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lleverage.ai/operator-agent/chat-and-sessions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
