Instructions and behaviour
Configure the organisation, Project and task-level instruction layers that shape how the Agent approaches work.
Set the Agent's general behaviour before encoding individual tasks.
Project-level instructions
In the current product, Project description is the Project-level instruction channel. It is injected into the Agent at the start of a session. Use it to explain both what the Project is for and durable behavioural rules that should apply across the Project.
The same Settings surface also contains Agent tone, which changes response style rather than business rules, plus current Project controls such as organisation branding.
A practical instruction stack is:
Organisation and user context — broad background captured outside the Project.
Project description — persistent Project purpose and cross-task behavioural direction.
Skills — task-specific methods, checks and tools for recurring work.
Session context — the current task, attachments, evidence and conversation.
Do not duplicate the same rule across all of these layers. Put it at the narrowest durable level that fits.
Start with responsibility, not personality
Write down what the Agent is responsible for in business language. For example:
Handle incoming sales-order questions for the Benelux order desk. Use the connected ERP for current customer and order facts. Do not invent product mappings or commercial terms. Ask when a requested customer or product cannot be resolved confidently.
A good Project-level setup usually establishes the operational area the Agent owns, authoritative sources, important boundaries, business terminology and what a satisfactory result looks like.
Put task-specific method in Skills
Rules that only apply to one recurring task belong in that Skill. Maintained business facts belong in Tables, Knowledge or the source system rather than being copied into instructions.
After changing Project-level instructions, rerun representative work because the change can affect many sessions.
Last updated
Was this helpful?