Continuous updates
Continuous updates keep the context repository current on their own as connected sources change, without a manual refresh.
Category
Product feature
See all terms
What are continuous updates?
Continuous updates keep the context repository current on their own as connected sources change, without anyone re-triggering a refresh. Each workspace has one context repository, and it updates continuously rather than sitting still between manual syncs.
Why continuous updates exist
Company data changes constantly, and a context repository that only updated when someone remembered to refresh it would drift out of step with the sources feeding it. Continuous updates remove that gap: the repository keeps pace with its sources on its own, so an agent reading from it is working from what's current rather than what was current the last time someone checked.
How do continuous updates work?
Continuous updates run underneath the native connectors that sync source data in, applying the same logic whether a file was written automatically or edited by hand. A person can edit a file's structure or content directly through the UI or through MCP, and Qontext keeps updating that file as the underlying source data changes, rather than treating a manual edit as the end of that file's automated maintenance. Build time for a workspace's initial repository varies by scale: small workspaces typically finish in minutes, while large ones with many sources can take longer.