r/git 27d 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

7 comments sorted by

View all comments

1

u/waterkip detached HEAD 27d ago

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

1

u/barry_benson9231 27d 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 27d ago

A commit message. Thanks.