Skip to main content
Guidance is what you would tell a new colleague on their first day: how you like things written, what the office always does, what it never does. You write it once and the agent reads it at the start of every piece of work.

​
Two levels

Your guidance

Personal instructions and context for the agent when responding to you.Anyone can set their own under Settings → Agent personalization. It applies to your conversations, and to work the agent does when you email it, because the agent acts as the verified sender.

Organization guidance

Instructions the agent follows for everyone in this organization.Set by organization admins under Settings → Agent personalization. Everyone can read it. Only admins can edit it.
Both are given to the agent on every run, organization guidance first and then yours. If they conflict, tell the agent which should win. Better still, fix the conflict.

​
What to put in guidance

​
Guidance, skills or memory?

Keep guidance short. Everything in it is read on every run, so a page of rarely relevant detail dilutes the rules that matter. Put procedures in skills.

​
Guidance and the safety review

Organization guidance is one of the few things the safety review reads when it screens a sensitive action. A rule such as “never delete anything in the Signed folder” therefore shapes how the agent behaves and also what the reviewer holds back.
Guidance tells the agent how to behave. It does not grant access. An instruction like “you may read all projects” does not let the agent see a project you cannot see.