Work with documents in Chat

Goal

Control the context Chat uses and turn its answer into verifiable project content.

Select context

• No reference: for general questions.
• Current document: for summarizing or rewriting the open document.
• @ document: to explicitly include a complete document.
• Selection: to include only the selected passage from the editor.

Precise references make answers easier to verify. For multi-document tasks, state the purpose of each document.

State the task

Include context, task, output, and constraints:

Using the current document and @Meeting notes, create this week's action list.
Return a table with task, owner, due date, and risk.
Use only information stated in the documents; mark missing values as “TBD.”

Manage conversations and models

• Keep one topic per conversation.
• Start a new conversation for temporary work and archive it afterward.
• Switch models from the top of Chat.
• If a long conversation drifts, start a new one and reference the key documents again.

You can send follow-up requests while Chat is responding; they enter a queue. Reorder or remove queued messages when priorities change.

Tool requests

For files, Shell, or external tools, check the target, path, and impact before allowing or rejecting the request. See Shell and Agent for the approval rules.

Write back and verify

Before writing an answer into the project, check:

• names, numbers, and dates against the source;
• quotations and links;
• whether unknown values remain marked;
• whether the final wording reflects your judgment.

Completion check

• Chat can identify the documents it used.
• The output matches the requested format.
• The result is verified and written into a project document.

Common issues

• The answer ignores your material: reference documents with @ and state their purpose.
• Other topics leak into the answer: start a new conversation with only the necessary context.
• No model is available: check the account, model catalog, and default text model.