Write effective Instructions
Give Agent durable preferences, context, and rules without repeating them in every request.
Instructions are guidance Agent should consider on every run. They are sometimes called a system prompt, but you can write them in ordinary language.
Open Settings → Instructions and enter the preferences, context, or rules you want Agent to follow. Changes save automatically.
What belongs in Instructions
Instructions work best for information that should remain useful across many requests:
- Response style: “Keep answers concise and use short bullet points.”
- Defaults: “Prefer my Work calendar unless I name another one.”
- Communication rules: “Always let me review a message before sending.”
- Personal context: “Jamie Chen is my project lead.”
- Working habits: “When a date is ambiguous, ask me to confirm it.”
What belongs in the request instead
Keep one-time details in the request you are making now. A specific document, destination, deadline, or recipient usually should not become a permanent instruction unless it represents a recurring preference.
Do not place API keys, passwords, financial credentials, or other secrets in Instructions.
Write clear rules
Prefer short, direct statements. One rule per line is easy to review and change later.
Instead of:
Be helpful with messages.
Write:
Keep messages under 100 words. Match the language of the original conversation. Always show the draft before sending.
Useful starting template
Response style:
- Keep answers concise.
- Use plain language.
Defaults:
- Prefer my Work calendar.
- Use my current location when I ask for nearby places.
Confirmations:
- Ask before sending messages or email.
- Ask when a date or recipient is ambiguous.Instructions guide Agent, but they do not enable a capability by themselves. The required tool must also be enabled.