Context
Context is what your agents already know before you ask them anything. It is the background you would give a new coworker on their first day.
Without it, you end up repeating yourself. With it, you say what you want once and it sticks.
What to put in it #
Good context is the stuff that is true every time:
- Who you are. "I run a two-person design studio."
- How you like things. "Keep writing short. No exclamation marks."
- Where things live. "Client work is in the Clients folder."
- What to avoid. "Never change anything in the archive folder."
- Words you use. What your team means by a term that might mean something else elsewhere.
What to leave out #
- One-off details. If it only matters for today's task, just say it in Chat.
- Anything secret you would not write down. Context is stored encrypted, but keys and passwords belong in Settings, which is built for them.
- Long documents. Attach those to a chat instead. Context is for standing instructions, not reference material.
Editing it #
- Go to Context.
- Pick which agent you are editing, or the shared context all agents see.
- Write in plain words. Sentences are fine — you do not need a special format.
- Save.
Changes apply to new work right away. Work already running keeps the context it started with, so nothing changes under its feet mid-task.
Shared and per-agent #
There are two levels:
- Shared context — everything every agent should know. Most of what you write goes here.
- Per-agent context — extra instructions for one agent doing a particular kind of job.
Start with shared. Only split things out when you find one agent needs to know something the others do not.
Writing context that works #
Be direct and concrete.
Instead of "be professional", write "no slang, no emoji, and always use the client's full company name."
Instead of "be careful with files", write "never delete a file — move it to the Old folder instead."
The more specific you are, the less you will need to correct later.
Tip When you catch yourself correcting the same thing twice, that correction belongs in context.
Keeping it tidy #
Context is read every time your agents work. A short, sharp context works better than a long rambling one. Review it every so often and cut what no longer applies.
