Skip to main content
Early access. Continuous updates are not generally available yet. Contact support@qontext.ai to enable them for your workspace.

​
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. Each source can run continuous updates after its initial sync. When Continuous updates is enabled for a source, every new or changed record from later syncs triggers an 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. Continuous updates are disabled by default for new sources. Open the source and turn on Continuous updates under Key information once the repository structure is ready. Only owners, admins, and the source creator can change this setting.

​
How it works

1

A source syncs

Each connected source syncs on its schedule. The initial sync imports the source data whether continuous updates are enabled or not.
2

Continuous updates are enabled

After the initial sync, new or changed records trigger an agent only while Continuous updates is enabled for that source. A sync that brings nothing changes nothing.
3

The agent reads your structure

The agent looks at the folders that could hold the record and reads their 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.
4

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.
5

The change is recorded

Nothing is silently overwritten. Every update and every new file goes through the same change process as any other edit.
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.
.qontext.structure.md
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, so you can always look back or restore.
  • On files with Require review turned on, updates are held for review 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

For a source with continuous updates enabled, its sync frequency determines how often Qontext checks for changes and can start an agent. To get fresher updates from a specific source, raise its sync frequency in the source’s settings.