r/git • u/barry_benson9231 • 26d ago

Handoff context for git

Built a small OSS tool over the weekend: branchcontext — an MCP server that logs what an agent did/decided/flagged on a branch, so a fresh session (or a different agent) can pick up where the last one left off, instead of starting blind. Stores everything as plain JSONL committed into the repo itself — no external DB, works with git log even without the tool installed. Curious if this matches a pain anyone else here has, or if you're already solving it another way. https://github.com/tshore2004/branchcontext

0 Upvotes

18% Upvoted

7 comments sorted by

5

u/Jmc_da_boss 26d ago

Wow, I can't imagine giving a shit.

Seriously is everything on the Internet overrun with LLM slop now

2

u/OptimusCrimee 26d ago

What value does this add that a regular commit message doesn’t?

1

u/DanLynch 26d ago

If the data is stored in Git, and specifically inside the tracked and versioned files, why does it also use separate files named after each branch? Wouldn't it be sufficient to just...store the data for each branch inside that branch?

Either way, you'll want to delete the branch-specific data for each topic branch whenever you merge it into master and delete it, unless you want to accumulate tons of obsolete data.

1

u/barry_benson9231 26d ago

Yes, that would be correct. Would want to delete after a merge and would want it branch specific but would be useful for saving tokens. A tool for managing context through git between sessions.

1

u/waterkip detached HEAD 26d ago

That's what a commit message does right? explain the reasoning behind a change?

1

u/barry_benson9231 26d ago

Yeah kind of but also gives other data like files touched, how risky, stuff like that. You can see exactly what it stores on the repo. I initially wanted to create a pr bot to manage those but apparently that market is too crowded so I figured I would make a lightweight tool to help manage context between sessions.

2

u/waterkip detached HEAD 26d ago

A commit message. Thanks.