Git
Git is a version control program that records every change to a project's files, allowing any previous state to be restored and enabling multiple people to work simultaneously.
In plain terms
You likely know the folder containing 'thesis_final', 'thesis_final2', and 'thesis_REALLY_final'. Git eliminates this chaos. You have a single folder, while the program records every saved state in the background, including who changed it, when, and why.
Imagine it like save points in a game. If something breaks, you step back to an earlier point. If you want to try a bold idea, you open a side thread. If it fails, you simply discard it, leaving your original work untouched.
Another major strength is collaborative work. Dozens, or even thousands, of people can work on the same program without overwriting each other's work, because Git can merge changes made on separate branches.
In the era of coding agents, it has also taken on a new role: serving as a safety net. When an AI agent rewrites a bunch of files, Git shows exactly what changed, and anything you dislike can be undone with a few commands.
How it works
- In the project folder, Git creates a hidden repository (repo for short) and keeps the full history in it.
- When you have completed a meaningful unit, you select the changes to keep and record them with a short message. This save point is the commit.
- If you want to try something new, you open a branch. This is a parallel workflow that does not disturb the main version.
- If the work on the branch proves successful, you merge it with the main version. If the same line was edited differently on two branches, Git signals a conflict, requiring human decision.
- You can synchronize the repository on your own machine with a shared server, such as GitHub: you upload your own changes and download those of others.
An everyday example
You ask a coding agent to modify the payment page of your webshop, and afterwards the cart button stops working. Since the project is in Git, you check which lines the agent changed and restore the last recorded, still functional state with a single command.
Who is affected
A common misconception
Limits and risks
- It only preserves what you saved: work without a commit can be lost just like any other unsaved file.
- It is not a backup on its own: if the repository exists only on your machine and the machine fails, the history is lost too.
- Once you have recorded and uploaded something, such as a password or secret key, it is very difficult to erase it completely from the history. In such cases, the leaked password or key must be replaced.
- Designed for text files. Handling large images, videos, or Word and Excel files is cumbersome; these require add-ons (such as Git LFS), and the system cannot clearly display their changes.
Similar, but not the same
- GitHub – GitHub is an online service that hosts Git repositories and provides collaboration tools around them, while Git is the version control program itself.
- Cloud storage (Google Drive, Dropbox) – Cloud storage automatically synchronizes files, but in Git you decide when and with what explanation to record a state, and you can work on parallel branches.
- Backup – Backups protect against data loss, Git is for tracking changes and collaboration, and backup is only a side effect.
Related concepts
Version control, Software development, Open source
GitHub, GitLab, coding agent, Terminal, CI/CD
A brief history
Git was written by Linus Torvalds, the creator of Linux, in 2005. Until then, Linux kernel developers could use the paid version control system BitKeeper for free, but this option ended, so a new tool was needed. Project maintenance was taken over by Junio Hamano later that same year, and he has led it ever since.
Where things stand
At the end of 2026, Git is by far the most widely used version control system, used by the vast majority of developers. Some large companies and parts of the gaming industry work with other systems. With the spread of coding agents, Git's role has grown further, because changes written by machines can also be reviewed, approved and reverted through it.
In the news
- Claude Code's 'Don't Ask Again' file exposes passwords and keys in 1,122 public copiesNov 7, 2026 · Code
- Attackers use agentic tooling to find exposed secrets in public GitHub reposNov 6, 2026 · Code
- GitHub Copilot impact dashboard adds chat and VS Code agent usage, code review gets API controlsNov 6, 2026 · Code
- GitLab 19.5 makes agentic development a governed part of its DevOps platformNov 6, 2026 · Code
- Bug report alleges Claude Code writes user's email address into User-Agent headerNov 5, 2026 · Code
- OpenAI to acquire Pierre Computer to strengthen CodexNov 4, 2026 · Code
- OpenAI builds new Git backend Pando after Codex agents drive commit surgeNov 4, 2026 · Code
- Xcode 27.3 adds GitHub Copilot to its built-in assistantNov 3, 2026 · Code
Also known as
Git · git · Git version control · Git repository · Git repo · Git repository
Sources
This entry was machine-edited and has undergone machine expert review; the “In the news” section updates automatically from Agent Age stories.