Context recovery

Find the thread, recording, or agent change that explains what happened.

Use conversations, recordings, and agent history when work should continue from existing context, when a decision needs evidence, or when an answer changed and you need to understand why.

The Product Specification documents the exact Recordings, Conversations, and Agent History views. This guide focuses on choosing the right evidence and carrying it forward safely.

Pick The Right History Source

Continue a conversation

Use the existing conversation when the same source files, tool results, approvals, or decisions should still influence the next answer.

Summarize a recording

Use a recording when you need meeting decisions, owners, risks, customer asks, or follow-up tasks extracted from a call.

Explain a behavior change

Use agent history with feedback and conversations when an agent used to answer correctly but now follows a different prompt, tool, data source, or access rule.

Real User Scenarios

Resume a customer answer

Open the last conversation, ask the agent to restate the current answer, missing evidence, and recommended next action. Create a Task if someone should own the follow-up.

Turn a meeting into work

Ask for decisions, owners, due dates, unresolved risks, and suggested tasks. Keep task creation in draft mode until the owners and deadlines are confirmed.

Audit a tool action

Use the conversation and Tool Executions together: the conversation explains intent, while Tool Executions show the exact function, arguments, approval, result, and error.

Start fresh safely

When the old thread contains the wrong customer, stale policy, or unrelated tool result, create a new conversation and paste only the facts that should carry forward.

Conversation Or New Chat

Use the same conversation when you need continuity:

• The source files or pasted context are still relevant.
• The agent already asked clarifying questions.
• A tool action, approval, or generated file belongs to the same work.
• You need to turn the thread into a Task or share it with another user.

Start a new chat when the topic, customer, permissions, or required source changes. This prevents stale context from shaping the next answer.

Recording Prompt Pattern

Summarize this recording into decisions, owners, risks, open questions,
and follow-up tasks. Do not create tasks until I approve the list.
Mark anything that was discussed but not decided.

For customer calls, add:

Separate customer commitments from internal ideas. Include exact next steps,
owner, due date, and which source or speaker supports each action item.

When The Answer Changed

If an agent behaves differently than before, check in this order:

1. Conversation context: did an old instruction or file influence the answer?
2. Agent prompts: did the role, constraints, or expected output change?
3. Data and Memory: was a source attached, removed, stale, or reprocessed?
4. Connections and tools: did access, function confirmation, or an external account change?
5. Feedback and history: did someone approve a prompt improvement or configuration edit?

Handoff Checklist

Link the conversation or recording.Name the agent used for the work.List source files, data collections, or memory pages.Include tool action status and approval state.State what is already decided and what still needs review.Create a Task when ownership or status tracking matters.

Use Tasks to Track Work when the recovered context needs an owner, status, or review step. If the issue comes from a changed shared setup, ask an admin to follow Monitor Usage, Audit Logs, and Risk.