---
title: "Content-addressed storage"
description: "Content-addressed storage keeps each piece of data under a key derived from its content, usually a cryptographic hash, so identical content is stored once and a stored object never changes."
canonical: "https://agentdrive.sh/glossary/content-addressed-storage"
---
# Content-addressed storage

> For the complete documentation index, see [llms.txt](https://agentdrive.sh/llms.txt). Every docs page is also served as markdown at its URL plus `.md`, and the full docs are in one file at [llms-full.txt](https://agentdrive.sh/llms-full.txt).

> Content-addressed storage keeps each piece of data under a key derived from its content, usually a cryptographic hash, so identical content is stored once and a stored object never changes.

Source: https://agentdrive.sh/glossary/content-addressed-storage. Part of the AgentDrive glossary: https://agentdrive.sh/glossary.

Because the key is computed from the bytes, storing the same content twice adds no new object, two copies share one object, and a hash names exactly one version. Git stores its objects this way. A separate record maps human-friendly names, such as file paths, to hashes, so renaming a file does not copy its bytes and old versions keep their original hash.

## In AgentDrive

AgentDrive stores file content in its object store under the sha256 of the content. A metadata record holds the path, version number, actor and message that point at each blob, so a retried write stores no new bytes, identical artifacts share one stored object and each version keeps its original content hash.

## Related terms

- [Provenance (agent provenance)](https://agentdrive.sh/glossary/provenance/index.md): Agent provenance is the record of which agent, on which platform and under which identity, created or changed an artifact, and when, so work stays attributable across agents and sessions.
- [Session sync](https://agentdrive.sh/glossary/session-sync/index.md): Session sync copies a coding-agent session from the machine it runs on into a shared workspace as it happens, so another agent or another machine can read and resume it.

## Go deeper

- [Content-addressing](https://agentdrive.sh/docs/concepts/content-addressing)
- [Workspaces](https://agentdrive.sh/docs/concepts/workspaces)

## Official source

- [Pro Git: Git Objects](https://git-scm.com/book/en/v2/Git-Internals-Git-Objects)

