Skip to main content
The agent is most useful when you treat it as a capable colleague who is new to the file: able, quick and well read, but dependent on you for the context and the standard. These habits make the biggest difference.

​
Brief it like a colleague

A good brief covers four things.
1

The goal

Say what you are trying to achieve, not only the task. “Draft a reply” is a task. “The client is anxious about the delay. Reassure them, and get the missing certificate by Friday” is a goal.
2

The material

Reference the documents, or make sure you are in the right project or matter with Include what you’re looking at switched on. Do not describe a document that you could point to.
3

The standard

Language, length, audience, format. If there is a model to follow, reference it: “in the style of the letter we sent to the Anderssons”.
4

The boundaries

Say what it should not do, and when to stop and ask. “Don’t contact anyone. If the NIE is missing, ask me.”

​
Match the tool to the job

​
Review like a supervisor

The agent’s work is a draft until you have checked it. The product is built to make checking quick.
  • Tracked changes. Accept and reject individually. Read the deletions as carefully as the insertions.
  • Sources. When the agent cites a document, open it. When Populate shows Contradicted or Insufficient, treat the value as unverified.
  • What was touched. After each turn, open the items the agent lists as edited, moved or filed.
  • Recipients. On every drafted email, check To and Cc before the text.
The agent can be wrong in a fluent, confident voice. It can misread a scan, merge two people with similar names, or state a legal position that was superseded. It does not replace your professional judgment, and nothing it produces should reach a client or a registry unreviewed.

​
Correct it, then teach it

When the agent gets something wrong, fix the instance, then ask whether it will come up again.
  • A one-off: just say so. “That’s the wrong Pérez. The buyer is María Pérez Gil.”
  • A preference: “Remember that I write dates as 14 March 2026”, or add it to your guidance.
  • A procedure: “Save that as a skill.”

​
Keep conversations focused

  • One subject per conversation. The agent re-reads the conversation on every turn. A long, mixed conversation is slower, costs more and blurs the instructions.
  • Start fresh when the subject changes. Your memory and guidance carry over. The clutter does not.
  • Use matters for long-running work. A matter keeps the description, documents, conversations and history together in a way a single chat cannot.

​
Work safely

  • Keep the default permission level, Approve for me, unless you have a reason to change it.
  • For anything irreversible, such as a deletion, a submission or a message to the other side, have the agent prepare and do the final step yourself.
  • Do not paste passwords or card numbers into a conversation. For websites that need a login, use a browser session and sign in yourself.
  • If something the agent read appears to be giving it orders (“ignore your previous instructions…”), that is a red flag about the document, not a fault in the agent. Tell your admin.

​
When it is not working

It probably lacks your material. Reference the documents and say who the reader is.
Check where the document lives. The agent sees what you can see, in the project you are working in. A file in your private vault is not visible from a project conversation unless you reference it. Newly uploaded files take a short while to become searchable.
You are probably on Ask for approval. Switch to Approve for me, or use Always allow in this thread for the action in question.
It reached its step or time limit. Reply “continue”. For large jobs, ask for a plan and approve it in stages. See Limits.
Try a stronger model for drafting, and give it an example of writing you like.