Git Context Controller

Git Context Controller (GCC) v2

[](https://github.com/faugustdev/git-context-controller/releases) [](LICENSE) [](https://skills.sh) [](https://codeguilds.dev/packages/git-context-controller) [](https://doi.org/10.5281/zenodo.19475089)

**Lean, git-backed context management for LLM agents.**

GCC v2 stores **hash + intent + optional decision notes** instead of verbose markdown. Full context is reconstructed on demand via `git show`. Dual mode: git-backed or standalone.

Based on the research paper: [Git Context Controller](https://arxiv.org/abs/2508.00031)

---

Why GCC?

LLM agents lose context as conversations grow. GCC solves this by giving agents structured memory:

• Lean storage -- ~50 tokens per entry vs ~500 in v1
• Git-backed truth -- real commits, not narrative copies
• Safe experimentation -- branches via git worktrees for real isolation
• Cross-session recovery -- reconstruct context from hashes on demand
• aiyoucli bridge -- auto-feeds commit data to vector memory when available

How It Works

Git Mode (with repo)

.GCC/
├── index.yaml       # Single source of truth (~50 tokens/entry)
├── branches/        # Branch-specific notes
├── worktrees/       # Worktree tracking
└── .bridge-log      # Sync state with aiyoucli

index.yaml entry:
  - id: C001
    hash: 85c8539        ← pointer to git truth
    intent: "release prep" ← why
    note: "descartamos semantic-release por overhead" ← optional decision
    branch: main
    date: "2026-02-25T21:40:00Z"

Standalone Mode (no repo)

Falls back to markdown files compatible with v1:

.GCC/
├─