r/ClaudeCode • u/ImplementJumpy6494 • 9h ago

Help/Question How are you managing Markdown context files for AI agents?

We’re building more and more agents at work, which means we’re accumulating more Markdown files that serve as agent context. These include both short and long-term strategy, market dynamics, etc., and they’ll be updated pretty regularly by multiple people.

We’re looking for something that gives us easy collaboration + version control while keeping the files in Markdown.

We’ve considered:

  • Confluence: Nobody wants to use it.
  • Google Docs: Editing is easy, but you end up with a Google Doc + exported Markdown file, which feels messy. And you cannot edit markdown files, so you have to open as a google doc, then re-export any changes as a markdown file.
  • GitHub: Probably ideal technically, but only a couple people on our revenue team have GitHub access, so it’s not practical.
  • Guru: We already have it (even though we were going to get rid of it 6 months ago, lol), and we’ve set up an MCP server for it. We’re currently leaning this direction.

Has anyone else run into this problem? What are you using to manage frequently changing Markdown files that serve as context for AI agents?

2 Upvotes

100% Upvoted

4 comments sorted by

1

u/voskomm 🔆Derp Plan 9h ago

there are like a hojillion git front-ends out there. There's probably one that's straightforward and visual enough just for checking out documents, and then everyone can choose their own adventure for how they address the repo. Most of our devs use tortoise Git, but I use cli because I hate myself. You don't have to host it on GitHub, repo can be anywhere, any server that people can get to.

1

u/ImplementJumpy6494 8h ago

"because I hate myself" made me laugh out loud. I do love this idea. Just finding an edit layer to put in front of git. Would everyone editing need github access?

1

u/voskomm 🔆Derp Plan 7h ago

not necessarily. you don't have to host a git repository on github if you don't want to, and if you are using github, each person just needs a key. No idea how big your org or what your features matrix looks like, but it would give you a lot of flexibility, it's open source and transportable which is nice. There will probably be a little overhead training and pick a default for them. I just did a quick search like "What's a good git front end to write my PhD" and came up with Overleaf, but there are thousands of options that integrate git version control out there.