Chat & Sessions

Use sessions to give the Agent work, keep related context together, and return to the evidence and outputs later.

A session is one piece of work with the Agent. It keeps the conversation, files, tool activity and outputs for that work together.

Sessions are useful because operational work rarely fits into one prompt. You may need to add a file, answer a question, inspect a result, correct something and continue.

Keep one piece of work together

Use the same session while you are still working on the same outcome.

For example, if you ask the Agent to review a supplier confirmation, then provide a missing purchase order and ask it to update its conclusion, those steps belong together.

Start a new session when you are moving to genuinely different work. This keeps the context easier to understand and the resulting history easier to inspect later.

Give the Agent enough context

A useful request normally makes four things clear:

• Outcome — what you need to get done.

• Relevant material — files, systems, Skills or other context it should use.

• Constraints — what it may or may not do.

• Evidence or output — what you want back so you can judge the result.

You do not need to describe every intermediate step. The Agent can choose an approach using the capabilities available to it.

Follow the work, not just the final answer

A session can contain more than chat messages. Depending on the task, you may see tool activity, files, requests for input and other evidence of what the Agent did.

For important operational work, this history matters. A confident final sentence does not by itself prove that the underlying work was correct.

When needed, inspect:

• which systems or tools were used;

• which files or information informed the result;

• where the Agent encountered uncertainty;

• what was created or changed;

• whether human input was required.

For broader execution history and traces, see Monitoring activity.

When the Agent needs you

The Agent may need information, a decision or approval before it can continue safely.

That is a normal operational boundary, not a failed run. Respond in the session when the handoff appears. Requests that need separate attention can also appear in the Request Inbox.

Working through Slack or Microsoft Teams

Where configured, the Agent can also be used through messaging surfaces such as Slack or Microsoft Teams.

The surface changes, but the principle does not: the conversation is still operational work carried out with the capabilities and access available to that Agent context.

Context across sessions

A new session gives you a fresh conversation. Some project-level context may still be available through project configuration, Skills, Knowledge Bases, Memory and connected systems.

Do not rely on conversation history or Memory for information that must be exact and authoritative. Put durable operational truth in the appropriate source system, Skill, Knowledge Base or maintained data source.