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

# Continuous updates

> Continuously check your sources and work every relevant change into your context repository

<Info>
  **Early access.** Continuous updates are not generally available yet. Contact [support@qontext.ai](mailto:support@qontext.ai) to enable them for your workspace.
</Info>

## Overview

Company knowledge doesn't stand still: deals progress, decisions are made, documents change. A repository you'd have to update by hand would be outdated the moment you stop. Continuous updates are what make the context repository self-maintaining.

Every record a sync brings in triggers a continuous update agent. The agent reads your repository and the structure files of the folders that could hold that record, decides what to create, update, or leave alone, and records the result as a change. There is nothing to configure or trigger.

***

## How it works

<Steps>
  <Step title="A sync brings in a record">
    Each connected [source](/sources) syncs on its schedule. Every new or changed record it brings in triggers its own continuous update agent. A sync that brings nothing changes nothing.
  </Step>

  <Step title="The agent reads your structure">
    The agent looks at the folders that could hold the record and reads their [structure files](/features/structure-files), including guidance inherited from parent folders and the workspace root. That guidance says what belongs where, how files are named, and how sure the agent has to be before touching anything.
  </Step>

  <Step title="It decides what changes">
    The agent updates the file the record belongs to, or creates one where your structure says it belongs. It can also delete or reorganize where the folder's guidance allows it. If the record clears no folder's strictness bar, the agent skips it and explains why, rather than forcing a fit or inventing a folder for it.
  </Step>

  <Step title="The change is recorded">
    Nothing is silently overwritten. Every update and every new file goes through the same change process as any other edit.
  </Step>
</Steps>

<Info>
  **Folder structure files.**

  The structure files carry your instructions for a folder: what belongs in it, how files are named, and how careful the agent has to be before changing anything. Whatever you leave unsaid, the agent decides on its own. Read more about them [here](/features/structure-files).
</Info>

```md .qontext.structure.md theme={null}
---
strictness: firm
---

One file per customer, named after the company.
Meeting notes belong in the Meetings subfolder.
```

Change a structure file while updates are running and the new guidance applies from the next time the agent reads it, which means to every record it has not processed yet.

***

## Reviewing continuous updates

Every continuous update appears in the **Changes** tab as an **Automated change**, with a change summary, file diffs, and the sources it's based on, linked so you can trace each update back to the underlying data.

* Each update creates a new [file version](/features/version-history), so you can always look back or restore.
* On files with **Require review** turned on, updates are held for [review](/features/change-reviews) and only applied once someone accepts them. The same happens when an update conflicts with a concurrent edit.
* All other updates are applied automatically.

***

## Update frequency

Syncs are the heartbeat of continuous updates: a source's **sync frequency** determines how often Qontext checks it for changes, and with that, how current the repository stays. To get fresher updates from a specific source, raise its sync frequency in the source's settings.