- Steer your agent or team toward specific behaviors or roles.
- Constrain or expand your agent or team’s capabilities.
- Ensure outputs are consistent, relevant, and aligned with your application’s needs.
- Enable advanced use cases such as multi-step reasoning, tool use, or structured output.
- System message: The system message is the main context that is sent to the agent or team, including all additional context
- User message: The user message is the message that is sent to the agent or team.
- Chat history: The chat history is the history of the conversation between the agent or team and the user.
- Additional input: Any few-shot examples or other additional input that is added to the context.
Context Caching
Most model providers support caching of system and user messages, though the implementation differs between providers. The general approach is to place repetitive content and common instructions in a stable request prefix that the provider can reuse across requests. Prompt caching reduces the cost and latency of processing that repeated prefix. The complete prompt is still included in each request. Agno’s context construction is designed to place the most likely static content at the beginning of the system message.If you wish to fine-tune this, the recommended approach is to manually set the system message. Some examples of prompt caching:
Learn more
Context Engineering for Agents
Craft system messages and instructions for agents.
Context Engineering for Teams
Configure context for multi-agent coordination.
Chat History
Include conversation history in context.