Version history
Version history tracks every change to a file in the context repository, showing where each version came from.
Category
Product feature
See all terms
What is version history?
Version history shows how a file changed over time. It lists every version with its source, change type, a version identifier, and a timestamp. Source records where a change came from, a connected source or a workspace member. Change type is either an automated change, from connected source data such as new CRM activity or updated documentation, or a direct update, made through the Qontext platform, MCP, or the API. The version marked latest is the current editable version of the file.
Why does version history exist?
A file in the context repository can change through several paths. A connected source can update it automatically as its data changes, and a person or an agent can update it directly through the platform, MCP, or the API. Without a record of each of these, nobody could tell why a file looks the way it does right now, or check what it said before the last change. Version history keeps every one of those changes visible in order, so a file that maintains itself doesn't turn into a black box.
How does version history work?
Each version entry logs where the change came from, whether it was automated or direct, a version identifier, and when it happened. Selecting any entry other than latest opens that version in read-only mode, so someone can inspect what the file said at that point without changing the current file. Every version becomes part of the file's record in the context repository, alongside other versioning tools like change reviews.