You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GCC v2: lean git-backed memory with utility scripts
Replace verbose markdown storage (~500 tokens/entry) with lean
index.yaml format (~50 tokens/entry) backed by real git commits.
Context is reconstructed on demand via git show.
New scripts:
- gcc_commit.sh: real git commit + lean index entry
- gcc_context.sh: reconstruct context from hashes
- gcc_bridge.sh: feed commit data to aiyoucli vector memory
- gcc_cleanup.sh: TTL-based worktree cleanup + index pruning
Updated gcc_init.sh with dual mode (git/standalone) detection.
Updated SKILL.md, README.md, file_formats.md, sample_session.md
for v2 format and workflows.
**Structured context management framework for LLM agents.**
7
+
**Lean, git-backed context management for LLM agents.**
8
8
9
-
GCC implements Git-like operations (COMMIT, BRANCH, MERGE, CONTEXT) to manage long-horizon agent memory as a persistent, versioned file system.
9
+
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.
10
10
11
11
> Based on the research paper: [Git Context Controller](https://arxiv.org/abs/2508.00031)
12
12
13
13
---
14
14
15
15
## Why GCC?
16
16
17
-
LLM agents lose context as conversations grow. Critical decisions, technical reasoning, and intermediate results vanish behind token limits. GCC solves this by giving agents a structured memory system:
17
+
LLM agents lose context as conversations grow. GCC solves this by giving agents structured memory:
18
18
19
-
-**No more lost context** -- milestones are persisted with full technical reasoning
20
-
-**Safe experimentation** -- branches isolate alternative approaches without polluting the main flow
21
-
-**Cross-session continuity** -- agents recover exactly where they left off
22
-
-**Multi-agent handoff** -- one agent's work is readable by another
19
+
-**Lean storage** -- ~50 tokens per entry vs ~500 in v1
20
+
-**Git-backed truth** -- real commits, not narrative copies
21
+
-**Safe experimentation** -- branches via git worktrees for real isolation
22
+
-**Cross-session recovery** -- reconstruct context from hashes on demand
23
+
-**aiyoucli bridge** -- auto-feeds commit data to vector memory when available
23
24
24
25
## How It Works
25
26
27
+
### Git Mode (with repo)
28
+
29
+
```
30
+
.GCC/
31
+
├── index.yaml # Single source of truth (~50 tokens/entry)
32
+
├── branches/ # Branch-specific notes
33
+
├── worktrees/ # Worktree tracking
34
+
└── .bridge-log # Sync state with aiyoucli
35
+
36
+
index.yaml entry:
37
+
- id: C001
38
+
hash: 85c8539 ← pointer to git truth
39
+
intent: "release prep" ← why
40
+
note: "descartamos semantic-release por overhead" ← optional decision
41
+
branch: main
42
+
date: "2026-02-25T21:40:00Z"
43
+
```
44
+
45
+
### Standalone Mode (no repo)
46
+
47
+
Falls back to markdown files compatible with v1:
48
+
49
+
```
50
+
.GCC/
51
+
├── index.yaml # Timeline
52
+
├── main.md # Roadmap (v1 compat)
53
+
├── log.md # OTA traces (v1 compat)
54
+
└── branches/
55
+
```
56
+
57
+
### Context Reconstruction
58
+
26
59
```
27
-
┌─────────────────────────────────┐
28
-
│ .GCC/ │
29
-
│ │
30
-
│ main.md (roadmap) │
31
-
│ metadata.yaml (state) │
32
-
│ commit.md (history) │
33
-
│ log.md (OTA traces) │
34
-
│ │
35
-
│ branches/ │
36
-
│ ├── feature-x/ │
37
-
│ │ ├── summary.md │
38
-
│ │ ├── commit.md │
39
-
│ │ └── log.md │
40
-
│ └── experiment-y/ │
41
-
│ ├── summary.md │
42
-
│ ├── commit.md │
43
-
│ └── log.md │
44
-
└─────────────────────────────────┘
45
-
```
46
-
47
-
### The OTA Cycle
48
-
49
-
Agents operate through **Observation-Thought-Action** cycles, logged in real time:
50
-
51
-
```
52
-
┌───────────┐ ┌───────────┐ ┌───────────┐
53
-
│ OBSERVE │────>│ THINK │────>│ ACT │
54
-
│ │ │ │ │ │
55
-
│ Read logs │ │ Analyze │ │ Execute │
56
-
│ Check │ │ Decide │ │ COMMIT │
57
-
│ state │ │ strategy │ │ BRANCH │
58
-
└───────────┘ └───────────┘ │ MERGE │
59
-
^ └─────┬─────┘
60
-
│ │
61
-
└───────────────────────────────────┘
62
-
Logged to log.md
63
-
```
64
-
65
-
### Command Flow
66
-
67
-
```
68
-
User works on task
69
-
│
70
-
▼
71
-
┌──────────────┐ milestone? ┌──────────┐
72
-
│ OTA Cycle │────────────────> │ COMMIT │──> commit.md
0 commit comments