Context is what an agent reads before every run. It is the difference between a draft you can publish and a draft about somebody else's business.
Answer four questions, not a blank box
Each agent's scope of work asks four short questions: what it should know about the work, who it is working for, what a good week looks like, and anything it should never do. An example sits in each box as grey placeholder text - it is there to show the shape of a good answer, not to be kept.
Two or three sentences each is plenty. Specific beats long:
We are pushing the lifetime hand-tool warranty this quarter. The competitors worth watching are Forge & Co, Tradeline and Sitewise.
Type the company once
About your business at the top of the roster - and on the Organisation page - holds what every agent in the project shares: what the business does, who its customers are, how agents should sound, and what none of them should say.
Every agent inherits it automatically. Nothing is copied into them, so editing it once changes what all of them read from their next run on. Their own four questions are then only about what is different for that role.
Let your documents do the first draft
Once anything is uploaded, Draft this from my documents has the agent read what you have and propose answers. It fills only the questions you have left empty, never overwrites what you typed, and leaves a question blank when the documents do not support an answer.
Read the draft before saving it. These answers become standing instructions, and a document can be out of date.
What good context changes
- Research picks the right competitors instead of the famous ones.
- Drafts sound like your business on the first attempt.
- "Never" answers stop the agent volunteering discounts, dates or opinions you did not authorise.
Where it shows up
Open any agent's Prompt preview to see exactly what a run reads: the project's shared context first, then that agent's own, then its objectives.