> ## Documentation Index
> Fetch the complete documentation index at: https://docs.suppio.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Context

> Add and manage the knowledge Suppio uses to answer support questions.

Context is the knowledge your agent uses when it answers.

Suppio requires context before an agent can be deployed or used through the API. Without active context, Suppio cannot generate grounded support replies.

<Warning>
  If an agent has no context, deployment methods are blocked or requests are rejected.
</Warning>

## Supported context sources

<AccordionGroup>
  <Accordion title="Plain text">
    Paste short notes, policies, FAQs, troubleshooting steps, or instructions directly into Suppio.
  </Accordion>

  <Accordion title="File upload">
    Upload a local `.txt` file. Other file formats are not accepted by the context uploader.
  </Accordion>

  <Accordion title="Website upload">
    Import website pages from public URLs. This works well for help centers, docs, landing pages, and product pages.
  </Accordion>

  <Accordion title="Mintlify docs">
    Connect a Mintlify documentation site by pasting a documentation URL.
  </Accordion>

  <Accordion title="GitBook">
    Import a GitBook space by pasting a GitBook URL.
  </Accordion>

  <Accordion title="Discord forum posts">
    After Discord is connected, import the starter content from up to 30 selected forum posts so Suppio can learn from useful past answers.
  </Accordion>

  <Accordion title="Follow channels">
    After Discord is connected, follow up to 10 selected channels so Suppio can retain their latest messages. New messages and edits to retained messages update the source automatically.
  </Accordion>

  <Accordion title="Live status page">
    Connect Atlassian Statuspage, Better Stack, Instatus, incident.io, or Status.io. Suppio checks the live provider when a user asks about outages, incidents, maintenance, or service health.
  </Accordion>

  <Accordion title="Shared agent context">
    When creating another agent in the same workspace, you can sync context from an existing agent instead of uploading everything again.
  </Accordion>
</AccordionGroup>

## Add context

<Steps>
  <Step title="Open the agent">
    Go to the workspace, choose the agent, and open **Context**.
  </Step>

  <Step title="Choose a source">
    Add text, upload a TXT file, import website pages, or choose an available documentation, Discord, or live status source.
  </Step>

  <Step title="Wait for processing">
    Suppio shows context source status while it processes and indexes content.
  </Step>

  <Step title="Test the agent">
    Ask real support questions in the sandbox to confirm the agent can find the right information.
  </Step>
</Steps>

## Manage existing context

Open a context card's menu to view, rename, or remove it. Plain-text and imported text content can be edited in the dashboard. Followed-channel sources use **Manage** to change which channels are tracked.

If agents share synced context, uploads, edits, renames, and removals apply to every agent in that sync group.

## Adaptive memory

Adaptive memory stores small notes and summaries that should influence future replies.

It can be updated from Discord with:

* `/learn` to save a manual note
* `/train` to propose reusable staff-confirmed guidance from the current ticket or forum post
* a reply that mentions Suppio with `remember`
* approved knowledge suggestions created after ticket or forum handoffs

Use adaptive memory for high-value corrections, repeated support guidance, and short policy notes. Do not use it as a replacement for full documentation.

Adaptive memory has an 800 KB limit and does not count as the active context required to unlock deployment methods.

## Knowledge quality

On every plan, **Context** surfaces missing knowledge, conflicting sources, and learning suggestions. You can inspect the supporting conversation or source, enter a correction, apply proposed context edits, or ignore the issue.

See [Knowledge gaps and conflicts](/knowledge-gaps).

## Source quality tips

* Prefer current docs over old chat messages.
* Remove outdated setup instructions before uploading.
* Keep one source focused on one topic when possible.
* Include exact names for plans, commands, products, and settings.
* Add screenshots or images only where the deployment supports image understanding.
* Re-test common questions after major context changes.

## Limits

Limits vary by plan. The pricing table currently lists:

| Plan       | Context uploads |
| ---------- | --------------: |
| Free       |               6 |
| Plus       |              10 |
| Pro        |              20 |
| Enterprise |              40 |

File size limits also vary by plan:

| Plan       | Maximum file size |
| ---------- | ----------------: |
| Free       |            800 KB |
| Plus       |              3 MB |
| Pro        |              5 MB |
| Enterprise |             10 MB |

Website context can include up to 100 selected pages from the full dashboard context manager. The onboarding importer accepts up to five starting links. Website, Mintlify, and GitBook sources can be configured to refresh automatically.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Suppio says context is required">
    Add at least one active context source to the agent, then retry deployment or API key creation.
  </Accordion>

  <Accordion title="Answers are inaccurate">
    Add the missing policy or troubleshooting detail as context, remove outdated sources, and test again in the sandbox.
  </Accordion>

  <Accordion title="Discord context sources are unavailable">
    Connect Discord first. Forum posts and followed channels require a Discord deployment connection.
  </Accordion>

  <Accordion title="Website upload fails">
    Confirm the URL is public, reachable, and not blocked by the website upload filters.
  </Accordion>

  <Accordion title="A file format is rejected">
    Convert the content to UTF-8 plain text and upload a `.txt` file, or paste it with **Plain text**.
  </Accordion>

  <Accordion title="A followed message edit is missing">
    Edits update only messages still inside the followed channel's retained recent-message window. Editing an older message does not re-add it ahead of newer updates.
  </Accordion>
</AccordionGroup>