commit

basicwidespread

A commit is a saved snapshot of the program's code: it records what changed, who changed it, when, and why, so you can return to it at any time.

In plain terms

Imagine writing a long essay, and after every major step, you not only save it but also pin a note to it: "rewrote the introduction because it was too long." A commit is the same in programming: saving and explanation combined.

A plain save overwrites the previous state, while a commit preserves it. Commits line up one after another and together form the project's complete history, allowing you to scroll back to any earlier state.

This is useful because if something breaks, it is clear exactly which change caused it and can be reverted. In a team, it also reveals who did what and why.

In the AI era, a new role has emerged: when a coding agent works on your program, commits show exactly what it touched, enabling step-by-step review or rollback of its work.

How it works

The developer (or coding agent) modifies some files: writes a new feature, fixes a bug, or replaces text.
It selects which changes belong together and prepares them to be committed.
He or she writes a short message with it about what was changed and why; this is the commit message.
Version control (most commonly Git) saves a snapshot with the author's name, timestamp, and a unique identifier, appending it to the previous commit.
A commit exists only on the developer's own machine at first; others see it when the developer uploads it to the shared repository (this is the push).

An everyday example

You ask a coding agent to fix the VAT calculation on your webshop's cart page. The agent creates a commit at the end with the message "Fixing VAT calculation in the cart," where you can see line by line what it changed. If the fix is still wrong, this single commit can be reverted, while other changes usually remain untouched.

Who is affected

developerA daily working tool: it records your own changes and tracks those of your teammates and of coding agents. → Code

entrepreneur, executiveCommit history shows who changed what in a company's software and when, which is valuable for debugging and accountability.

parent, student, teacherAnyone learning to program will soon encounter it, and the commit history clearly shows how a submission was completed. → Education & Family

jobseeker, new graduateYour commits in public projects show how you work, serving as part of your developer resume. → Work & HR

A common misconception

MythA commit is the same as the save button, and once done, the change is live.

In realityA commit is a snapshot with a comment that enters the history, not a simple file save. By default, it exists only on your own machine and reaches the shared repository and the live system through separate steps.

Limits and risks

A commit is not a backup itself: until you upload it to the shared repository, it can be lost if your machine fails.
Once you have committed and uploaded something, it is very difficult to erase it without a trace, so never include passwords, API keys, or personal data in it.
A commit does not guarantee that the code is good: faulty or non-functional changes are recorded just the same.
If a coding agent creates the commit, review it before forwarding it, because both the code and the message may be flawed or inaccurate even if the message sounds confident.

Similar, but not the same

push – The commit records the change locally, while the push uploads it to the shared repository where others can see it.
pull request – A pull request is a request to review and merge one or more commits, while a commit itself is the recorded change.
save – Saving overwrites the file's previous state, whereas a commit preserves earlier versions and adds an explanation to the change.

Related concepts

Broader

version control, Git, software development

Narrower

commit message, commit identifier (hash), revert

On the edge

repository, branch, push, pull request, coding agent

A brief history

The word "commit" originates from database transaction management, where it denotes the final recording of a change. Older version control systems, such as CVS and Subversion, already used it. In these, the commit went directly to the central server. The most widespread form today was popularized by Git: here, the commit is first created on the local machine. Linus Torvalds created Git in 2005 for Linux development.

Where things stand

At the end of 2026, the commit is a self-evident basic unit of software development. What is new is that more and more commits are made by coding agents, so reviewing commits and marking authorship have become more important.

Status: 2026 November

In the news

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

A&O Shearman commits $1.1bn lawyer-led investment to its AI programmeNov 5, 2026 · Jog
OpenAI builds new Git backend Pando after Codex agents drive commit surgeNov 4, 2026 · Code
Anthropic heads to IPO with nearly $17 billion quarterly revenue, but $1.5 trillion valuation is contestedNov 2, 2026 · Agent Age
Only 20% of government schools in Jalandhar equipped for AINov 2, 2026 · Education & Family
Survey: 65% of US consumers would blame the AI company if an AI agent commits fraudNov 2, 2026 · Money
Wall Street loses $1 trillion in a week as Apple overtakes NvidiaOct 30, 2026 · Agent Age
Foxconn prepares new tie-up with OpenAI, sees no sign of an AI bubbleOct 30, 2026 · Ipar
House Democrats criticize Justice Department support for OpenAI in copyright suitOct 30, 2026 · Jog

Also known as

commit · kommit · commitol · kommitol · git commit · change tracking · check-in

Sources

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