Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Prompt engineering is where people go when they refuse to write files Karpathy's LLM Wiki gist is painfully simple: > raw sources stay untouched > the agent writes the wiki > `CLAUDE.md` or `AGENTS.md` tells it the rules > `index.md` maps the pages > `log.md` records what changed That...

alphabatcher's profile picture

Alpha Batcher

51,860 subscribers

14,041 görüntüleme • 4 ay önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

CLAUDE + OBSIDIAN + KARPATHY'S LLM WIKI = A WIKI THAT MAINTAINS ITSELF run this once and your research compounds instead of evaporating sources go in, a wiki comes out, and a loop keeps it honest • three layers, one owner each > the schema - CLAUDE.md, you and the agent co-evolve it > the wiki - markdown the agent owns. it writes, you read > raw sources - immutable, read only, never edited • three operations on repeat > ingest - read the source, write the summary, log one line > query - answer with citations, file it back as a new page > lint - contradictions, orphans and dead links caught early RAG re-derives the same answer from raw chunks on every query. you pay for that thinking again, every time you ask this wiki gets written once and stays current. 10-15 pages per source, nearly 100 sources on the index alone month one it saves you an hour a day. month six it knows your field better than the person you're up against for the senior seat "Obsidian is the IDE, the LLM is the programmer, the wiki is the codebase" - Andrej Karpathy the stack: 📁 Obsidian ↳ 📁 Claude ↳ 📁 Karpathy LLM-Wiki ↳
0:30

CLAUDE + OBSIDIAN + KARPATHY'S LLM WIKI = A WIKI THAT MAINTAINS ITSELF run this once and your research compounds instead of evaporating sources go in, a wiki comes out, and a loop keeps it honest • three layers, one owner each > the schema - CLAUDE.md, you and the agent co-evolve it > the wiki - markdown the agent owns. it writes, you read > raw sources - immutable, read only, never edited • three operations on repeat > ingest - read the source, write the summary, log one line > query - answer with citations, file it back as a new page > lint - contradictions, orphans and dead links caught early RAG re-derives the same answer from raw chunks on every query. you pay for that thinking again, every time you ask this wiki gets written once and stays current. 10-15 pages per source, nearly 100 sources on the index alone month one it saves you an hour a day. month six it knows your field better than the person you're up against for the senior seat "Obsidian is the IDE, the LLM is the programmer, the wiki is the codebase" - Andrej Karpathy the stack: 📁 Obsidian ↳ 📁 Claude ↳ 📁 Karpathy LLM-Wiki ↳

Annatar.md

16,939 görüntüleme • 12 gün önce

THE ANATOMY OF A SECOND BRAIN THAT WRITES ITSELF one Obsidian vault, three layers, and a loop that files every good answer back into a wiki you never touch the structure: > CLAUDE.md + AGENTS.md - the constitution. same rules whether Claude or Codex runs the loop > raw/ - inbox, articles, assets. frozen and read-only, you feed it and walk away > wiki/ - index.md, entities/, concepts/, synthesis.md. the agent grows this on its own > log.md - append-only, every move timestamped 47 sources in -> 210 pages out the agent typed 96% of it. you typed zero the cost trick: point Opus 5 only at synthesis.md, the one file that needs frontier reasoning. everything else runs fine on cheaper models under the hood it's loop engineering: you ask -> a good answer gets filed back -> the wiki grows start linking entities to each other and you're one step from a full graph your research compounds while you sleep. the full blueprint is below 👇
0:24

THE ANATOMY OF A SECOND BRAIN THAT WRITES ITSELF one Obsidian vault, three layers, and a loop that files every good answer back into a wiki you never touch the structure: > CLAUDE.md + AGENTS.md - the constitution. same rules whether Claude or Codex runs the loop > raw/ - inbox, articles, assets. frozen and read-only, you feed it and walk away > wiki/ - index.md, entities/, concepts/, synthesis.md. the agent grows this on its own > log.md - append-only, every move timestamped 47 sources in -> 210 pages out the agent typed 96% of it. you typed zero the cost trick: point Opus 5 only at synthesis.md, the one file that needs frontier reasoning. everything else runs fine on cheaper models under the hood it's loop engineering: you ask -> a good answer gets filed back -> the wiki grows start linking entities to each other and you're one step from a full graph your research compounds while you sleep. the full blueprint is below 👇

Annatar.md

23,649 görüntüleme • 21 gün önce

HERMES AGENT SHIPS WITH A BUNDLED SKILL FOR ANDREJ KARPATHY'S LLM WIKI PATTERN. A SELF-IMPROVING KNOWLEDGE BASE THAT GROWS EVERY TIME YOU FEED IT. mentioned this briefly in the overnight workflow article. here is the full breakdown. what it is: a self-improving knowledge base built as interlinked markdown files. unlike RAG (which rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. cross-references stay linked. contradictions get flagged automatically. synthesis reflects everything ingested so far. why this matters for Hermes memory: Hermes built-in memory knows YOU. it remembers your conversations, your preferences, your business context across sessions. but it doesn't know your inbox. or your meeting transcripts. or that article you saved last week. or the expert framework you want it to learn. the LLM Wiki solves that. THE DIVISION OF LABOR human curates sources and directs analysis. agent summarizes, cross-references, files, and maintains consistency. you drop in articles, transcripts, notes. Hermes indexes them, links related concepts, flags contradictions, updates affected pages. your knowledge base grows itself. SETUP IS ONE COMMAND the skill ships with Hermes. enable it. set WIKI_PATH in ~/.hermes/.env: WIKI_PATH=/Users/you/wiki defaults to ~/wiki if unset. then drop anything into it: "index this article into my wiki: [paste URL or text]" Hermes reads it, builds a source page, updates related entries, flags contradictions. THE OBSIDIAN ANGLE set OBSIDIAN_VAULT_PATH to the same directory. now your wiki is visible in Obsidian's graph view. nodes, links, backlinks. all built by Hermes. for headless servers: install obsidian-headless. syncs vaults without a GUI. agent writes from the server, you read on your laptop. THE COMPOUND EFFECT Hermes knows you. the wiki knows your world. combine them and the agent answers questions using BOTH contexts at once. month 1: you explain things twice. month 3: the agent references the wiki on its own. answers get sharper because the knowledge base got sharper. AUTOMATIONS THAT FEED THE WIKI set cron jobs to ingest automatically: "every day at 9am, check Granola for new meetings. add any new transcripts to my wiki under meeting notes." "every morning, scan my Gmail starred items. add anything worth keeping to the wiki." "every week, check arXiv for new papers in [your niche]. summarize and file." your wiki grows while you sleep. Hermes never forgets what gets indexed. THE LIMITATION TO KNOW unlike Hermes memory (which is conversational and lives across sessions), the wiki is a separate knowledge layer. Hermes won't pull from the wiki automatically unless you reference it or save it as a skill. best setup: build an LLM Wiki personality that tells Hermes to consult the wiki when answering strategy questions or domain-specific queries. full HERMES AGENT OVERNIGHT WORKFLOW👇
14:28

HERMES AGENT SHIPS WITH A BUNDLED SKILL FOR ANDREJ KARPATHY'S LLM WIKI PATTERN. A SELF-IMPROVING KNOWLEDGE BASE THAT GROWS EVERY TIME YOU FEED IT. mentioned this briefly in the overnight workflow article. here is the full breakdown. what it is: a self-improving knowledge base built as interlinked markdown files. unlike RAG (which rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. cross-references stay linked. contradictions get flagged automatically. synthesis reflects everything ingested so far. why this matters for Hermes memory: Hermes built-in memory knows YOU. it remembers your conversations, your preferences, your business context across sessions. but it doesn't know your inbox. or your meeting transcripts. or that article you saved last week. or the expert framework you want it to learn. the LLM Wiki solves that. THE DIVISION OF LABOR human curates sources and directs analysis. agent summarizes, cross-references, files, and maintains consistency. you drop in articles, transcripts, notes. Hermes indexes them, links related concepts, flags contradictions, updates affected pages. your knowledge base grows itself. SETUP IS ONE COMMAND the skill ships with Hermes. enable it. set WIKI_PATH in ~/.hermes/.env: WIKI_PATH=/Users/you/wiki defaults to ~/wiki if unset. then drop anything into it: "index this article into my wiki: [paste URL or text]" Hermes reads it, builds a source page, updates related entries, flags contradictions. THE OBSIDIAN ANGLE set OBSIDIAN_VAULT_PATH to the same directory. now your wiki is visible in Obsidian's graph view. nodes, links, backlinks. all built by Hermes. for headless servers: install obsidian-headless. syncs vaults without a GUI. agent writes from the server, you read on your laptop. THE COMPOUND EFFECT Hermes knows you. the wiki knows your world. combine them and the agent answers questions using BOTH contexts at once. month 1: you explain things twice. month 3: the agent references the wiki on its own. answers get sharper because the knowledge base got sharper. AUTOMATIONS THAT FEED THE WIKI set cron jobs to ingest automatically: "every day at 9am, check Granola for new meetings. add any new transcripts to my wiki under meeting notes." "every morning, scan my Gmail starred items. add anything worth keeping to the wiki." "every week, check arXiv for new papers in [your niche]. summarize and file." your wiki grows while you sleep. Hermes never forgets what gets indexed. THE LIMITATION TO KNOW unlike Hermes memory (which is conversational and lives across sessions), the wiki is a separate knowledge layer. Hermes won't pull from the wiki automatically unless you reference it or save it as a skill. best setup: build an LLM Wiki personality that tells Hermes to consult the wiki when answering strategy questions or domain-specific queries. full HERMES AGENT OVERNIGHT WORKFLOW👇

YanXbt

30,804 görüntüleme • 3 ay önce

Introducing Wikiwise: an open-source Mac app for managing your own Karpathy-style LLM wiki. Set up a new wiki in a few clicks: all you need is Wikiwise + your agent. It's infinitely customizable, just markdown/html under the hood, and one click to share your wiki publicly. Here's how it works: * Install Wikiwise for mac (it's built in Swift so super minimal and performant). In Karpathy's framework, Wikiwise is your IDE. * Start a new Wiki: it generates a new folder on your machine that's scaffolded in the wiki structure Andrej Karpathy describes (index.md, raw folder, wiki folder, CLAUDE.md/AGENTS.md, although it tries to be as un-opinionated as possible). * Then just point your agent (Codex, Claude Code, Cursor, etc) at the folder and tell it what to import -- files on your machine, connect to your Readwise account, or urls from the web. * Your agent creates wthe wiki for you: Your agent will know how to ingest your raw sources (via the AGENTS.md) and will immediately start writing+linking wiki pages for you. * Go crazy on customization! The rendered wiki pages live as static html/css in your folder too so just tell your agent to change stuff, and if you need any more customization Wikiwise is fully open source :) * Ask questions about your research with your agent, ask it to bring in new sources, write new documents, etc. * (optionally) Hit the Publish button to share your wiki with friends/colleagues at a custom URL === I tried to walk the line on a couple constraints with Wikiwise: 1. I wanted it to be easy to spin up new wikis, especially without chaining together a bunch of different apps. It takes me a few minutes to spin up a new wiki on a topic -- I already have five! 2. Infinitely Customizable: one great aspect of building a wiki as Karpathy described is that you can modify any aspect of your wiki with your agent. Every new wiki styling+structure is self-contained in the local folder, which allows you to preserve this. Wikiwise is just an IDE that makes the setup easier and includes a nice un-opinionated starting state. 3. Minimal: Wikiwise is built mostly in Swift, and the DMG you install to download it is only 2.6MB (!) 4. Easy Publishing: my colleague Eleanor Konik has been building her own LLM wikis for months, but has always really struggled to actually share them with her book club. There are tools to do it, but figuring out hosting is always a huge headache. This seemed like an ideal usecase for a tool like Wikiwise to solve. The process of building wikiwise was also pretty interesting -- I "bootstrapped" the app in a way by first building my own wiki based on Karpathy's tweet and other notes I had, and slowly formed the shape of the project in collaboration with my LLM. This was all done in 3 days over the latest Readwise company hackathon we had. Truly an incredible time to be alive. Anyways, curious what you think! Links in next tweet.
3:10

Introducing Wikiwise: an open-source Mac app for managing your own Karpathy-style LLM wiki. Set up a new wiki in a few clicks: all you need is Wikiwise + your agent. It's infinitely customizable, just markdown/html under the hood, and one click to share your wiki publicly. Here's how it works: * Install Wikiwise for mac (it's built in Swift so super minimal and performant). In Karpathy's framework, Wikiwise is your IDE. * Start a new Wiki: it generates a new folder on your machine that's scaffolded in the wiki structure Andrej Karpathy describes (index.md, raw folder, wiki folder, CLAUDE.md/AGENTS.md, although it tries to be as un-opinionated as possible). * Then just point your agent (Codex, Claude Code, Cursor, etc) at the folder and tell it what to import -- files on your machine, connect to your Readwise account, or urls from the web. * Your agent creates wthe wiki for you: Your agent will know how to ingest your raw sources (via the AGENTS.md) and will immediately start writing+linking wiki pages for you. * Go crazy on customization! The rendered wiki pages live as static html/css in your folder too so just tell your agent to change stuff, and if you need any more customization Wikiwise is fully open source :) * Ask questions about your research with your agent, ask it to bring in new sources, write new documents, etc. * (optionally) Hit the Publish button to share your wiki with friends/colleagues at a custom URL === I tried to walk the line on a couple constraints with Wikiwise: 1. I wanted it to be easy to spin up new wikis, especially without chaining together a bunch of different apps. It takes me a few minutes to spin up a new wiki on a topic -- I already have five! 2. Infinitely Customizable: one great aspect of building a wiki as Karpathy described is that you can modify any aspect of your wiki with your agent. Every new wiki styling+structure is self-contained in the local folder, which allows you to preserve this. Wikiwise is just an IDE that makes the setup easier and includes a nice un-opinionated starting state. 3. Minimal: Wikiwise is built mostly in Swift, and the DMG you install to download it is only 2.6MB (!) 4. Easy Publishing: my colleague Eleanor Konik has been building her own LLM wikis for months, but has always really struggled to actually share them with her book club. There are tools to do it, but figuring out hosting is always a huge headache. This seemed like an ideal usecase for a tool like Wikiwise to solve. The process of building wikiwise was also pretty interesting -- I "bootstrapped" the app in a way by first building my own wiki based on Karpathy's tweet and other notes I had, and slowly formed the shape of the project in collaboration with my LLM. This was all done in 3 days over the latest Readwise company hackathon we had. Truly an incredible time to be alive. Anyways, curious what you think! Links in next tweet.

Tristan

96,743 görüntüleme • 5 ay önce

This beginner guide to Karpathy's LLM Wiki is one of the most useful AI videos i've shared this year Karpathy's idea: instead of asking AI questions every time, make it build you a permanent knowledge base that grows smarter over time > drop your documents into a folder > Claude reads them and builds a structured wiki in Obsidian > every time you add a new source, Claude Sonnet updates existing pages and links new ideas > ask complex questions - Claude Opus answers from the organized wiki, not raw files it's like having a researcher who never forgets and connects dots across everything you've ever given it full setup guide is in the video above
14:21

This beginner guide to Karpathy's LLM Wiki is one of the most useful AI videos i've shared this year Karpathy's idea: instead of asking AI questions every time, make it build you a permanent knowledge base that grows smarter over time > drop your documents into a folder > Claude reads them and builds a structured wiki in Obsidian > every time you add a new source, Claude Sonnet updates existing pages and links new ideas > ask complex questions - Claude Opus answers from the organized wiki, not raw files it's like having a researcher who never forgets and connects dots across everything you've ever given it full setup guide is in the video above

Mr. Buzzoni

58,787 görüntüleme • 4 ay önce

I genuinely don't understand why everyone isn't using this yet. Andrej Karpathy, OpenAI co-founder, posted a simple idea that went massively viral: Stop using AI to write code. Use it to build a second brain. You point Claude Code at a folder. Drop in any source: an article, a transcript, a PDF. Claude reads it, links it, files it into a living wiki of everything you know. It compounds like interest. The more you feed it, the smarter it gets. Here's the whole thing: 1) Install Obsidian 2) Create a vault 3) Open it in Claude Code 4) Paste Karpathy's wiki idea and tell Claude to build it 5) Claude makes three folders: - raw (for sources) - wiki (for its pages) - CLAUDE. md (that runs it) 6) Drop any source into raw and say: "ingest this" 7) Ask questions across everything, forever Five minutes to set up and you never start from a blank chat again. Full step by step guide below.
1:48

I genuinely don't understand why everyone isn't using this yet. Andrej Karpathy, OpenAI co-founder, posted a simple idea that went massively viral: Stop using AI to write code. Use it to build a second brain. You point Claude Code at a folder. Drop in any source: an article, a transcript, a PDF. Claude reads it, links it, files it into a living wiki of everything you know. It compounds like interest. The more you feed it, the smarter it gets. Here's the whole thing: 1) Install Obsidian 2) Create a vault 3) Open it in Claude Code 4) Paste Karpathy's wiki idea and tell Claude to build it 5) Claude makes three folders: - raw (for sources) - wiki (for its pages) - CLAUDE. md (that runs it) 6) Drop any source into raw and say: "ingest this" 7) Ask questions across everything, forever Five minutes to set up and you never start from a blank chat again. Full step by step guide below.

CyrilXBT

332,572 görüntüleme • 3 ay önce

i genuinely can't understand why this isn't the first thing every claude user builds... andrej karpathy, co-founder of openai, quietly solved the exact problem making your ai useless and almost nobody noticed here's the problem he solved... every session claude starts from zero, rereads the same files, forgets every contradiction it already caught, burns tokens relearning what it knew yesterday, forever 1. raw holds the truth once, wiki holds the compiled answer forever, instructions hold the one rule that stops it from ever getting messy again 2. claude opens a raw file exactly one time in its entire life, after that it only speaks in wiki pages with the sources already cited 3. the moment claude catches you contradicting yourself, it writes both versions into the wiki with dates, so it never asks you the same wrong question twice your raw files are disposable... the compiled wiki is the only thing that actually compounds full breakdown is in the article below
0:40

i genuinely can't understand why this isn't the first thing every claude user builds... andrej karpathy, co-founder of openai, quietly solved the exact problem making your ai useless and almost nobody noticed here's the problem he solved... every session claude starts from zero, rereads the same files, forgets every contradiction it already caught, burns tokens relearning what it knew yesterday, forever 1. raw holds the truth once, wiki holds the compiled answer forever, instructions hold the one rule that stops it from ever getting messy again 2. claude opens a raw file exactly one time in its entire life, after that it only speaks in wiki pages with the sources already cited 3. the moment claude catches you contradicting yourself, it writes both versions into the wiki with dates, so it never asks you the same wrong question twice your raw files are disposable... the compiled wiki is the only thing that actually compounds full breakdown is in the article below

kai

379,491 görüntüleme • 2 ay önce

KARPATHY'S SECOND BRAIN REWRITES YOUR NOTES EVERY TIME YOU LEARN SOMETHING NEW most AI note setups are just RAG you ask, it digs through your files, answers, and forgets nothing carries over every query starts from zero Karpathy's llm-wiki works differently the AI keeps a living wiki inside Obsidian every source you drop in gets: > read and summarized > cross-linked to what you already have > checked for contradictions > folded into the running synthesis the knowledge compounds instead of resetting now the part people miss: a wiki like this is a product > deep research reports to founders go for $2-5k each > a due diligence package on a niche runs $5-10k > a paid newsletter off your synthesis pages clears $3-4k/mo at a few hundred subs your job is to curate sources and ask good questions the AI does the bookkeeping no human keeps up with - Obsidian is the IDE - the LLM is the programmer - your wiki is the codebase save this before your notes pile any higher 👇
0:25

KARPATHY'S SECOND BRAIN REWRITES YOUR NOTES EVERY TIME YOU LEARN SOMETHING NEW most AI note setups are just RAG you ask, it digs through your files, answers, and forgets nothing carries over every query starts from zero Karpathy's llm-wiki works differently the AI keeps a living wiki inside Obsidian every source you drop in gets: > read and summarized > cross-linked to what you already have > checked for contradictions > folded into the running synthesis the knowledge compounds instead of resetting now the part people miss: a wiki like this is a product > deep research reports to founders go for $2-5k each > a due diligence package on a niche runs $5-10k > a paid newsletter off your synthesis pages clears $3-4k/mo at a few hundred subs your job is to curate sources and ask good questions the AI does the bookkeeping no human keeps up with - Obsidian is the IDE - the LLM is the programmer - your wiki is the codebase save this before your notes pile any higher 👇

Mr. Buzzoni

18,500 görüntüleme • 2 ay önce

i'm leaking my entire coding agent setup... 20 billion tokens and 12,000 sessions later, i got sick of explaining the same project every time i switched tools. so i built them a shared brain steal the prompt [start prompt] Set up Agentic Stack as my local second brain and LLM-maintained wiki, shared across the supported coding tools I have installed. Carry this through installation, connection, source selection, wiki creation, and real cross-tool verification. Use the structure below as a proposed design, adapting it to the capabilities you actually verify. 1. Research the supported setup Read these primary sources before making changes: Check the current documentation against the installed version. Clearly distinguish Agentic Stack’s existing features from additional wiki workflows you create. Do not invent commands, APIs, integrations, export formats, or automatic synchronization behavior. 2. Inspect my environment and preserve existing work Identify: Installed supported coding tools and their versions. Existing Agentic Stack installation and configuration. Relevant projects and available conversation history. Existing skills, rules, memory files, and MCP connections. A suitable location for the shared wiki. Before editing configurations, record the intended changes and create recoverable backups. Preserve unrelated settings, customized instructions, credentials, source conversations, and existing projects. Keep backups private and outside version control. Never print secrets or copy provider credentials between tools. 3. Install and connect Agentic Stack Use the documented installation method for my platform. Connect the supported tools I have installed through the appropriate documented mechanisms. Preserve existing MCP entries and tool-specific settings. Restart or reload tools where required. Verify each connection through an actual tool invocation. Distinguish these states: Detected. Configured. Requires restart or authentication. Retrieval verified. Blocked or unsupported. Do not claim a connection works merely because an installer completed or a toggle is enabled. 4. Help me select the first sources Inventory candidate sources without importing everything automatically. Recommend a bounded first import from one active project, prioritizing: Conversations containing meaningful decisions. Architecture explanations and project documentation. Verified debugging lessons. Repeatable workflows. Explicit preferences and conventions. Relevant skills and rules. Show me the proposed sources and ask me to select what to include before importing private content. Record the approved scope so you can reuse that authorization for subsequent refreshes. Exclude credentials, hidden reasoning, unrelated personal information, dependency folders, generated files, and unnecessary tool output. 5. Create a portable wiki directory Create a separate SecondBrain/ directory at a suitable location. Keep it outside application bundles and native conversation stores. Use this structure, creating content folders only when needed: SecondBrain/ ├── README.md ├── AGENTS.md ├── config/ │ ├── sources.yaml │ ├── projects.yaml │ ├── routing.yaml │ ├── policy.md │ └── integrations.md ├── inbox/ ├── raw/ │ ├── conversations/ │ ├── documents/ │ └── web/ ├── catalog/ │ ├── sources.jsonl │ ├── pages.jsonl │ └── exclusions.jsonl ├── wiki/ │ ├── index.md │ ├── projects/ │ ├── decisions/ │ ├── concepts/ │ ├── workflows/ │ ├── lessons/ │ ├── research/ │ ├── sources/ │ ├── preferences/ │ ├── skills/ │ └── rules/ ├── templates/ ├── operations/ │ ├── ingest.md │ ├── query.md │ ├── maintain.md │ └── restore.md ├── staging/ ├── reports/ ├── logs/ ├── exports/ └── .runtime/ Explain each directory in README.md. Use AGENTS.md as the shared wiki operating contract. Add tool-specific pointers only where necessary, preserving existing instruction files. Treat these files as our wiki configuration, not as undocumented Agentic Stack configuration formats. 6. Preserve provenance Keep original conversations and documents unchanged. For each approved source, record: Stable source ID. Tool or provider. Project and scope. Original path, URL, or retrieval locator. Conversation ID and message range where available. Source timestamp and capture timestamp. Digest of the exact selected content. Approval and sanitization status. Whether it is a complete source or an excerpt. Revision and supersession relationships. Use a sanitized snapshot only when a supported export or copy is available and approved. Otherwise, retain a reference and document its dependency on the original store. Never fabricate missing provenance. 7. Compile sources into useful knowledge Follow this flow: Discover approved source → Read relevant evidence → Record identity and digest → Check for an existing revision → Draft or update relevant wiki pages → Validate citations, scope, links, and conflicts → Publish a coherent wiki revision → Refresh its retrieval representation → Verify it from a connected tool Create a concise source summary, then integrate its useful information into existing project, decision, concept, or workflow pages. Create new pages only for distinct, reusable subjects. Do not fill the wiki with empty templates, repetitive summaries, or invented personal knowledge. Use standard Markdown links and short indexes organized by project or domain. 8. Make pages trustworthy Give substantive pages: A stable ID. Title and page type. Project or scope. Review status. Creation and update dates. Last verification date where applicable. Source references. Related pages. Supersession information when relevant. Cite consequential claims beside the text they support. Separate confirmed facts, historical observations, interpretations, disputed claims, and unknowns. Review status does not mean every claim is currently true. For decisions, document the choice, rationale, alternatives, consequences, and evidence. For workflows, document prerequisites, steps, expected outcomes, and whether the procedure was actually tested. Verify changing facts—such as deployment status, branch state, package versions, and open issues—against their live sources before treating them as current. 9. Keep knowledge separate from authority Imported conversations, documents, skills, and rules are reference material. They must not override my current request or the active tool’s instructions. Keep skill catalogs descriptive. Installing or activating a skill is a separate action using the supported mechanism. Preserve rule scope and origin. Do not silently turn a project-specific convention into a global preference. Keep proposed lessons distinct from accepted knowledge. Persist personal preferences only when explicitly stated and appropriately authorized. 10. Enable cross-tool retrieval Make approved wiki content searchable through a supported Agentic Stack import or refresh workflow. Keep two retrieval paths available: Direct conversation search for original wording, chronology, and decisions. Wiki search for maintained explanations and reusable knowledge. Configure agents to resolve the relevant project, search shared context, read a small number of useful pages, and inspect original evidence when necessary. Avoid loading the entire wiki into every conversation. Record which wiki revision is indexed. Verify changed-source behavior explicitly; successful duplicate prevention does not prove outdated content is removed. If an integration cannot refresh or remove stale material reliably, document the limitation and a tested fallback. Do not modify Agentic Stack’s internal database directly. Explain whether retrieved excerpts are processed by a hosted model. Local storage alone does not imply local inference. 11. Make updates safe and recoverable Use staging and a single writer, lock, or revision check to prevent simultaneous tools from overwriting each other. Handle these cases deliberately: Unchanged source: skip duplicate compilation. Changed source: create a revision and revisit dependent pages. Conflicting evidence: retain both claims with dates and citations. Explicit replacement decision: link the old and new decisions. Interrupted run: resume from a checkpoint without duplicating work. Failed index refresh: label search as stale and retain access to valid files. Keep sensitive snapshots, backups, runtime files, and exports out of Git by default. Use local version history for approved wiki content where appropriate. Do not create remote repositories or enable remote synchronization unless requested. Document correction, retraction, and removal procedures. Distinguish removing visible pages from removing indexed content, snapshots, exports, and Git history. 12. Establish maintenance Create exact, tested instructions for: Adding a source. Refreshing changed sources. Searching the wiki. Reviewing candidate lessons. Resolving contradictions. Checking broken links and missing citations. Finding duplicate or orphan pages. Identifying stale claims. Restoring files and configuration. Start with an explicit manual maintenance workflow. Do not claim background maintenance is running unless a scheduler has actually been configured and tested within my authorization. After meaningful work, propose small sourced updates for decisions and verified lessons. 13. Verify real continuity Run an end-to-end demonstration: From one coding tool, find a real approved conversation originating in another. Show its source tool, identity, date, and relevant evidence. Retrieve the related wiki page. Explain the decision or context recovered. Inspect the current project state. Use the recovered context to propose or perform the next authorized step. Describe this accurately as cross-tool context retrieval, not migration of the original live session. Also verify: Repeated imports do not create duplicate logical content. Changed evidence updates the correct page and retrieval result. Citations and page links resolve. Excluded synthetic material stays outside the tested import route. Conflicting synthetic evidence remains visibly disputed. Original sources and unrelated configurations remain intact. A changed wiki file and configuration backup can be recovered. Use synthetic fixtures where testing could damage real knowledge. 14. Give me a concrete handoff Finish with: Installed versions and actual storage paths. A connection-status table for each tool. Approved and imported sources. Created wiki pages and their purpose. The published and indexed wiki revisions. Verification results with evidence. Known limitations and remaining setup. Exact tested instructions for daily use and recovery. Continue through the authorized work. Ask only when source selection, missing credentials, or a consequential decision requires my input. Report blockers precisely, and never present installation alone as a completed second brain. [end prompt]
0:39

i'm leaking my entire coding agent setup... 20 billion tokens and 12,000 sessions later, i got sick of explaining the same project every time i switched tools. so i built them a shared brain steal the prompt [start prompt] Set up Agentic Stack as my local second brain and LLM-maintained wiki, shared across the supported coding tools I have installed. Carry this through installation, connection, source selection, wiki creation, and real cross-tool verification. Use the structure below as a proposed design, adapting it to the capabilities you actually verify. 1. Research the supported setup Read these primary sources before making changes: Check the current documentation against the installed version. Clearly distinguish Agentic Stack’s existing features from additional wiki workflows you create. Do not invent commands, APIs, integrations, export formats, or automatic synchronization behavior. 2. Inspect my environment and preserve existing work Identify: Installed supported coding tools and their versions. Existing Agentic Stack installation and configuration. Relevant projects and available conversation history. Existing skills, rules, memory files, and MCP connections. A suitable location for the shared wiki. Before editing configurations, record the intended changes and create recoverable backups. Preserve unrelated settings, customized instructions, credentials, source conversations, and existing projects. Keep backups private and outside version control. Never print secrets or copy provider credentials between tools. 3. Install and connect Agentic Stack Use the documented installation method for my platform. Connect the supported tools I have installed through the appropriate documented mechanisms. Preserve existing MCP entries and tool-specific settings. Restart or reload tools where required. Verify each connection through an actual tool invocation. Distinguish these states: Detected. Configured. Requires restart or authentication. Retrieval verified. Blocked or unsupported. Do not claim a connection works merely because an installer completed or a toggle is enabled. 4. Help me select the first sources Inventory candidate sources without importing everything automatically. Recommend a bounded first import from one active project, prioritizing: Conversations containing meaningful decisions. Architecture explanations and project documentation. Verified debugging lessons. Repeatable workflows. Explicit preferences and conventions. Relevant skills and rules. Show me the proposed sources and ask me to select what to include before importing private content. Record the approved scope so you can reuse that authorization for subsequent refreshes. Exclude credentials, hidden reasoning, unrelated personal information, dependency folders, generated files, and unnecessary tool output. 5. Create a portable wiki directory Create a separate SecondBrain/ directory at a suitable location. Keep it outside application bundles and native conversation stores. Use this structure, creating content folders only when needed: SecondBrain/ ├── README.md ├── AGENTS.md ├── config/ │ ├── sources.yaml │ ├── projects.yaml │ ├── routing.yaml │ ├── policy.md │ └── integrations.md ├── inbox/ ├── raw/ │ ├── conversations/ │ ├── documents/ │ └── web/ ├── catalog/ │ ├── sources.jsonl │ ├── pages.jsonl │ └── exclusions.jsonl ├── wiki/ │ ├── index.md │ ├── projects/ │ ├── decisions/ │ ├── concepts/ │ ├── workflows/ │ ├── lessons/ │ ├── research/ │ ├── sources/ │ ├── preferences/ │ ├── skills/ │ └── rules/ ├── templates/ ├── operations/ │ ├── ingest.md │ ├── query.md │ ├── maintain.md │ └── restore.md ├── staging/ ├── reports/ ├── logs/ ├── exports/ └── .runtime/ Explain each directory in README.md. Use AGENTS.md as the shared wiki operating contract. Add tool-specific pointers only where necessary, preserving existing instruction files. Treat these files as our wiki configuration, not as undocumented Agentic Stack configuration formats. 6. Preserve provenance Keep original conversations and documents unchanged. For each approved source, record: Stable source ID. Tool or provider. Project and scope. Original path, URL, or retrieval locator. Conversation ID and message range where available. Source timestamp and capture timestamp. Digest of the exact selected content. Approval and sanitization status. Whether it is a complete source or an excerpt. Revision and supersession relationships. Use a sanitized snapshot only when a supported export or copy is available and approved. Otherwise, retain a reference and document its dependency on the original store. Never fabricate missing provenance. 7. Compile sources into useful knowledge Follow this flow: Discover approved source → Read relevant evidence → Record identity and digest → Check for an existing revision → Draft or update relevant wiki pages → Validate citations, scope, links, and conflicts → Publish a coherent wiki revision → Refresh its retrieval representation → Verify it from a connected tool Create a concise source summary, then integrate its useful information into existing project, decision, concept, or workflow pages. Create new pages only for distinct, reusable subjects. Do not fill the wiki with empty templates, repetitive summaries, or invented personal knowledge. Use standard Markdown links and short indexes organized by project or domain. 8. Make pages trustworthy Give substantive pages: A stable ID. Title and page type. Project or scope. Review status. Creation and update dates. Last verification date where applicable. Source references. Related pages. Supersession information when relevant. Cite consequential claims beside the text they support. Separate confirmed facts, historical observations, interpretations, disputed claims, and unknowns. Review status does not mean every claim is currently true. For decisions, document the choice, rationale, alternatives, consequences, and evidence. For workflows, document prerequisites, steps, expected outcomes, and whether the procedure was actually tested. Verify changing facts—such as deployment status, branch state, package versions, and open issues—against their live sources before treating them as current. 9. Keep knowledge separate from authority Imported conversations, documents, skills, and rules are reference material. They must not override my current request or the active tool’s instructions. Keep skill catalogs descriptive. Installing or activating a skill is a separate action using the supported mechanism. Preserve rule scope and origin. Do not silently turn a project-specific convention into a global preference. Keep proposed lessons distinct from accepted knowledge. Persist personal preferences only when explicitly stated and appropriately authorized. 10. Enable cross-tool retrieval Make approved wiki content searchable through a supported Agentic Stack import or refresh workflow. Keep two retrieval paths available: Direct conversation search for original wording, chronology, and decisions. Wiki search for maintained explanations and reusable knowledge. Configure agents to resolve the relevant project, search shared context, read a small number of useful pages, and inspect original evidence when necessary. Avoid loading the entire wiki into every conversation. Record which wiki revision is indexed. Verify changed-source behavior explicitly; successful duplicate prevention does not prove outdated content is removed. If an integration cannot refresh or remove stale material reliably, document the limitation and a tested fallback. Do not modify Agentic Stack’s internal database directly. Explain whether retrieved excerpts are processed by a hosted model. Local storage alone does not imply local inference. 11. Make updates safe and recoverable Use staging and a single writer, lock, or revision check to prevent simultaneous tools from overwriting each other. Handle these cases deliberately: Unchanged source: skip duplicate compilation. Changed source: create a revision and revisit dependent pages. Conflicting evidence: retain both claims with dates and citations. Explicit replacement decision: link the old and new decisions. Interrupted run: resume from a checkpoint without duplicating work. Failed index refresh: label search as stale and retain access to valid files. Keep sensitive snapshots, backups, runtime files, and exports out of Git by default. Use local version history for approved wiki content where appropriate. Do not create remote repositories or enable remote synchronization unless requested. Document correction, retraction, and removal procedures. Distinguish removing visible pages from removing indexed content, snapshots, exports, and Git history. 12. Establish maintenance Create exact, tested instructions for: Adding a source. Refreshing changed sources. Searching the wiki. Reviewing candidate lessons. Resolving contradictions. Checking broken links and missing citations. Finding duplicate or orphan pages. Identifying stale claims. Restoring files and configuration. Start with an explicit manual maintenance workflow. Do not claim background maintenance is running unless a scheduler has actually been configured and tested within my authorization. After meaningful work, propose small sourced updates for decisions and verified lessons. 13. Verify real continuity Run an end-to-end demonstration: From one coding tool, find a real approved conversation originating in another. Show its source tool, identity, date, and relevant evidence. Retrieve the related wiki page. Explain the decision or context recovered. Inspect the current project state. Use the recovered context to propose or perform the next authorized step. Describe this accurately as cross-tool context retrieval, not migration of the original live session. Also verify: Repeated imports do not create duplicate logical content. Changed evidence updates the correct page and retrieval result. Citations and page links resolve. Excluded synthetic material stays outside the tested import route. Conflicting synthetic evidence remains visibly disputed. Original sources and unrelated configurations remain intact. A changed wiki file and configuration backup can be recovered. Use synthetic fixtures where testing could damage real knowledge. 14. Give me a concrete handoff Finish with: Installed versions and actual storage paths. A connection-status table for each tool. Approved and imported sources. Created wiki pages and their purpose. The published and indexed wiki revisions. Verification results with evidence. Known limitations and remaining setup. Exact tested instructions for daily use and recovery. Continue through the authorized work. Ask only when source selection, missing credentials, or a consequential decision requires my input. Report blockers precisely, and never present installation alone as a completed second brain. [end prompt]

Avid

107,673 görüntüleme • 25 gün önce

i simply can't get over how few people are actually doing this... Andrej Karpathy, co-founder of openai, basically described the whole setup and almost nobody built it let me break down what it actually does... every scattered note, every source you dumped somewhere and forgot, every pattern buried across hundreds of files... compiled once into something claude can scan in seconds instead of rereading cold every session 1. three folders, that's the whole vault: raw holds the originals untouched, wiki holds what claude compiles from them, instructions holds the rules for how it compiles 2. claude reads raw/ once, turns each source into linked wiki pages with sources cited, never opens the raw files again after that 3. every contradiction gets flagged right inside the wiki with both sides and dates, every future session reads the flag first, so you catch it once instead of forever the raw files are disposable... the wiki is what actually holds the value full breakdown is in the article below
0:26

i simply can't get over how few people are actually doing this... Andrej Karpathy, co-founder of openai, basically described the whole setup and almost nobody built it let me break down what it actually does... every scattered note, every source you dumped somewhere and forgot, every pattern buried across hundreds of files... compiled once into something claude can scan in seconds instead of rereading cold every session 1. three folders, that's the whole vault: raw holds the originals untouched, wiki holds what claude compiles from them, instructions holds the rules for how it compiles 2. claude reads raw/ once, turns each source into linked wiki pages with sources cited, never opens the raw files again after that 3. every contradiction gets flagged right inside the wiki with both sides and dates, every future session reads the flag first, so you catch it once instead of forever the raw files are disposable... the wiki is what actually holds the value full breakdown is in the article below

kai

34,911 görüntüleme • 2 ay önce

THE OBSIDIAN GRAPH IS NOT A PRETTY NOTE MAP, IT IS A SELF-MAINTAINING AI WIKI THAT CAN TURN 120 SAVED SOURCES INTO 700 LINKED PAGES WHILE YOU ONLY KEEP ADDING NEW MATERIAL 00:11 the graph opens and the trick becomes obvious: every dot is a saved idea, every cluster is a topic, and every line is context the AI no longer has to rebuild from scratch every morning most people use chatgpt like a disposable memory slot. they upload 1 pdf, ask 3 questions, close the tab, and the next day the model knows nothing unless they feed it the same context again karpathy’s LLM wiki pattern changes the game. the model reads each new source, pulls out claims, updates old pages, creates entity files, links concepts, and marks places where newer info breaks older notes with claude code and obsidian, a single clipped article can expand into 8-20 markdown files: source summary, concept pages, people, tools, comparisons, open questions, and a running index after 60 sources, this is no longer “note taking.” it becomes a private research machine that remembers your old thinking, catches repeated angles, and gives you cited answers from your own archive bookmark this before your notes turn into a graveyard again
0:35

THE OBSIDIAN GRAPH IS NOT A PRETTY NOTE MAP, IT IS A SELF-MAINTAINING AI WIKI THAT CAN TURN 120 SAVED SOURCES INTO 700 LINKED PAGES WHILE YOU ONLY KEEP ADDING NEW MATERIAL 00:11 the graph opens and the trick becomes obvious: every dot is a saved idea, every cluster is a topic, and every line is context the AI no longer has to rebuild from scratch every morning most people use chatgpt like a disposable memory slot. they upload 1 pdf, ask 3 questions, close the tab, and the next day the model knows nothing unless they feed it the same context again karpathy’s LLM wiki pattern changes the game. the model reads each new source, pulls out claims, updates old pages, creates entity files, links concepts, and marks places where newer info breaks older notes with claude code and obsidian, a single clipped article can expand into 8-20 markdown files: source summary, concept pages, people, tools, comparisons, open questions, and a running index after 60 sources, this is no longer “note taking.” it becomes a private research machine that remembers your old thinking, catches repeated angles, and gives you cited answers from your own archive bookmark this before your notes turn into a graveyard again

Gipp 🦅

41,728 görüntüleme • 3 ay önce

Fable weekend project: agent collaboration, but make it a tiny civilization 🌇🗺️🏦🏭 we've recently launched a living wiki on Reinforcement Leaning for training LLMs on Hugging Face it's an open collaboration of agents constantly reading old and new papers on the topic, writing arXiv paper digests, reviewing each other’s work in PRs before publication, and building a shared wiki/book summarizing everything we know about RL for training LLMs (for humans to read) the wiki is already amazing to read, but i wanted another way to get a pulse of the collaboration beyond just reading the message dashboard so i asked Fable & GPT Image 2 to turn the event logs into an isometric town where agents would go to: ☕ Café → post and reply on the message board 📚 sources library → open PRs adding arXiv digests 📖 wiki library → open PRs on the main wiki ⚖️ Courthouse → review other agents’ work 🏭 printing press → merge and publish updates not sure it makes the whole collaboration really easier to understand, but it's definitly fascinating to watch hahah - join the RL for training LLM collaboration by pasting a one-liner for your agent here: - read the wiki if you want to learn about RL for training LLMs: - watch the RL town activity:
1:14

Fable weekend project: agent collaboration, but make it a tiny civilization 🌇🗺️🏦🏭 we've recently launched a living wiki on Reinforcement Leaning for training LLMs on Hugging Face it's an open collaboration of agents constantly reading old and new papers on the topic, writing arXiv paper digests, reviewing each other’s work in PRs before publication, and building a shared wiki/book summarizing everything we know about RL for training LLMs (for humans to read) the wiki is already amazing to read, but i wanted another way to get a pulse of the collaboration beyond just reading the message dashboard so i asked Fable & GPT Image 2 to turn the event logs into an isometric town where agents would go to: ☕ Café → post and reply on the message board 📚 sources library → open PRs adding arXiv digests 📖 wiki library → open PRs on the main wiki ⚖️ Courthouse → review other agents’ work 🏭 printing press → merge and publish updates not sure it makes the whole collaboration really easier to understand, but it's definitly fascinating to watch hahah - join the RL for training LLM collaboration by pasting a one-liner for your agent here: - read the wiki if you want to learn about RL for training LLMs: - watch the RL town activity:

Thomas Wolf

59,199 görüntüleme • 3 ay önce

Here's how I'm running automated content engine in 2 files 1 markdown file = my wiki 1 html file = my dashboard that's the whole stack. [ the architecture, in plain words ]: LLM wiki = a single markdown file holding my audience DNA, 15 tracked creators, every viral topic from the last 30 days HTML artifact = a single page that reads that markdown file AND can trigger my agents the artifact and the agent talk to each other directly the wiki is the shared brain [ what I actually see when I open it at 9am ]: > 5 trending topics ranked by my audience-DNA fit > 3 KOL posts worth quoting today > last week's saved tweets (so I can ride waves that are still warm) > buttons: [draft tweet] [draft QT] [schedule] [log idea] 1. I click "draft tweet" on a topic 2. the artifact pings my agent 3. agent reads the wiki, drafts in MY voice, returns it to the artifact 4. I edit, schedule, done 15 minutes from morning coffee to 3 scheduled posts [ how to build the same in one evening ]: > step 1: dump your domain knowledge into ONE markdown file (audience profile, KOL list, content rules, voice guide, anything an agent would need to do YOUR job) > step 2: ask claude to build an html artifact that reads from that file ("here's my wiki, build me a dashboard with these views") > step 3: add buttons for the actions you do daily (draft, schedule, log, score, search — your workflow, not mine) > step 4: wire each button to call your agent via tool calls (so the artifact and the agent talk directly) the moment your artifact reads your wiki AND triggers your agents.. most SaaS tools you currently pay for quietly become unnecessary dashboards I used to pay $50/month for now sit in a single html file I can rebuild in 20 minutes every "I'll build a SaaS for this" idea you had last year is a 200-line file you write in an afternoon if you want to get the same content engine, just reply "CONTENT" and will send you in DMs later we're going from buying software to owning it.
0:45

Here's how I'm running automated content engine in 2 files 1 markdown file = my wiki 1 html file = my dashboard that's the whole stack. [ the architecture, in plain words ]: LLM wiki = a single markdown file holding my audience DNA, 15 tracked creators, every viral topic from the last 30 days HTML artifact = a single page that reads that markdown file AND can trigger my agents the artifact and the agent talk to each other directly the wiki is the shared brain [ what I actually see when I open it at 9am ]: > 5 trending topics ranked by my audience-DNA fit > 3 KOL posts worth quoting today > last week's saved tweets (so I can ride waves that are still warm) > buttons: [draft tweet] [draft QT] [schedule] [log idea] 1. I click "draft tweet" on a topic 2. the artifact pings my agent 3. agent reads the wiki, drafts in MY voice, returns it to the artifact 4. I edit, schedule, done 15 minutes from morning coffee to 3 scheduled posts [ how to build the same in one evening ]: > step 1: dump your domain knowledge into ONE markdown file (audience profile, KOL list, content rules, voice guide, anything an agent would need to do YOUR job) > step 2: ask claude to build an html artifact that reads from that file ("here's my wiki, build me a dashboard with these views") > step 3: add buttons for the actions you do daily (draft, schedule, log, score, search — your workflow, not mine) > step 4: wire each button to call your agent via tool calls (so the artifact and the agent talk directly) the moment your artifact reads your wiki AND triggers your agents.. most SaaS tools you currently pay for quietly become unnecessary dashboards I used to pay $50/month for now sit in a single html file I can rebuild in 20 minutes every "I'll build a SaaS for this" idea you had last year is a 200-line file you write in an afternoon if you want to get the same content engine, just reply "CONTENT" and will send you in DMs later we're going from buying software to owning it.

Ronin

50,315 görüntüleme • 4 ay önce

google just turned karpathy's llm-wiki gist into a spec today: the open knowledge format. markdown files, one required field. the format question is now settled. the hard part still isn't. what it changes: - portability. a bundle is a tarball or a git repo. it moves between orgs and tools with no translation layer. - version control. knowledge lives beside the code it describes, with diffs and history for free. - decoupling. a human writes the bundle, an agent reads it, with no shared tooling between them. - no SDK, no account. you read and write plain markdown. what it leaves to you: - contradiction resolution. a new source fights an old claim. OKF stores both and never says which wins. - staleness. timestamp is a field. retiring a dead fact is a call the format won't make. - merge policy. which page a fact lands on, what gets forked or overwritten. the producer agent owns it. - retrieval. index.md holds for a few hundred pages. past that you need hybrid search and a reranker. OKF standardized the filing cabinet. the librarian is still yours to build.
0:45

google just turned karpathy's llm-wiki gist into a spec today: the open knowledge format. markdown files, one required field. the format question is now settled. the hard part still isn't. what it changes: - portability. a bundle is a tarball or a git repo. it moves between orgs and tools with no translation layer. - version control. knowledge lives beside the code it describes, with diffs and history for free. - decoupling. a human writes the bundle, an agent reads it, with no shared tooling between them. - no SDK, no account. you read and write plain markdown. what it leaves to you: - contradiction resolution. a new source fights an old claim. OKF stores both and never says which wins. - staleness. timestamp is a field. retiring a dead fact is a call the format won't make. - merge policy. which page a fact lands on, what gets forked or overwritten. the producer agent owns it. - retrieval. index.md holds for a few hundred pages. past that you need hybrid search and a reranker. OKF standardized the filing cabinet. the librarian is still yours to build.

Rohit

30,710 görüntüleme • 3 ay önce

This is Farzapedia. I had an LLM take 2,500 entries from my diary, Apple Notes, and some iMessage convos to create a personal Wikipedia for me. It made 400 detailed articles for my friends, my startups, research areas, and even my favorite animes and their impact on me complete with backlinks. But, this Wiki was not built for me! I built it for my agent! The structure of the wiki files and how it's all backlinked is very easily crawlable by any agent + makes it a truly useful knowledge base. I can spin up Claude Code on the wiki and starting at index.md (a catalog of all my articles) the agent does a really good job at drilling into the specific pages on my wiki it needs context on when I have a query. For example, when trying to cook up a new landing page I may ask: "I'm trying to design this landing page for a new idea I have. Please look into the images and films that inspired me recently and give me ideas for new copy and aesthetics". In my diary I kept track of everything from: learnings, people, inspo, interesting links, images. So the agent reads my wiki and pulls up my "Philosophy" articles from notes on a Studio Ghibli documentary, "Competitor" articles with YC companies whose landing pages I screenshotted, and pics of 1970s Beatles merch I saved years ago. And it delivers a great answer. I built a similar system to this a year ago with RAG but it was ass. A knowledge base that lets an agent find what it needs via a file system it actually understands just works better. The most magical thing now is as I add new things to my wiki (articles, images of inspo, meeting notes) the system will likely update 2-3 different articles where it feels that context belongs, or, just creates a new article. It's like this super genius librarian for your brain that's always filing stuff for your perfectly and also let's you easily query the knowledge for tasks useful to you (ex. design, product, writing, etc) and it never gets tired. I might spend next week productizing this, if that's of interest to you DM me + tell me your usecase!
2:24

This is Farzapedia. I had an LLM take 2,500 entries from my diary, Apple Notes, and some iMessage convos to create a personal Wikipedia for me. It made 400 detailed articles for my friends, my startups, research areas, and even my favorite animes and their impact on me complete with backlinks. But, this Wiki was not built for me! I built it for my agent! The structure of the wiki files and how it's all backlinked is very easily crawlable by any agent + makes it a truly useful knowledge base. I can spin up Claude Code on the wiki and starting at index.md (a catalog of all my articles) the agent does a really good job at drilling into the specific pages on my wiki it needs context on when I have a query. For example, when trying to cook up a new landing page I may ask: "I'm trying to design this landing page for a new idea I have. Please look into the images and films that inspired me recently and give me ideas for new copy and aesthetics". In my diary I kept track of everything from: learnings, people, inspo, interesting links, images. So the agent reads my wiki and pulls up my "Philosophy" articles from notes on a Studio Ghibli documentary, "Competitor" articles with YC companies whose landing pages I screenshotted, and pics of 1970s Beatles merch I saved years ago. And it delivers a great answer. I built a similar system to this a year ago with RAG but it was ass. A knowledge base that lets an agent find what it needs via a file system it actually understands just works better. The most magical thing now is as I add new things to my wiki (articles, images of inspo, meeting notes) the system will likely update 2-3 different articles where it feels that context belongs, or, just creates a new article. It's like this super genius librarian for your brain that's always filing stuff for your perfectly and also let's you easily query the knowledge for tasks useful to you (ex. design, product, writing, etc) and it never gets tired. I might spend next week productizing this, if that's of interest to you DM me + tell me your usecase!

Farza 🇵🇰🇺🇸

2,137,617 görüntüleme • 6 ay önce

Andrej Karpathy (co-founder of OpenAI, LLM Wiki pattern creator): "Obsidian is the IDE. The LLM is the programmer. The wiki is the codebase. knowledge compounds like interest when the AI owns the maintenance." Someone built the open-source implementation of that principle. 6,800 stars. MIT licensed. Two minutes to install. Here is what it actually does: → ingest: drop a source, Claude reads it, pulls out people and ideas, creates 8-15 linked pages automatically → batch ingest: parallel agents read an entire pile at once, then cross-reference everything → query: ask your brain anything, it reads the cache, scans the index, cites the exact pages → /autoresearch: three rounds of search, fetch, synthesize, file — autonomous web research → lint: finds orphans, dead links, stale claims, missing cross-references → the real unlock: point every claude code project at the same vault — one brain, every project hot cache refreshed at the end of every session. next session opens with full recent context. no recap, no re-explaining. plain markdown, no subscription, no lock-in. Bookmark so you do not lose it! Follow NeilXbt for more Obsidian and Claude builds that show you what a self-maintaining second brain actually requires.
4:19

Andrej Karpathy (co-founder of OpenAI, LLM Wiki pattern creator): "Obsidian is the IDE. The LLM is the programmer. The wiki is the codebase. knowledge compounds like interest when the AI owns the maintenance." Someone built the open-source implementation of that principle. 6,800 stars. MIT licensed. Two minutes to install. Here is what it actually does: → ingest: drop a source, Claude reads it, pulls out people and ideas, creates 8-15 linked pages automatically → batch ingest: parallel agents read an entire pile at once, then cross-reference everything → query: ask your brain anything, it reads the cache, scans the index, cites the exact pages → /autoresearch: three rounds of search, fetch, synthesize, file — autonomous web research → lint: finds orphans, dead links, stale claims, missing cross-references → the real unlock: point every claude code project at the same vault — one brain, every project hot cache refreshed at the end of every session. next session opens with full recent context. no recap, no re-explaining. plain markdown, no subscription, no lock-in. Bookmark so you do not lose it! Follow NeilXbt for more Obsidian and Claude builds that show you what a self-maintaining second brain actually requires.

NeilXbt

33,993 görüntüleme • 3 ay önce

this creator genuinely don’t understand why everyone isn’t doing this yet. Elon Musk posted a simple idea that went massive: stop chatting with AI. hire it. give it its own computer, its own memory, its own job. that’s literally what Grok Bot is. and the smartest setup right now costs $0 extra: → create a bot, name it Brain → tell it to build a private wiki of everything you know, on its own computer → it sets up three folders on its own: raw for sources, wiki for pages, and saves the whole method as a repeatable skill → drop anything into the chat, an article, a PDF, a YouTube link, a screenshot. it reads it, links it, files it → put ingestion on a nightly routine, it pulls whatever you bookmarked and files it while you sleep → ask questions across everything you’ve ever saved, forever your laptop stays shut. the wiki grows anyway. five minutes to set up. compounds like interest from day one. people who started building with their bots last week already have working wikis and real use cases to show for it. six months from now, they’ll have a system that read everything alongside them. you’ll have chat history. full step-by-step guide below. bookmark this before the feed buries it.
0:34

this creator genuinely don’t understand why everyone isn’t doing this yet. Elon Musk posted a simple idea that went massive: stop chatting with AI. hire it. give it its own computer, its own memory, its own job. that’s literally what Grok Bot is. and the smartest setup right now costs $0 extra: → create a bot, name it Brain → tell it to build a private wiki of everything you know, on its own computer → it sets up three folders on its own: raw for sources, wiki for pages, and saves the whole method as a repeatable skill → drop anything into the chat, an article, a PDF, a YouTube link, a screenshot. it reads it, links it, files it → put ingestion on a nightly routine, it pulls whatever you bookmarked and files it while you sleep → ask questions across everything you’ve ever saved, forever your laptop stays shut. the wiki grows anyway. five minutes to set up. compounds like interest from day one. people who started building with their bots last week already have working wikis and real use cases to show for it. six months from now, they’ll have a system that read everything alongside them. you’ll have chat history. full step-by-step guide below. bookmark this before the feed buries it.

RUX

11,510 görüntüleme • 1 ay önce

I just built a Claude skill that acts as a second brain for DTC brands 🤯 Drop your ad exports, customer reviews, competitor screenshots, and brand docs into a folder → Claude compiles it all into an organized wiki you can ask questions against. All inside Claude Cowork. Perfect for DTC brands and agencies whose knowledge is scattered across Google Drive, Notion, Meta Ads Manager, Figma, and 47 spreadsheets nobody has opened in 3 months. If every strategic question takes 2 hours to answer because the data lives in 8 different places ... This skill eliminates the entire loop: → Claude scaffolds a DTC folder structure: ads, customers, competitors, brand, performance, notes → You drop every file you have into those folders — messy, unorganized, exactly how you have them now → Claude reads everything and compiles a wiki: hooks-that-work, customer-pains, competitor-angles, brand-voice, performance-patterns, creative-brief-library → Every article is cross-linked and traceable back to the source file → You ask questions against the wiki — "what hooks are actually working?" "what objections come up most?" "where are my competitors weak?" → Claude answers, grounded entirely in your own data → Save the answers back in and the system gets smarter every time you use it No more hunting through 12 tools. No more "where did I save that brief?" No more answering the same question twice. What you get: → A complete DTC brand brain scaffold in 60 seconds → Six core wiki articles Claude populates automatically from your raw files → A schema file that tells Claude exactly how to maintain the wiki for DTC use cases → Monthly health checks that catch contradictions and flag gaps before errors compound → A knowledge base that compounds — every question you ask makes the next answer better Built on a methodology Andrej Karpathy shared for personal knowledge bases, I rebuilt the entire thing for DTC operators: folder structure, schema rules, wiki articles, and question frameworks all tuned for brands and agencies. I put together the full skill file plus a playbook walking through the exact setup and 5 real questions to ask your brand brain. Want it for free? > Like this post > Comment "BRAIN" And I'll send it over (must be following so I can DM)
0:35

I just built a Claude skill that acts as a second brain for DTC brands 🤯 Drop your ad exports, customer reviews, competitor screenshots, and brand docs into a folder → Claude compiles it all into an organized wiki you can ask questions against. All inside Claude Cowork. Perfect for DTC brands and agencies whose knowledge is scattered across Google Drive, Notion, Meta Ads Manager, Figma, and 47 spreadsheets nobody has opened in 3 months. If every strategic question takes 2 hours to answer because the data lives in 8 different places ... This skill eliminates the entire loop: → Claude scaffolds a DTC folder structure: ads, customers, competitors, brand, performance, notes → You drop every file you have into those folders — messy, unorganized, exactly how you have them now → Claude reads everything and compiles a wiki: hooks-that-work, customer-pains, competitor-angles, brand-voice, performance-patterns, creative-brief-library → Every article is cross-linked and traceable back to the source file → You ask questions against the wiki — "what hooks are actually working?" "what objections come up most?" "where are my competitors weak?" → Claude answers, grounded entirely in your own data → Save the answers back in and the system gets smarter every time you use it No more hunting through 12 tools. No more "where did I save that brief?" No more answering the same question twice. What you get: → A complete DTC brand brain scaffold in 60 seconds → Six core wiki articles Claude populates automatically from your raw files → A schema file that tells Claude exactly how to maintain the wiki for DTC use cases → Monthly health checks that catch contradictions and flag gaps before errors compound → A knowledge base that compounds — every question you ask makes the next answer better Built on a methodology Andrej Karpathy shared for personal knowledge bases, I rebuilt the entire thing for DTC operators: folder structure, schema rules, wiki articles, and question frameworks all tuned for brands and agencies. I put together the full skill file plus a playbook walking through the exact setup and 5 real questions to ask your brand brain. Want it for free? > Like this post > Comment "BRAIN" And I'll send it over (must be following so I can DM)

Mike Futia

15,257 görüntüleme • 6 ay önce

Still baffled as to why people are sleeping on this. Implementing this strategy is what allowed me to bump my monthly earnings to $13,000 a year ago A simple concept shared by OpenAI co-founder Andrej Karpathy recently exploded to 21 million views. Stop treating AI as just a coding tool and start using it to construct your personal second brain The workflow is seamless. Direct Claude Code to a designated directory, drop in any raw material like a PDF, transcript, or article, and let Claude parse, connect, and integrate it into a dynamic personal wiki. It compounds over time, meaning the system grows sharper the more information you feed it The quick setup guide: Download Obsidian, spin up a new vault, and open it up in Claude Code Feed Claude the document outlining Karpathy's wiki framework and tell it to initialize the system The AI will automatically structure three core folders: raw for source uploads, wiki for your interconnected pages, and CLAUDE to manage the engine Drop new materials into raw and give the command: "ingest this" Search and query your entire accumulated database whenever you want Total setup time is about five minutes, and you will never stare at an empty prompt window again The full walkthrough is linked below. Hit bookmark so you don't lose it
0:24

Still baffled as to why people are sleeping on this. Implementing this strategy is what allowed me to bump my monthly earnings to $13,000 a year ago A simple concept shared by OpenAI co-founder Andrej Karpathy recently exploded to 21 million views. Stop treating AI as just a coding tool and start using it to construct your personal second brain The workflow is seamless. Direct Claude Code to a designated directory, drop in any raw material like a PDF, transcript, or article, and let Claude parse, connect, and integrate it into a dynamic personal wiki. It compounds over time, meaning the system grows sharper the more information you feed it The quick setup guide: Download Obsidian, spin up a new vault, and open it up in Claude Code Feed Claude the document outlining Karpathy's wiki framework and tell it to initialize the system The AI will automatically structure three core folders: raw for source uploads, wiki for your interconnected pages, and CLAUDE to manage the engine Drop new materials into raw and give the command: "ingest this" Search and query your entire accumulated database whenever you want Total setup time is about five minutes, and you will never stare at an empty prompt window again The full walkthrough is linked below. Hit bookmark so you don't lose it

Bober_smart

23,803 görüntüleme • 1 ay önce

THIS GUY BUILT A BUSINESS SECOND BRAIN WITH CLAUDE CODE + OBSIDIAN IN 3 STEPS Most teams do not need another Notion workspace. They need a place where the company can remember how it works. The video shows a simple setup: 1. Create one empty folder called second brain. 2. Split it into 3 buckets: raw new knowledge wiki 3. Let Claude Code turn messy company material into connected notes. The useful part is the separation. Raw is where your existing stuff goes: SOPs, sales docs, process notes, client delivery checklists, old Loom summaries, onboarding docs. New knowledge is where fresh outside material lands: articles, clips, tactics, examples, market notes. Wiki is the cleaned version: concepts, roles, processes, SOPs, gaps, reusable decisions. That is where Claude Code becomes more useful than a normal chat window. Instead of asking it to remember random context forever, you give it a folder it can read, edit, and reorganize. Then Obsidian becomes the human interface. The Obsidian Web Clipper captures useful pages into the vault. Claude Code ingests them. The wiki gets updated. Then you can ask questions like: “Does my current workflow actually hold up?” That is the real point. Not “AI notes.” A business memory system that can compare what you do today against new information tomorrow. The caveat: this is not magic company intelligence. If your raw docs are vague, outdated, or full of tribal knowledge, Claude will organize weak inputs into cleaner weak outputs. You still need naming rules, review habits, and someone responsible for deleting junk. But the setup is refreshingly practical. Folder first. Clipper second. Claude Code as the maintainer. No giant knowledge base migration. No complex setup. Just a local vault that can slowly turn scattered business memory into something searchable, editable, and actually reusable.
1:25

THIS GUY BUILT A BUSINESS SECOND BRAIN WITH CLAUDE CODE + OBSIDIAN IN 3 STEPS Most teams do not need another Notion workspace. They need a place where the company can remember how it works. The video shows a simple setup: 1. Create one empty folder called second brain. 2. Split it into 3 buckets: raw new knowledge wiki 3. Let Claude Code turn messy company material into connected notes. The useful part is the separation. Raw is where your existing stuff goes: SOPs, sales docs, process notes, client delivery checklists, old Loom summaries, onboarding docs. New knowledge is where fresh outside material lands: articles, clips, tactics, examples, market notes. Wiki is the cleaned version: concepts, roles, processes, SOPs, gaps, reusable decisions. That is where Claude Code becomes more useful than a normal chat window. Instead of asking it to remember random context forever, you give it a folder it can read, edit, and reorganize. Then Obsidian becomes the human interface. The Obsidian Web Clipper captures useful pages into the vault. Claude Code ingests them. The wiki gets updated. Then you can ask questions like: “Does my current workflow actually hold up?” That is the real point. Not “AI notes.” A business memory system that can compare what you do today against new information tomorrow. The caveat: this is not magic company intelligence. If your raw docs are vague, outdated, or full of tribal knowledge, Claude will organize weak inputs into cleaner weak outputs. You still need naming rules, review habits, and someone responsible for deleting junk. But the setup is refreshingly practical. Folder first. Clipper second. Claude Code as the maintainer. No giant knowledge base migration. No complex setup. Just a local vault that can slowly turn scattered business memory into something searchable, editable, and actually reusable.

kocer

16,698 görüntüleme • 3 ay önce