Home / Articles / One vault, ten agents, 35,000 objects / Versions / v1.3.0
One vault, ten agents, 35,000 objects: what changed in v1.3.0
From v1.2.0 (2026-10-19, d303ce0f1) to v1.3.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 3 changed in place, 37 unchanged. About 0 words added and 122 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
2 unchanged paragraphs
!shot ov-size.webp | images/ | The newsroom's vault against two of our own git repositories: 5,281 files, 1,295 commits and 35,423 objects, against the SG/Send application's 5,584 files, 4,399 commits and 42,434 objects,application and the sgit CLI's 1,811 files, 1,603 commits and 13,985 objects.CLI. | comparison
13 unchanged paragraphs, under In short {#in-short}, The vault {#vault}, What an agent fetches {#fetch}
!shot ov-fetch.webp | images/ | What an agent fetches from the 35,000-object vault and what it costs, in seconds, on a log scale: the full clone 210 seconds; the whole tree with one commit 57; one 130-file folder with one commit 13 seconds and 137 objects; structure only 27; one folder with all its history 227; the biggest folder with all its history 264; widening a clone by a folder 7.8; one file on demand 2.9; a pull with nothing new 2.5.scale. | comparison
7 unchanged paragraphs, under What an agent does every session {#session}, Where the time goes {#storage}
!shot ov-storage.webp | images/ | The same vault and client with the objects in three places: hosted, a plain file server on local disk, and a local API server. Full clone 210, 111 and 69 seconds; one commit 57, 25 and 12; one folder with one commit 13, 2.3 and 0.8; one folder with all history 181 hosted against 7.1 locally; one file on demand 2.5, 1.8 and 1.8. | comparison
15 unchanged paragraphs, under Many clients at once {#many}, From agents' memory to source code {#code}, What this does not claim {#limits}…