What Are Context Files?
Context files are documents that provide persistent background knowledge to agents. Unlike skills (which define behavior), context files supply facts — API specifications, coding standards, product requirements, runbooks, or any reference material an agent needs to give informed responses.
Context files are injected into the [knowledge] section of the system prompt every time an agent processes a request. This means the model always has access to the information without the user needing to paste it into every conversation.
Scopes
Context files are scoped to control who benefits from them:
Organization Scope
Available to all agents for all users. Use for company-wide knowledge:
- Security policies
- Compliance requirements
- Brand guidelines
- Architecture decision records
Team Scope
Available to agents when used by members of a specific team:
- Team-specific coding standards
- Service documentation
- Deployment procedures
- On-call runbooks
User Scope
Personal knowledge available only in your own sessions:
- Personal project notes
- Preferred frameworks and patterns
- Draft specifications you’re iterating on
Creating Context Files
In the UI
Settings → Context Files → Add Context File — choose scope, add a title, paste content, then save.
Business and Enterprise: for team-scoped files, assign the file to the correct team before saving.
Via the Admin Agent
Create an org-scoped context file called "API Design Standards":
Our REST APIs follow these conventions:
- Use plural nouns for resource endpoints (/users, /teams)
- Return 201 for successful resource creation
- Use camelCase for JSON field names
- Include pagination via cursor-based ?cursor= parameter
- All timestamps are ISO 8601 in UTC
- Error responses use {"error": {"code": "...", "message": "..."}} format
Managing Context Files
Go to Settings → Context Files to view, edit, rename, or delete existing files. Or ask the admin agent:
List all context files
Update the "API Design Standards" context file with this content: ...
How Agents Use Context Files
When an agent runs, Auxot includes that agent’s attached context files automatically. Keep files focused and task-specific so responses stay relevant.
For large docs, split one long file into smaller files by topic (for example: API standards, deployment runbook, incident policy).