LangChain CEO Explores Storing AI Agent Docs Outside Version Control

Something we’re thinking a bunch about as well

Would love thoughts!

@dexhorthy I don't know. it's handy to have it right there avail for everyone without additional hassle to maintain another service

thought about this a lot. agree with the points but from the 5 bullets, being in the repo gives you 4 out of 5 instead of "outside your repo"

I do think we need a better story here. maybe clear separate folders. having them per branch also helps contain docs to the specific branch if you are doing work there, etc.

@dexhorthy With a good way to access it, I fully agree. Osidian vault or similar. What would be your tool of choice?

Just store them in controller layer version control with all trees/btanches sweeping routines.

Orch layer may have or may have not different lifecycle vs the object under management (project under management).

Everything is linear early. Then you’ll discover that controller might need upper layer controller. (We are alnost there in llm org awareness)

E.g. for research convergence and wild code zoo decimation and overall governance.

File based VCS gives 80% of the value for configuration management for no cost and other 20% is pain in the ass to build (I have to do it and I hate it).

@dexhorthy i think if you have a monorepo, keeping them in the core repo can be helpful. otherwise, a separate location makes sense as long as it ticks the criteria you've listed.

@dexhorthy Agree plus I tend to think that agents get confused when they read them and they happen to be outdated.

@dexhorthy @hwchase17 agreed on all. overall like google docs, but agents first. optimized for human reading too.