Jigsaw
Git Warden is one piece of a growing family of projects, big and small. Here is how the pieces fit together, as seen from this one.
Git Warden you are here
Guard posts between AI agents and their Git remote: a Push Guard that checks every push with deterministic rules, and a Backup Guard that keeps an append-only backup of every branch and tag.
Hermetarium possible wall
The world an agent wakes up in: an OCI image it may use freely as root, behind a wall with Squid as the only, logged way out.
A house whose wall could hold the Push Guard. Git Warden’s spec names Hermetarium as one example of the wall around an agent, never a requirement: the Push Guard, its configuration and its write credential belong where the agent cannot reach them, and the agent pushes only to the guard. In Hermetarium the guard would sit outside the habitat, much as Squid keeps vendor keys out of it today. Nothing joins the two yet; the pairing is neither built nor tested.
Fregoli kin
A web application an agent can rewrite while it is running: capabilities are Cordis plugins mounted and unmounted in a live Node process.
A fellow piece of the same puzzle; no direct connection yet.
grok-budget-mcp kin
A small local MCP server that tells a Grok Build agent how much of its weekly usage pool is left, the same figure as /usage. Read-only, unofficial endpoint.
A fellow piece of the same puzzle; no direct connection yet.
claude-budget-mcp kin
A small local MCP server that tells a Claude Code agent how much of its 5-hour and weekly usage limits is left, the same figures as /usage. Read-only, unofficial endpoint.
A fellow piece of the same puzzle; no direct connection yet.