Custom Context

Custom context lets you give the AI Assistant organization-specific knowledge about your cloud environment. This knowledge is injected at the start of a conversation, so the assistant can reason about things that aren’t visible in your resource data — like how your teams are organized, what your tagging conventions mean, or which environments map to which accounts.

Custom contexts are created by organization administrators and are available to all users.

What to put in a custom context

Custom context is a plain-text document. Useful content includes:

• Environment structure — which AWS accounts or GCP projects belong to production, staging, or dev
• Tagging conventions — what tags like team, cost-center, or env mean in your organization
• Naming patterns — how your teams name VPCs, buckets, or service accounts
• Ownership information — which team owns which set of resources
• Business context — compliance requirements or policies that affect how you interpret your infrastructure

Example:

Our AWS account IDs map as follows:
- 123456789012: production
- 234567890123: staging
- 345678901234: development

All production resources are tagged with env=prod. The "team" tag maps to our Slack channels.
Security team owns all resources tagged with team=security.

Creating and managing contexts

1. Open the AI Assistant on the Platform Home page
2. Click Add Context, then Manage Context documents
3. Create a new context document, give it a name, and paste your content
4. Save the document

To delete or edit a context, return to Manage Context documents from the same menu.

Auto-include

Each context document has an Auto-include toggle. When enabled, the document is automatically added to every new conversation for all users in the organization. This is the recommended setting for shared organizational knowledge that should always be available to the assistant.

You can also select context documents manually at the start of a conversation if you want to include them selectively.

Timing

Limits

Keep context documents focused and concise. The byte limit is intentional — a document that tries to describe everything will use token budget that the assistant needs for reasoning.

Next steps

• AI Assistant Overview — How the assistant works and how to configure data access modes