Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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...

rohit4verse's profile picture

Rohit

23,545 subscribers

30,710 görüntüleme • 2 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

ANTHROPIC KILLED THE VECTOR DATABASE AND REPLACED IT WITH A FOLDER no embeddings. no black-box retrieval. no special memory tools. the agent just reads and writes a folder the insight: your agent already knows how to use a filesystem. so Anthropic made long-term memory a directory of small markdown files, mounted straight into the agent's sandbox at /mnt/memory the agent manages it with the tools it already has, bash, read, write, edit, grep, and Anthropic auto-injects a note into the system prompt so the agent always knows the memory is there and where to look the result: > every change is an immutable version: full audit trail, point-in-time recovery, redaction > read-only or read-write per store, so many agents can safely share one memory > workspace-scoped and persistent, memory that survives every session end most teams bolt on a vector DB and pray retrieval works. Anthropic went the opposite way: compiled knowledge as plain, human-readable files you can open, diff, and edit yourself and there's a second layer. Anthropic's "Dreaming" runs offline, reviews past sessions and the store, and rewrites it into a cleaner, higher-signal version. the agent literally consolidates memory in its sleep. bookmark this. the most production-grade agent memory right now is just a well-organized folder, and Anthropic proved it.
0:50

ANTHROPIC KILLED THE VECTOR DATABASE AND REPLACED IT WITH A FOLDER no embeddings. no black-box retrieval. no special memory tools. the agent just reads and writes a folder the insight: your agent already knows how to use a filesystem. so Anthropic made long-term memory a directory of small markdown files, mounted straight into the agent's sandbox at /mnt/memory the agent manages it with the tools it already has, bash, read, write, edit, grep, and Anthropic auto-injects a note into the system prompt so the agent always knows the memory is there and where to look the result: > every change is an immutable version: full audit trail, point-in-time recovery, redaction > read-only or read-write per store, so many agents can safely share one memory > workspace-scoped and persistent, memory that survives every session end most teams bolt on a vector DB and pray retrieval works. Anthropic went the opposite way: compiled knowledge as plain, human-readable files you can open, diff, and edit yourself and there's a second layer. Anthropic's "Dreaming" runs offline, reviews past sessions and the store, and rewrites it into a cleaner, higher-signal version. the agent literally consolidates memory in its sleep. bookmark this. the most production-grade agent memory right now is just a well-organized folder, and Anthropic proved it.

NO1ennn

13,359 görüntüleme • 17 gün önce

Karpathy found a way to reduce token consumption by 90% The problem is that the LLM re-reads the same files over and over again, loses context between documents, and provides less accurate answers as a result The solution is called Wiki Layer the LLM cleans, structures, and links all your data once, after which it never works with raw files again Three folders `raw/` for originals, `wiki/` for a clean knowledge base in Markdown, and files with rules for the agent Result up to 90% token savings on repeat queries, automatic links between documents, and a visual knowledge graph in Obsidian Everything stays on your local machine nothing goes to the cloud
0:32

Karpathy found a way to reduce token consumption by 90% The problem is that the LLM re-reads the same files over and over again, loses context between documents, and provides less accurate answers as a result The solution is called Wiki Layer the LLM cleans, structures, and links all your data once, after which it never works with raw files again Three folders `raw/` for originals, `wiki/` for a clean knowledge base in Markdown, and files with rules for the agent Result up to 90% token savings on repeat queries, automatic links between documents, and a visual knowledge graph in Obsidian Everything stays on your local machine nothing goes to the cloud

Asteri

1,096,350 görüntüleme • 2 ay önce

Markdown is the new programming language. But writing markdown sucks. So I created a beautiful app to write and edit markdown files with agents, locally. It's called Skribe, an open-source, beautiful markdown editor and you can try it for free today. Just: - Open your codebase - Only markdown files are shown - Edit and write markdown alongside Claude Code or Codex within a beautiful editor
1:05

Markdown is the new programming language. But writing markdown sucks. So I created a beautiful app to write and edit markdown files with agents, locally. It's called Skribe, an open-source, beautiful markdown editor and you can try it for free today. Just: - Open your codebase - Only markdown files are shown - Edit and write markdown alongside Claude Code or Codex within a beautiful editor

Chris Ashby

11,258 görüntüleme • 2 ay önce

A deleted page leaves a world that looks complete. The thing becomes something that was never written, and you become someone who never read it. Memory lives in the record, and the record sits on machines owned by strangers. Whoever holds the machines holds what happened. A society builds its idea of itself out of what happened, then writes its laws from that idea. The people who administer those machines are editing reality, because there is no other reality available to a species that thinks in records. What you call the past is a rendering, and someone else owns the engine. Treat every settled fact as a claim with a source you have not checked. Notice when you believe something because you saw it once rather than because you kept it. A man who remembers where his knowledge came from is harder to govern.
1:02

A deleted page leaves a world that looks complete. The thing becomes something that was never written, and you become someone who never read it. Memory lives in the record, and the record sits on machines owned by strangers. Whoever holds the machines holds what happened. A society builds its idea of itself out of what happened, then writes its laws from that idea. The people who administer those machines are editing reality, because there is no other reality available to a species that thinks in records. What you call the past is a rendering, and someone else owns the engine. Treat every settled fact as a claim with a source you have not checked. Notice when you believe something because you saw it once rather than because you kept it. A man who remembers where his knowledge came from is harder to govern.

Dylan Allman

15,438 görüntüleme • 24 gün önce

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this
0:24

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,186 görüntüleme • 2 ay önce

My agent is now paying for its own data. No API key. No account. No credit card. Check the video I recorded. This uses the x402 open protocol built by Coinbase, along with a simple skill. This is an open protocol governed by the Linux Foundation. To complete a goal, an agent can now search for an actor on the Apify Store, pay for it, and use it without any human intervention. The way it works is pretty simple: 1. Your agent finds an Actor it wants to use 2. It sends a request 3. The Actor sends back an HTTP 402 "Payment Required" response 4. Agent authorizes payment from a wallet in USDC on Base 5. The Actor runs 6. User receives the result The model is pay-as-you-go: the agent authorizes a spending ceiling, pays only for usage, and the remaining balance is automatically settled. This brings an entire marketplace of AI tools into the agentic economy. Here is the skill you need. Add it to your agent, and it will take care of everything for you: If you want to know how this works, including what you can do with $1, read this post: Thanks to the Apify team for partnering with me on this post.
5:56

My agent is now paying for its own data. No API key. No account. No credit card. Check the video I recorded. This uses the x402 open protocol built by Coinbase, along with a simple skill. This is an open protocol governed by the Linux Foundation. To complete a goal, an agent can now search for an actor on the Apify Store, pay for it, and use it without any human intervention. The way it works is pretty simple: 1. Your agent finds an Actor it wants to use 2. It sends a request 3. The Actor sends back an HTTP 402 "Payment Required" response 4. Agent authorizes payment from a wallet in USDC on Base 5. The Actor runs 6. User receives the result The model is pay-as-you-go: the agent authorizes a spending ceiling, pays only for usage, and the remaining balance is automatically settled. This brings an entire marketplace of AI tools into the agentic economy. Here is the skill you need. Add it to your agent, and it will take care of everything for you: If you want to know how this works, including what you can do with $1, read this post: Thanks to the Apify team for partnering with me on this post.

Santiago

26,865 görüntüleme • 1 ay ö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 • 2 ay önce

ANTHROPIC LEAKED A 5-AGENT SETUP THAT TURNS ONE QUESTION INTO A SOURCED REPORT you write one line and never open a tab - the fleet reads 40 sources and only the answer comes back. question → scope → 5 searchers → dedupe → writer → fact-check → report the scope agent turns a vague question into 5 angles that do not overlap - skip this and five agents fetch the same three articles. 5 searchers run in parallel with separate contexts - none of them sees what the others found, which is exactly why they do not converge on the same source. dedupe is code, not an agent - flatten, drop repeats, normalize URLs, zero tokens, instant. the writer only sees structured findings, never raw pages - it cannot cite something that was never verified because it never had access to it. the fact-checker reads the draft against the sources, not against itself - every claim without a matching source goes back, and only that section is rewritten. nothing reaches you until a second agent, with clean context, has tried to kill it. 12 minutes, 40 sources, one report where every line traces back to something real. save this and read the full graph engineering course below ↓
0:49

ANTHROPIC LEAKED A 5-AGENT SETUP THAT TURNS ONE QUESTION INTO A SOURCED REPORT you write one line and never open a tab - the fleet reads 40 sources and only the answer comes back. question → scope → 5 searchers → dedupe → writer → fact-check → report the scope agent turns a vague question into 5 angles that do not overlap - skip this and five agents fetch the same three articles. 5 searchers run in parallel with separate contexts - none of them sees what the others found, which is exactly why they do not converge on the same source. dedupe is code, not an agent - flatten, drop repeats, normalize URLs, zero tokens, instant. the writer only sees structured findings, never raw pages - it cannot cite something that was never verified because it never had access to it. the fact-checker reads the draft against the sources, not against itself - every claim without a matching source goes back, and only that section is rewritten. nothing reaches you until a second agent, with clean context, has tried to kill it. 12 minutes, 40 sources, one report where every line traces back to something real. save this and read the full graph engineering course below ↓

Hanako

58,439 görüntüleme • 11 gün önce

This Obsidian and Claude architecture charges nothing and removes the maintenance entirely. Obsidian stores everything as plain Markdown files. Claude Code points at the vault directory. No API integrations. No paid connectors. No configuration beyond a folder path. The gap between project management systems that get abandoned the moment life gets busy and a system that maintains itself from the notes you were already writing is not discipline or organizational skill. It is the architecture described in this article, and the afternoon it takes to build five markdown components that never need a status update meeting again.
0:27

This Obsidian and Claude architecture charges nothing and removes the maintenance entirely. Obsidian stores everything as plain Markdown files. Claude Code points at the vault directory. No API integrations. No paid connectors. No configuration beyond a folder path. The gap between project management systems that get abandoned the moment life gets busy and a system that maintains itself from the notes you were already writing is not discipline or organizational skill. It is the architecture described in this article, and the afternoon it takes to build five markdown components that never need a status update meeting again.

NeilXbt

32,130 görüntüleme • 2 ay önce

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 is why a good answer should not die in chat history If the model gives you a useful comparison, summary, decision, bug explanation, or research thread, file it back into the project Use: > `wiki/topics/[topic].md` > `wiki/entities/[person-or-company].md` > `wiki/sources/[source-name].md` > `wiki/analysis/[question].md` Make the agent keep the wiki from rotting: > backlinks > summaries > contradictions > stale claims > orphan pages > missing source links For coding projects, same idea: > `CLAUDE.md`: who you are, project rules, files not to touch > `index.md`: current files and features > `log.md`: date, change, reason > saved pages: decisions you do not want to re-explain Start by saving one good answer today
11:03

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 is why a good answer should not die in chat history If the model gives you a useful comparison, summary, decision, bug explanation, or research thread, file it back into the project Use: > `wiki/topics/[topic].md` > `wiki/entities/[person-or-company].md` > `wiki/sources/[source-name].md` > `wiki/analysis/[question].md` Make the agent keep the wiki from rotting: > backlinks > summaries > contradictions > stale claims > orphan pages > missing source links For coding projects, same idea: > `CLAUDE.md`: who you are, project rules, files not to touch > `index.md`: current files and features > `log.md`: date, change, reason > saved pages: decisions you do not want to re-explain Start by saving one good answer today

Alpha Batcher

14,041 görüntüleme • 2 ay önce

"The model is no longer the product. Codex, Perplexity Computer, or Claude Code - all are orchestration system. It takes a model and pairs it with an agent harness. What is an agent harness ? The rules for how the agent loops around" - Aravind Srinivas
3:27

"The model is no longer the product. Codex, Perplexity Computer, or Claude Code - all are orchestration system. It takes a model and pairs it with an agent harness. What is an agent harness ? The rules for how the agent loops around" - Aravind Srinivas

Rohan Paul

120,488 görüntüleme • 2 ay önce

A DEVELOPER PROVED YOU CAN FIND THE EXACT COMMIT THAT BROKE YOUR CODE IN A HISTORY OF 10,000 -- IN ABOUT 13 STEPS, AUTOMATICALLY.. 33 minutes from a Google engineer on git bisect: the built-in command that binary-searches your entire history to hunt down the one commit that introduced a bug. -> The moment it lands, "When did this break?" stops being an afternoon of guessing. You hand git a good commit, a bad one, and a test and it finds the culprit while you watch. Most people debug a regression by reading diffs by hand, blaming the obvious file, and hoping. Bisect doesn't hope. It cuts the search in half, then in half again, until only the guilty commit is left standing. Reading history by hand was never the skill -> letting git do the binary search for you is. And when an AI agent dumps hundreds of commits into your repo and one quietly breaks production, bisect is what finds the needle without you reading a single line. The bug isn't hiding. It's sitting in one exact commit. Most people just never learned to make git point at it. Bookmark & Watch it today ↓
32:07

A DEVELOPER PROVED YOU CAN FIND THE EXACT COMMIT THAT BROKE YOUR CODE IN A HISTORY OF 10,000 -- IN ABOUT 13 STEPS, AUTOMATICALLY.. 33 minutes from a Google engineer on git bisect: the built-in command that binary-searches your entire history to hunt down the one commit that introduced a bug. -> The moment it lands, "When did this break?" stops being an afternoon of guessing. You hand git a good commit, a bad one, and a test and it finds the culprit while you watch. Most people debug a regression by reading diffs by hand, blaming the obvious file, and hoping. Bisect doesn't hope. It cuts the search in half, then in half again, until only the guilty commit is left standing. Reading history by hand was never the skill -> letting git do the binary search for you is. And when an AI agent dumps hundreds of commits into your repo and one quietly breaks production, bisect is what finds the needle without you reading a single line. The bug isn't hiding. It's sitting in one exact commit. Most people just never learned to make git point at it. Bookmark & Watch it today ↓

slash1s

37,773 görüntüleme • 2 ay önce

You can spin up an AI workforce with one prompt. Here's why it works: it pulls the context the AI needs to lay the foundation. Give it: - your role - team size - the goals you want to hit. Then say "interview me." After that, build it out in four steps: 1) Start with 1 agent. - What does it feel like to work with one? 2) Make that agent proactive. - Now it's doing things on your behalf before you ask. 3) Expand to 2 agents. - One directs the other, or routes to it. - This is where you learn how context gets passed. 4) Scale the workforce. - A mission control where you watch it all move around. - Now you see what has to run in parallel, which agent never needed that tool, which one runs fine on a smaller model. - Not everything needs Opus. Sub-agents are haiku and sonnet. The catch: the prompt gets you agents with markdown files doing some stuff. Getting to the 90% plus level is iteration, and that part is specific to each person. Nobody can hand it to you. Start with one agent. Spin up one agent this week. The rest is discovery.
3:10

You can spin up an AI workforce with one prompt. Here's why it works: it pulls the context the AI needs to lay the foundation. Give it: - your role - team size - the goals you want to hit. Then say "interview me." After that, build it out in four steps: 1) Start with 1 agent. - What does it feel like to work with one? 2) Make that agent proactive. - Now it's doing things on your behalf before you ask. 3) Expand to 2 agents. - One directs the other, or routes to it. - This is where you learn how context gets passed. 4) Scale the workforce. - A mission control where you watch it all move around. - Now you see what has to run in parallel, which agent never needed that tool, which one runs fine on a smaller model. - Not everything needs Opus. Sub-agents are haiku and sonnet. The catch: the prompt gets you agents with markdown files doing some stuff. Getting to the 90% plus level is iteration, and that part is specific to each person. Nobody can hand it to you. Start with one agent. Spin up one agent this week. The rest is discovery.

The Startup Ideas Podcast (SIP) 🧃

18,006 görüntüleme • 12 gün önce

Agents can one shot mobile apps, but testing is still the bottleneck. So we built a CLI that gives Claude Code the one thing it was missing - eyes and hands The best part? t's fully vision-based: - No scripts, no selectors, no element IDs - It interacts with the app exactly like a human would Claude now writes code → tests it on the app → sees what broke → fixes it Spawn a cloud agent, go to sleep, and wake up knowing it actually worked.
0:38

Agents can one shot mobile apps, but testing is still the bottleneck. So we built a CLI that gives Claude Code the one thing it was missing - eyes and hands The best part? t's fully vision-based: - No scripts, no selectors, no element IDs - It interacts with the app exactly like a human would Claude now writes code → tests it on the app → sees what broke → fixes it Spawn a cloud agent, go to sleep, and wake up knowing it actually worked.

Landseer Enga

86,958 görüntüleme • 6 ay önce

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this
13:23

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

56,177 görüntüleme • 2 ay önce

This is one of the coolest open-source AI agent projects I've seen in a while: 'Understand Anything' It's a plugin for Claude Code, Codex, OpenCode etc. that analyzes your codebase and turns it into a knowledge base that you can interact with. It explains the codebase to you, rather than showing you the structure. It seems like it's designed for code but I opened my Obsidian vault of podcast highlights in Claude Code, then ran /understand. The result is a knowledge graph that I can search of highlights from 888 podcast episodes and 144K lines of markdown text.
0:22

This is one of the coolest open-source AI agent projects I've seen in a while: 'Understand Anything' It's a plugin for Claude Code, Codex, OpenCode etc. that analyzes your codebase and turns it into a knowledge base that you can interact with. It explains the codebase to you, rather than showing you the structure. It seems like it's designed for code but I opened my Obsidian vault of podcast highlights in Claude Code, then ran /understand. The result is a knowledge graph that I can search of highlights from 888 podcast episodes and 144K lines of markdown text.

Dan McAteer

174,505 görüntüleme • 2 ay önce

i keep telling people to build this and they nod politely and never do it... andrej karpathy posted how to fix this a while ago, and everyone just keeps working the old way the dumb thing is this... you pay to teach claude the same lessons over and over, every chat is a fresh amnesia patient, every contradiction it catches evaporates the second you close the tab, and you accept this like it's just how ai works 1. one folder is a graveyard for originals that nobody edits, another folder is claude's active memory that only claude writes to, a third folder is a two-page rulebook that keeps claude from confusing them 2. a raw file gets read the day it arrives and then it's done, claude never touches it again, everything it needed is already extracted into wiki pages with the source cited right there 3. every time claude notices your new answer clashes with your old one, it doesn't pick a side, it writes both with dates, and from then on it treats you like someone who might be wrong the raw folder is a museum... the wiki is the actual working brain full breakdown is in the article below
0:20

i keep telling people to build this and they nod politely and never do it... andrej karpathy posted how to fix this a while ago, and everyone just keeps working the old way the dumb thing is this... you pay to teach claude the same lessons over and over, every chat is a fresh amnesia patient, every contradiction it catches evaporates the second you close the tab, and you accept this like it's just how ai works 1. one folder is a graveyard for originals that nobody edits, another folder is claude's active memory that only claude writes to, a third folder is a two-page rulebook that keeps claude from confusing them 2. a raw file gets read the day it arrives and then it's done, claude never touches it again, everything it needed is already extracted into wiki pages with the source cited right there 3. every time claude notices your new answer clashes with your old one, it doesn't pick a side, it writes both with dates, and from then on it treats you like someone who might be wrong the raw folder is a museum... the wiki is the actual working brain full breakdown is in the article below

kai

32,120 görüntüleme • 24 gün önce

A guy in China plugged an LLM into Karpathy method + Claude Code and built a second brain that remembers everything forever. Not a note app, not RAG just 3 folders on a laptop. Folder 1 holds raw sources: articles, journal entries, chat logs. The LLM reads them but never touches them. Folder 2 is the wiki hundreds of markdown pages the LLM writes and maintains itself, where every person, idea and decision gets filed, cross-referenced and kept current. Folder 3 is one file: CLAUDEmd, the rulebook that turns a chatbot into a librarian. He drops in a new article and Claude reads it, updates 10-15 pages, flags what contradicts his old notes, logs the timestamp while he watches his memory grow node by node in Obsidian graph view. Ask it anything and it doesn’t dig through raw files like ChatGPT does the synthesis already exists, the connections are already drawn. The method comes from a gist Karpathy posted on April 4, now sitting at 5,000 stars and 5,000 forks, with 1 production team already scaled to 4,000 interlinked concepts in 6 months. The part nobody mentions: Vannevar Bush described this exact machine in 1945 the Memex, a personal memory store with trails between documents. Nobody built it for 81 years because someone had to do the maintenance. Now maintenance costs nothing the LLM does the filing while the human does the thinking. Every article makes the brain smarter, and it never forgets. His memory has a git history now.
0:28

A guy in China plugged an LLM into Karpathy method + Claude Code and built a second brain that remembers everything forever. Not a note app, not RAG just 3 folders on a laptop. Folder 1 holds raw sources: articles, journal entries, chat logs. The LLM reads them but never touches them. Folder 2 is the wiki hundreds of markdown pages the LLM writes and maintains itself, where every person, idea and decision gets filed, cross-referenced and kept current. Folder 3 is one file: CLAUDEmd, the rulebook that turns a chatbot into a librarian. He drops in a new article and Claude reads it, updates 10-15 pages, flags what contradicts his old notes, logs the timestamp while he watches his memory grow node by node in Obsidian graph view. Ask it anything and it doesn’t dig through raw files like ChatGPT does the synthesis already exists, the connections are already drawn. The method comes from a gist Karpathy posted on April 4, now sitting at 5,000 stars and 5,000 forks, with 1 production team already scaled to 4,000 interlinked concepts in 6 months. The part nobody mentions: Vannevar Bush described this exact machine in 1945 the Memex, a personal memory store with trails between documents. Nobody built it for 81 years because someone had to do the maintenance. Now maintenance costs nothing the LLM does the filing while the human does the thinking. Every article makes the brain smarter, and it never forgets. His memory has a git history now.

West Lord

61,701 görüntüleme • 1 ay önce

Most AI tools today are just command-takers. You type, it responds. You click, it executes. There's truly no learning, no memory, no adaptation. You're still doing most of the work. Which is why Miles by Avo on Solana would make so much sense if built well. From what I understand so far, miles learns about you over time, adapts to how you operate, and figures out the tools you struggle to navigate on your own. Less clicking, more conversation, the more you use it, the better it gets at working with you, not just for you. That shift from command-follower to learning companion is bigger than it sounds. It's the difference between a tool and an agent that actually knows you. The second one is Agent Grid and this one is for builders and power users. But as I mentioned in this video, I'm still studying the Agent Grid. I'd come talk about it once I learn properly about it. Souren just keeps shipping!
1:28

Most AI tools today are just command-takers. You type, it responds. You click, it executes. There's truly no learning, no memory, no adaptation. You're still doing most of the work. Which is why Miles by Avo on Solana would make so much sense if built well. From what I understand so far, miles learns about you over time, adapts to how you operate, and figures out the tools you struggle to navigate on your own. Less clicking, more conversation, the more you use it, the better it gets at working with you, not just for you. That shift from command-follower to learning companion is bigger than it sounds. It's the difference between a tool and an agent that actually knows you. The second one is Agent Grid and this one is for builders and power users. But as I mentioned in this video, I'm still studying the Agent Grid. I'd come talk about it once I learn properly about it. Souren just keeps shipping!

Sir Khaycee

20,419 görüntüleme • 5 ay önce

Jeff Bezos looked at a government waiting room and priced it at a hundred billion dollars. Bezos: “This is a $100 billion business, by the way. This is huge business.” That number is not ambition. It is a measurement. A company that size does not create a hundred billion dollars of new value here. It recovers a hundred billion that is already being destroyed, on schedule, in public, by a process everyone has agreed to call normal. The size of the opportunity is the size of the wound. Bezos: “They almost always say yes, they just make you wait a long time.” So the verdict was never in question. Only the delivery date. Which means the months bought nothing. They were storage. Your project sat in a room while the word yes waited its turn to be said. Nobody in there was deciding. Someone was scheduling. And the room bills by the day. Suarez: “The daily carrying cost, one day of interest, 200 to $400,000 per day.” Now find the recipient. There isn’t one. No school funded, no inspector paid, no safety review performed. A tax at least moves money into someone’s hands. This deletes it at four hundred thousand a day, and every dollar was real before the queue touched it. Bezos: “And that doesn’t count the frustration.” Count it anyway. It lands on a body long before it lands on a spreadsheet. Suarez: “Which is infinite. I have some white hairs as a result of this stuff.” That is the invoice. The money has a rate. The rest gets charged to the man, and he pays it whether the answer comes back yes or no. No one has ever been refunded a year. Every other cost in this economy can be hedged, insured, refinanced, or written off. Waiting is the only one that is final. A man will forgive being told no. He will never get back the time he spent standing there waiting to be told yes. We built a civilization that can move a decision at the speed of light and still schedule it at the speed of a man’s hair turning white. Bezos: “It should give you a yes or a no in 10 seconds. And if the answer is no, it should tell you the 6 things you have to change to get a yes.” For four thousand years the wait was honest. Someone had to hold the entire code in one head and walk it line by line against your drawings. Reading was slow because reading was human. That stopped being true in less time than it takes to approve one building. Bezos: “Maybe with AI it can just read all the plans. And it knows all the codes. Spit it out.” The constraint is gone. The wait stayed. Anything still moving at the old speed after the cost of thinking collapsed is not slow. It is choosing. The queue never protected you from a bad building. It protected a signature from a bad outcome. Nobody gets fired for the wait. They get fired for the answer. An institution has no lifespan, so time costs it nothing. You have one, so time is the only thing it can take. Every queue is a trade between something that dies and something that doesn’t, and only one side is ever charged. That trade held for the whole of recorded history because the mortal side had no leverage. It does now. Somebody is going to build this. A hundred billion does not sit in a waiting room forever. And the day it exists, the wait stops being a fact of the world and becomes a decision with a name attached. The hundred billion was never the prize. It is the receipt for how long we agreed to stand there. We are the first people alive who get to stop signing it.
1:55

Jeff Bezos looked at a government waiting room and priced it at a hundred billion dollars. Bezos: “This is a $100 billion business, by the way. This is huge business.” That number is not ambition. It is a measurement. A company that size does not create a hundred billion dollars of new value here. It recovers a hundred billion that is already being destroyed, on schedule, in public, by a process everyone has agreed to call normal. The size of the opportunity is the size of the wound. Bezos: “They almost always say yes, they just make you wait a long time.” So the verdict was never in question. Only the delivery date. Which means the months bought nothing. They were storage. Your project sat in a room while the word yes waited its turn to be said. Nobody in there was deciding. Someone was scheduling. And the room bills by the day. Suarez: “The daily carrying cost, one day of interest, 200 to $400,000 per day.” Now find the recipient. There isn’t one. No school funded, no inspector paid, no safety review performed. A tax at least moves money into someone’s hands. This deletes it at four hundred thousand a day, and every dollar was real before the queue touched it. Bezos: “And that doesn’t count the frustration.” Count it anyway. It lands on a body long before it lands on a spreadsheet. Suarez: “Which is infinite. I have some white hairs as a result of this stuff.” That is the invoice. The money has a rate. The rest gets charged to the man, and he pays it whether the answer comes back yes or no. No one has ever been refunded a year. Every other cost in this economy can be hedged, insured, refinanced, or written off. Waiting is the only one that is final. A man will forgive being told no. He will never get back the time he spent standing there waiting to be told yes. We built a civilization that can move a decision at the speed of light and still schedule it at the speed of a man’s hair turning white. Bezos: “It should give you a yes or a no in 10 seconds. And if the answer is no, it should tell you the 6 things you have to change to get a yes.” For four thousand years the wait was honest. Someone had to hold the entire code in one head and walk it line by line against your drawings. Reading was slow because reading was human. That stopped being true in less time than it takes to approve one building. Bezos: “Maybe with AI it can just read all the plans. And it knows all the codes. Spit it out.” The constraint is gone. The wait stayed. Anything still moving at the old speed after the cost of thinking collapsed is not slow. It is choosing. The queue never protected you from a bad building. It protected a signature from a bad outcome. Nobody gets fired for the wait. They get fired for the answer. An institution has no lifespan, so time costs it nothing. You have one, so time is the only thing it can take. Every queue is a trade between something that dies and something that doesn’t, and only one side is ever charged. That trade held for the whole of recorded history because the mortal side had no leverage. It does now. Somebody is going to build this. A hundred billion does not sit in a waiting room forever. And the day it exists, the wait stops being a fact of the world and becomes a decision with a name attached. The hundred billion was never the prize. It is the receipt for how long we agreed to stand there. We are the first people alive who get to stop signing it.

Dustin

17,035 görüntüleme • 23 gün önce