version control (VCS)

basicwidespread

Version control is a method and tool that preserves fixed states of a file or program in sequence, so any earlier version can be searched for and restored.

In plain terms

You likely know the situation: "thesis_final.docx", "thesis_final2.docx", "thesis_REALLY_final.docx". Version control eliminates this chaos: a single file exists, backed by a precise log of who changed what and when, and if the author noted it, why.

Imagine it as both a ship's log and a time machine. If something breaks, you step back to a previous, working state. If you want to know when an error was introduced, you review the entries.

The other major benefit is collaborative work. Several people can work on the same material simultaneously without unintentionally overwriting each other's work: the system keeps track of and merges the changes, and alerts in case of conflict.

Version control has taken on a new role in the age of AI: when a coding agent rewrites files on its own, it acts as a safety net. You can see exactly what the agent touched, and if you saved the state beforehand, you can undo the changes in one step if you don't like the result.

How it works

You create a repository, that is, a folder whose entire history the system tracks.
You work on the files, then when a meaningful unit is completed, you record the state (commit) and briefly describe what you changed.
For every commit, the system stores the change, the author and the timestamp, so the saved versions add up to a traceable history.
If you want to experiment, you open a branch: this is a parallel working copy on which you can try things without endangering the main version.
If the experiment succeeds, you merge the branch back into the main version. Where two people edited the same line, the system flags a conflict, requiring human decision.

An everyday example

If you open the 'Version history' menu in Google Docs and restore yesterday's text, you are already using a simple form of version control. Programmers do the same with code, only in much more detail and more deliberately, typically with a tool called Git.

Who is affected

developerThe basic tool for daily work: without it, it is practically impossible to work in a team or safely adopt modifications made by a coding agent. → Code

entrepreneur, executiveIf your company commissions software, version-controlled code guarantees that the work will not be lost and shows who delivered what.

employeeThe version histories of shared documents, spreadsheets and presentations rely on the same principle and save you from accidental overwrites. → Work & HR

parent, student, teacherIn a thesis or group project, it is traceable who wrote what, and a flawed version does not constitute a catastrophe. → Education & Family

A common misconception

MythVersion control is the same as backup, just for programmers.

In realityA backup keeps a copy in case the data is lost. Version control preserves an interpretable, step-by-step history of changes and coordinates the parallel work of multiple people. Neither replaces the other: even a version-controlled folder stored only on your own machine can be lost.

Limits and risks

It only preserves what you saved; work lost between the two saves is not recovered.
Once something enters the history, it is difficult to remove without a trace, so never save passwords or secret keys into it.
It works really well with text files (code, notes); with large images and videos, it is cumbersome and does not clearly show the differences.
It shows what an agent or a colleague changed, but not whether the change is correct – verification remains your responsibility.

Similar, but not the same

backup – A backup copy protects against data loss, while version control gives a step-by-step traceable history and the ability to restore earlier versions.
Git – Git is a specific version control program, while version control is the method itself, implemented by other tools as well.
GitHub – GitHub is an online service where repositories managed with Git can be hosted and shared; it is not the version control system itself, but the platform built on top of it.

Related concepts

Broader

software development, change tracking

Narrower

Git, commit, branch, merge, repository

On the edge

GitHub, code review, open source, coding agent, backup

A brief history

The first version control system, SCCS, was created in 1972 by Marc Rochkind at Bell Labs. The most widely used tool today, Git, was written in 2005 by Linus Torvalds for Linux development.

Where things stand

At the end of 2026, this is a practically mandatory basic skill in software development, and the market is dominated by Git. The spread of coding agents has made it even more important, as it makes machine-made modifications transparent and reversible.

Status: 2026 November

In the news

Appears in 2 Agent Age stories; the curve shows weekly occurrence in the news magazine.

Anthropic built its own source control for AI-scale code volume, but it is not availableOct 12, 2026 · Code
Cursor releases Origin, a Git host for fleets of AI agentsAug 11, 2026 · Code

Also known as

version control · version control · version control system · version control · version control · version control system · VCS · source control

Sources

Pro Git book: About Version Control

This entry was machine-edited and has undergone machine expert review; the “In the news” section updates automatically from Agent Age stories.