Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

STOP STORING NOTES. START COMPILING THEM. a pile of notes isn't memory. it's accumulation wearing memory's clothes. these 7 repos build the other kind, where Claude reads a source once and links it to everything you already have. copy the list: graphify: turns a codebase with its docs, SQL...

55,114 görüntüleme • 11 gün önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

HERMES AGENT HAS A SECOND BRAIN. 1,100+ KNOWLEDGE FILES. AUTO-LINKED. SELF-IMPROVING. GROWING EVERY NIGHT. THIS IS THE OBSIDIAN GRAPH BEHIND IT. every dot = one knowledge file (markdown) every line = one wiki-link between files every color = one category (skills, notes, decisions, sources, entities) HOW IT BUILDS ITSELF: Hermes ships with a bundled LLM Wiki skill. based on Andrej Karpathy's pattern. unlike RAG (rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. when you feed the agent a source: → it reads the content → writes a structured markdown page → auto-links to every related existing page → flags contradictions with previous entries → updates all affected pages one source in. multiple connections created. the graph grows denser with every entry. WHAT FEEDS THE WIKI: → articles and URLs you find interesting → meeting transcripts → PDF documents and research papers → conversation history from Hermes sessions → Claude Code and Codex session history → Slack logs, email threads, saved notes → YouTube transcripts → raw text dropped into a _raw/ folder the obsidian-wiki package supports multi-agent ingest from Hermes, Claude Code, Codex, OpenClaw, Pi, Windsurf, and ChatGPT exports. install: pip install obsidian-wiki obsidian-wiki setup --vault ~/wiki AUTOMATE THE GROWTH: set cron jobs to feed the wiki overnight: "every day at 9am, check for new meetings. ingest transcripts into the wiki." "every week, check arXiv for new papers in [niche]. summarize and file into the wiki." "every day, ingest today's Hermes sessions into the wiki under session-history." month 1: 50 entries. scattered. month 3: 300+ entries. cross-referenced. month 6: 1,000+ entries. the agent surfaces patterns you never searched for. WHY OBSIDIAN: the wiki is plain markdown files. no database. no lock-in. open it in Obsidian for graph view: → nodes show knowledge density → links show how ideas connect → clusters reveal your strongest domains → orphan nodes reveal gaps Hermes writes from a VPS. Obsidian reads on your laptop. obsidian-headless syncs without a GUI. agent writes from the server, you browse on your device. FOUR MEMORY LAYERS: Layer 1: memory.md + user.md (~2,200 + 1,375 chars. short-term.) Layer 2: SQLite with FTS5 (full session transcripts. searchable.) Layer 3: external providers (Mem0, SuperMemory, Honcho. optional.) Layer 4: Obsidian wiki via LLM Wiki skill (unlimited. compounding. the long-term brain.) layers 1-3 handle memory. layer 4 handles knowledge. the graph in this post is layer 4. SETUP: set in Desktop app, Dashboard, or config.yaml: WIKI_PATH=~/wiki OBSIDIAN_VAULT_PATH=~/wiki first run: Hermes asks for your domain. answer with your niche. the skill builds SCHEMA.md with tag taxonomy. after that: "index this into my wiki: [URL or text]" the wiki grows. the graph densifies. the agent gets smarter because the knowledge base got smarter. full 15 levels breakdown in the article 👇

YanXbt

35,900 görüntüleme • 4 ay önce

It is becoming f*cking dangerous: I don't understand why everyone still isn't doing this, thanks to this I reached an income of $12,000 as early as 3 months ago Andrej Karpathy, co-founder of OpenAI, shared a straightforward concept that blew up with over 23 million views: stop relying on AI strictly for coding and start using it to construct your own personal knowledge engine Point Claude Code to a folder, toss in raw materials (whether it's an article, a video transcript, or a PDF) and Claude processes everything, links relevant topics together, and organizes it into a self-updating wiki of your personal knowledge. It acts like compound interest: the more information you add, the more capable it becomes Here is the exact breakdown: Set up Obsidian, create a fresh vault, and open it using Claude Code Supply Karpathy's wiki layout prompt and instruct Claude to build the architecture Claude automatically sets up three components: a ⁠raw⁠ directory for source files, a ⁠wiki⁠ directory for processed pages, and a ⁠CLAUDE.md⁠ control file to run the system Dump any document into the ⁠raw⁠ folder and run "ingest this" Query your entire knowledge repository at any time, indefinitely It takes just five minutes to configure, eliminating the need to ever start a conversation with a completely blank context window again Check the link below for the complete step-by-step walkthrough on setting up Claude with Obsidian Bookmark this post for later

Bober_smart

82,139 görüntüleme • 12 gün önce

It blows my mind how few people have implemented this setup. A year ago, this exact system allowed me to automate 90% of my tasks and expand my business Andrey Karpathy, co-founder of OpenAI, dropped a simple idea that generated 22 million views and 108,000 saves "stop relying on AI strictly for generating code, and start leveraging it to build a personal second brain" The logic is straightforward: You link Claude Code to a specific directory and throw in any reference materials (articles, meeting transcripts, or PDFs) The system analyzes the text, maps out connections, and constructs a living repository of everything you know. It compounds continuously: as you feed it more data, the entire ecosystem becomes significantly smarter How it breaks down in practice: Launch Obsidian, set up a new repository, and connect it to Claude Code Feed in the template based on Karpathy's wiki approach and instruct Claude to deploy the architecture The model automatically constructs three core areas: raw for your incoming documents, wiki for organized pages, and a master CLAUDE file that coordinates all processes Move any new resource into the raw folder and issue a quick command to process it Query your entire personal knowledge base whenever you need answers A quick five-minute deployment means you will never have to initiate a prompt from a blank canvas again I published the complete guide in the article. Make sure to bookmark it for later

Bober_smart

111,498 görüntüleme • 28 gün önce