I built a plugin that combines Karpathy's LLM-Wiki and Google's Open Knowledge Format (OKF) to maintain my Obsidian vault. An embedded agent helps me to monitor freshness, relevance and links, to keep knowledge and memory current.
That works perfectly fine in single player mode. For knowledge workers, multi player mode becomes more difficult: how can I manage git conflicts in a way, a non-technical user can deal with it. How do I escalate conflicts with differt perspectives? Who decides (initial/all/any contributor)? How to manage retrieval for users without a GitHub account?
My idea is to built a skill (and use it with the agent) that carries most of that work for the user.
Does anyone tried something similar yet? I'd behappy to get your ideas!
Anyone who manages a large number of own notes in a knowledge management system is familiar with the five minutes of maintenance required after every new note - time that no one ever has. Vault Operator, my Obsidian plugin, now includes an inline layer in the editor that integrates this maintenance right into the reading flow. An approach based on Karpathy’s idea of an LLM-maintainable vault and Google’s Open Knowledge Format.
That works perfectly fine in single player mode. For knowledge workers, multi player mode becomes more difficult: how can I manage git conflicts in a way, a non-technical user can deal with it. How do I escalate conflicts with differt perspectives? Who decides (initial/all/any contributor)? How to manage retrieval for users without a GitHub account?
My idea is to built a skill (and use it with the agent) that carries most of that work for the user.
Does anyone tried something similar yet? I'd behappy to get your ideas!