pssah4

Open source project (MIT-licensed) to adress the multiplayer problem - here each developer runs Claude Code or Codex in their own clone. Pulse registers work on a shared GitHub board, schedules builds from dependencies and planned files, and takes approved work through tests, review, and security audit to a pull request.

Have you actually watched the video? I put some time and afford in this to explain how and Agent works, givung a hands-ob example what loop, harness, skills and MCP actually mean in this context and how they work toghether - using my own learning project to showcase. The video delivers what the title says.

fair point, thanks for that advise!

Thanks for the pointer - but nope, you're not right. I actually proof read what I publish, but I missed this one.

As I said, I built this for myself as a learning project, in German. Then I decided to share it, which meant: deliver it in English for a broader audience.

Yes, I use AI to generate documentation and translation. But don't judge me by that. Actually I am building and sharing, judge me by the quality of the tool.

I created the video to explain how an agent works, with the example of my own learning project. I built this to understand how it works under the hood and now I share it.

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.