Загрузка видео...

Не удалось загрузить видео

На главную

A FORMER GOOGLE LEAD BUILT A MEMORY SYSTEM THAT NEVER LOSES A SINGLE DETAIL Most agents forget everything the moment a session ends, starting from zero every single time. He built a scoring layer instead, one that decides what actually matters past this session and what gets dropped. Contradictions...

0xWast3's profile picture

wast3

3,211 subscribers

26,649 просмотров • 9 дней назад •via X (Twitter)

Наука и технологииОбразование
LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

New course: Agent Memory: Building Memory-Aware Agents, built in partnership with Oracle and taught by Richmond Alake and Nacho Martínez. Many agents work well within a single session but their memory resets once the session ends. Consider a research agent working on dozens of papers across multiple days: without memory, it has no way to store and retrieve what it learned across sessions. This short course teaches you to build a memory system that enables agents to persist memory and thereby learn across sessions. You'll design a Memory Manager that handles different memory types, implement semantic tool retrieval that scales without bloating the context, and build write-back pipelines that let your agent autonomously update and refine what it knows over time. Skills you'll gain: - Build persistent memory stores for different agent memory types - Implement a Memory Manager that orchestrates how your agent reads, writes, and retrieves memory - Treat tools as procedural memory and retrieve only relevant ones at inference time using semantic search Join and learn to build agents that remember and improve over time!
1:37

New course: Agent Memory: Building Memory-Aware Agents, built in partnership with Oracle and taught by Richmond Alake and Nacho Martínez. Many agents work well within a single session but their memory resets once the session ends. Consider a research agent working on dozens of papers across multiple days: without memory, it has no way to store and retrieve what it learned across sessions. This short course teaches you to build a memory system that enables agents to persist memory and thereby learn across sessions. You'll design a Memory Manager that handles different memory types, implement semantic tool retrieval that scales without bloating the context, and build write-back pipelines that let your agent autonomously update and refine what it knows over time. Skills you'll gain: - Build persistent memory stores for different agent memory types - Implement a Memory Manager that orchestrates how your agent reads, writes, and retrieves memory - Treat tools as procedural memory and retrieve only relevant ones at inference time using semantic search Join and learn to build agents that remember and improve over time!

Andrew Ng

160,148 просмотров • 4 месяцев назад

This 1-min clip from the creator of LangChain + this 10-min read from him will teach you more about what actually matters in AI agents than everything you've scrolled past this year. Watch this. Then read below. You'll think about agents differently after. -Memory defines how an agent behaves; same conversation, different compaction rules, different agent. - There's no version control for memory. No diffs, no reverts, no way to see what changed. - Compaction can silently erase parts of your agent's personality mid-session without anyone noticing. - "Open memory" means exportable state and inspectable compaction, not a vector database. - The storage layer is solved and boring; the memory contract above it is what actually matters. Give this 11 minutes this weekend . It'll change how you build.
1:13

This 1-min clip from the creator of LangChain + this 10-min read from him will teach you more about what actually matters in AI agents than everything you've scrolled past this year. Watch this. Then read below. You'll think about agents differently after. -Memory defines how an agent behaves; same conversation, different compaction rules, different agent. - There's no version control for memory. No diffs, no reverts, no way to see what changed. - Compaction can silently erase parts of your agent's personality mid-session without anyone noticing. - "Open memory" means exportable state and inspectable compaction, not a vector database. - The storage layer is solved and boring; the memory contract above it is what actually matters. Give this 11 minutes this weekend . It'll change how you build.

Avid

16,898 просмотров • 4 месяцев назад

Anthropic engineer just dropped a full walkthrough on building AI agents from scratch this single video is worth more than any $600 AI agents course here's what she covers: > what Agent, Environment, and Session actually mean > how to stream live events from your agent > wiring up custom tools from scratch > the server-side loop that makes agents actually work > roadmap to subagents, vaults, and memory 37 minutes that will answer every question you have about building agents the people who understand what Claude can actually do are building things everyone else thinks requires a whole team most of them aren't smarter, they just know features that most people have never heard of full breakdown on every Claude feature worth knowing in the article below
36:49

Anthropic engineer just dropped a full walkthrough on building AI agents from scratch this single video is worth more than any $600 AI agents course here's what she covers: > what Agent, Environment, and Session actually mean > how to stream live events from your agent > wiring up custom tools from scratch > the server-side loop that makes agents actually work > roadmap to subagents, vaults, and memory 37 minutes that will answer every question you have about building agents the people who understand what Claude can actually do are building things everyone else thinks requires a whole team most of them aren't smarter, they just know features that most people have never heard of full breakdown on every Claude feature worth knowing in the article below

Anatoli Kopadze

38,627 просмотров • 2 месяцев назад

Holy shit... One month before Andrej Karpathy dropped the “LLM Wiki” idea… someone had already built it. Not theory. Not hype. A working system. LLMs today restart from zero every time. No memory. No evolution. No learning. That’s broken. Most people use CLAUDE.md / AGENTS.md → Manual updates → Easy to forget → Knowledge gets lost That’s not intelligence. That’s a notepad. So I built dynamic memory for LLMs: • Learns automatically • Stores without manual effort • Weakens irrelevant data over time • Strengthens what actually matters Before the “LLM Wiki” idea went viral, this already had: • Brain-like decay/boost memory • Smart deduplication (no noise) • Experience tracking per tech • Cross-referenced knowledge graph • Loss-proof backups • Auto-grouped tool sessions Then I added: • memory_audit (clean + optimize memory) • Memory injection directly into tools Now this isn’t just a concept. It’s a live system that turns LLMs from stateless tools → evolving intelligence. Using it daily: → ~5K tokens → Zero manual work → Memory that actually compounds Link in comments. RT & Bookmark — this will be standard soon.
0:32

Holy shit... One month before Andrej Karpathy dropped the “LLM Wiki” idea… someone had already built it. Not theory. Not hype. A working system. LLMs today restart from zero every time. No memory. No evolution. No learning. That’s broken. Most people use CLAUDE.md / AGENTS.md → Manual updates → Easy to forget → Knowledge gets lost That’s not intelligence. That’s a notepad. So I built dynamic memory for LLMs: • Learns automatically • Stores without manual effort • Weakens irrelevant data over time • Strengthens what actually matters Before the “LLM Wiki” idea went viral, this already had: • Brain-like decay/boost memory • Smart deduplication (no noise) • Experience tracking per tech • Cross-referenced knowledge graph • Loss-proof backups • Auto-grouped tool sessions Then I added: • memory_audit (clean + optimize memory) • Memory injection directly into tools Now this isn’t just a concept. It’s a live system that turns LLMs from stateless tools → evolving intelligence. Using it daily: → ~5K tokens → Zero manual work → Memory that actually compounds Link in comments. RT & Bookmark — this will be standard soon.

Nainsi Dwivedi

15,726 просмотров • 3 месяцев назад

New short course: LLMs as Operating Systems: Agent Memory, created with Letta, and taught by its founders Charles Packer and Sarah Wooders. An LLM's input context window has limited space. Using a longer input context also costs more and results in slower processing. So, managing what's stored in this context window is important. In the innovative paper MemGPT: Towards LLMs as Operating Systems, its authors (which include the instructors) proposed using an LLM agent to manage this context window. Their system uses a large persistent memory that stores everything that could be included in the input context, and an agent decides what is actually included. Take the example of building a chatbot that needs to remember what's been said earlier in a conversation (perhaps over many days of interaction with a user). As the conversation's length grows, the memory management agent will move information from the input context to a persistent searchable database; summarize information to keep relevant facts in the input context; and restore relevant conversation elements from further back in time. This allows a chatbot to keep what's currently most relevant in its input context memory to generate the next response. When I read the original MemGPT paper, I thought it was an innovative technique for handling memory for LLMs. The open-source Letta framework, which we'll use in this course, makes MemGPT easy to implement. It adds memory to your LLM agents and gives them transparent long-term memory. In detail, you’ll learn: - How to build an agent that can edit its own limited input context memory, using tools and multi-step reasoning - What is a memory hierarchy (an idea from computer operating systems, which use a cache to speed up memory access), and how these ideas apply to managing the LLM input context (where the input context window is a "cache" storing the most relevant information; and an agent decides what to move in and out of this to/from a larger persistent storage system) - How to implement multi-agent collaboration by letting different agents share blocks of memory This course will give you a sophisticated understanding of memory management for LLMs, which is important for chatbots having long conversations, and for complex agentic workflows. Please sign up here!
2:57

New short course: LLMs as Operating Systems: Agent Memory, created with Letta, and taught by its founders Charles Packer and Sarah Wooders. An LLM's input context window has limited space. Using a longer input context also costs more and results in slower processing. So, managing what's stored in this context window is important. In the innovative paper MemGPT: Towards LLMs as Operating Systems, its authors (which include the instructors) proposed using an LLM agent to manage this context window. Their system uses a large persistent memory that stores everything that could be included in the input context, and an agent decides what is actually included. Take the example of building a chatbot that needs to remember what's been said earlier in a conversation (perhaps over many days of interaction with a user). As the conversation's length grows, the memory management agent will move information from the input context to a persistent searchable database; summarize information to keep relevant facts in the input context; and restore relevant conversation elements from further back in time. This allows a chatbot to keep what's currently most relevant in its input context memory to generate the next response. When I read the original MemGPT paper, I thought it was an innovative technique for handling memory for LLMs. The open-source Letta framework, which we'll use in this course, makes MemGPT easy to implement. It adds memory to your LLM agents and gives them transparent long-term memory. In detail, you’ll learn: - How to build an agent that can edit its own limited input context memory, using tools and multi-step reasoning - What is a memory hierarchy (an idea from computer operating systems, which use a cache to speed up memory access), and how these ideas apply to managing the LLM input context (where the input context window is a "cache" storing the most relevant information; and an agent decides what to move in and out of this to/from a larger persistent storage system) - How to implement multi-agent collaboration by letting different agents share blocks of memory This course will give you a sophisticated understanding of memory management for LLMs, which is important for chatbots having long conversations, and for complex agentic workflows. Please sign up here!

Andrew Ng

200,950 просмотров • 1 год назад

the engineer who built Claude Code just dropped a 28-minute video on how to write prompts that actually work I've seen $300 courses that don't cover what he shows in the first 10 minutes CLAUDE.md files, memory shortcuts, parallel sessions, prompting patterns all in one video and completely free after watching this, the next step is agents I wrote a full guide on how to build one yourself with Claude Code article below
27:17

the engineer who built Claude Code just dropped a 28-minute video on how to write prompts that actually work I've seen $300 courses that don't cover what he shows in the first 10 minutes CLAUDE.md files, memory shortcuts, parallel sessions, prompting patterns all in one video and completely free after watching this, the next step is agents I wrote a full guide on how to build one yourself with Claude Code article below

Anatoli Kopadze

1,289,822 просмотров • 2 месяцев назад

MICROSOFT QUIETLY BUILT ONE MEMORY MODULE THAT PLUGS INTO ANY AI AGENT AND CUTS ITS CONTEXT BY UP TO 100X no retraining. no task-specific redesign. you just plug it in Microsoft's insight: agents don't need to remember what happened. they need the knowledge pulled from it - the facts and the reusable skills, not the raw logs so PlugMem stops storing history. it compiles experience into a knowledge graph, then feeds the agent only what matters the result: > up to 1-2 orders of magnitude fewer tokens > highest decision-utility per token of any system tested > one unchanged module beats task-specific memory on chat QA, multi-hop search, and web agents more memory was never the answer. better memory is - and Microsoft just shipped it as a plug-in bookmark this. the agents that win won't remember more, they'll remember smarter.
0:42

MICROSOFT QUIETLY BUILT ONE MEMORY MODULE THAT PLUGS INTO ANY AI AGENT AND CUTS ITS CONTEXT BY UP TO 100X no retraining. no task-specific redesign. you just plug it in Microsoft's insight: agents don't need to remember what happened. they need the knowledge pulled from it - the facts and the reusable skills, not the raw logs so PlugMem stops storing history. it compiles experience into a knowledge graph, then feeds the agent only what matters the result: > up to 1-2 orders of magnitude fewer tokens > highest decision-utility per token of any system tested > one unchanged module beats task-specific memory on chat QA, multi-hop search, and web agents more memory was never the answer. better memory is - and Microsoft just shipped it as a plug-in bookmark this. the agents that win won't remember more, they'll remember smarter.

NO1ennn

225,032 просмотров • 9 дней назад

context engineering vs graph engineering. every few months the list gets a new word and everyone treats it as a replacement for the last one. these two are not on the same list. one decides what the model sees this turn, the other decides what exists at all. the cleanest way to tell them apart is to ask what a single unit of work looks like. > context engineering is the window the window opens empty, every single time. you assemble what goes in it. the prompt, the docs, the history, the tool results. the assembling is the work. the window only grows. it never shrinks on its own, so eventually something gets dropped. usually from the middle. usually without telling you. then the turn ends and the window is thrown away. not archived, thrown away. the next turn opens empty again and you re-explain what you already explained. good context engineering is knowing what to leave out, not what to pack in. the unit of work is one window. > graph engineering is the structure the same material arrives from the same sources. instead of packing it into a window, you pull entities out of it, resolve the duplicates into one node, and write typed edges between them. nothing here is stored as text you hope to find again. it is stored as a thing with a name and its connections to other things. when the turn ends, the graph is still there. the next turn does not start from zero. it starts by querying what already exists, and the query walks edges instead of guessing at similarity. good graph engineering is deciding what counts as the same thing twice. the unit of work is one relationship. > they are not alternatives the graph is what refills the window. context engineering decides what fits. graph engineering decides what there is to choose from. remove the graph and every session starts blind. remove the context work and the best structure in the world arrives as an unreadable dump. that also tells you which one broke. the answer drifted from what you actually said, or forgot something from this same session. that is the window. the answer is coherent but invents a connection that does not exist, or cannot join two facts it has clearly seen. that is the structure. people debug the prompt because the prompt is the easiest thing to edit. it keeps taking the blame for failures that live a layer down. save this - then read the full breakdown below
0:40

context engineering vs graph engineering. every few months the list gets a new word and everyone treats it as a replacement for the last one. these two are not on the same list. one decides what the model sees this turn, the other decides what exists at all. the cleanest way to tell them apart is to ask what a single unit of work looks like. > context engineering is the window the window opens empty, every single time. you assemble what goes in it. the prompt, the docs, the history, the tool results. the assembling is the work. the window only grows. it never shrinks on its own, so eventually something gets dropped. usually from the middle. usually without telling you. then the turn ends and the window is thrown away. not archived, thrown away. the next turn opens empty again and you re-explain what you already explained. good context engineering is knowing what to leave out, not what to pack in. the unit of work is one window. > graph engineering is the structure the same material arrives from the same sources. instead of packing it into a window, you pull entities out of it, resolve the duplicates into one node, and write typed edges between them. nothing here is stored as text you hope to find again. it is stored as a thing with a name and its connections to other things. when the turn ends, the graph is still there. the next turn does not start from zero. it starts by querying what already exists, and the query walks edges instead of guessing at similarity. good graph engineering is deciding what counts as the same thing twice. the unit of work is one relationship. > they are not alternatives the graph is what refills the window. context engineering decides what fits. graph engineering decides what there is to choose from. remove the graph and every session starts blind. remove the context work and the best structure in the world arrives as an unreadable dump. that also tells you which one broke. the answer drifted from what you actually said, or forgot something from this same session. that is the window. the answer is coherent but invents a connection that does not exist, or cannot join two facts it has clearly seen. that is the structure. people debug the prompt because the prompt is the easiest thing to edit. it keeps taking the blame for failures that live a layer down. save this - then read the full breakdown below

Hanako

19,160 просмотров • 16 дней назад

THIS IS ANDREJ KARPATHY'S OBSIDIAN VAULT : THE BRAIN ANTHROPIC JUST HIRED FOR MILLIONS This is every idea, every decision and every connection he's made over years of work, visualized in real time. Everything else gets lost. The pattern you noticed last March. The connection between two problems you solved a year apart. The idea that would've changed everything if you'd remembered it in the room. This system keeps all of it. Every note links to another. Every link becomes a path. Every path is a decision he can retrace in seconds while everyone else starts from zero. Thousands of nodes. Hundreds of live connections. Years of thinking that never decayed, never died in a Slack thread, never got buried in a meeting nobody remembers. The breakthroughs aren't luck. They're the system handing him back a link he made eighteen months ago and forgot he had. No team. No wiki. No standups. One person and a tool that remembers everything he can't. Most people open Obsidian and make three notes they never open again. He built an operating system for his own thinking. Anthropic just paid millions for the output - this is the machine that produced it.
22:22

THIS IS ANDREJ KARPATHY'S OBSIDIAN VAULT : THE BRAIN ANTHROPIC JUST HIRED FOR MILLIONS This is every idea, every decision and every connection he's made over years of work, visualized in real time. Everything else gets lost. The pattern you noticed last March. The connection between two problems you solved a year apart. The idea that would've changed everything if you'd remembered it in the room. This system keeps all of it. Every note links to another. Every link becomes a path. Every path is a decision he can retrace in seconds while everyone else starts from zero. Thousands of nodes. Hundreds of live connections. Years of thinking that never decayed, never died in a Slack thread, never got buried in a meeting nobody remembers. The breakthroughs aren't luck. They're the system handing him back a link he made eighteen months ago and forgot he had. No team. No wiki. No standups. One person and a tool that remembers everything he can't. Most people open Obsidian and make three notes they never open again. He built an operating system for his own thinking. Anthropic just paid millions for the output - this is the machine that produced it.

Avid

64,799 просмотров • 2 месяцев назад

ANTHROPIC LEAD ENGINEER MAKING $2.3M/YEAR JUST LEAKED A 12-PAGE DOCUMENT - AND GOT FIRED 15 MINUTES AFTER PUBLISHING most developers build loops - but almost every loop breaks in one of five ways, and each failure has a symptom visible from the outside without reading a single line of code > Blind loop - the agent waits for a human to hand it work every morning - automating execution but not discovery > Tangled loop - parallel agents share one directory and overwrite each other parallelism that destroys instead of multiplies > Nodding loop - the agent grades its own work and approves it every time a loop that has never said no to itself is broken > Amnesiac loop - results live only in the context window every morning the system wakes up with no memory of yesterday > Manual loop - no trigger a human presses the button to start it that is not a loop that is a script waiting for a person a real loop finds its own work - remembers what it did has something that can say no never lets two agents touch the same file and fires itself on a timer remove any one of the five - and the loop either breaks or never starts 12 pages that changed how I build agentic systems today
0:50

ANTHROPIC LEAD ENGINEER MAKING $2.3M/YEAR JUST LEAKED A 12-PAGE DOCUMENT - AND GOT FIRED 15 MINUTES AFTER PUBLISHING most developers build loops - but almost every loop breaks in one of five ways, and each failure has a symptom visible from the outside without reading a single line of code > Blind loop - the agent waits for a human to hand it work every morning - automating execution but not discovery > Tangled loop - parallel agents share one directory and overwrite each other parallelism that destroys instead of multiplies > Nodding loop - the agent grades its own work and approves it every time a loop that has never said no to itself is broken > Amnesiac loop - results live only in the context window every morning the system wakes up with no memory of yesterday > Manual loop - no trigger a human presses the button to start it that is not a loop that is a script waiting for a person a real loop finds its own work - remembers what it did has something that can say no never lets two agents touch the same file and fires itself on a timer remove any one of the five - and the loop either breaks or never starts 12 pages that changed how I build agentic systems today

Sprytix

153,575 просмотров • 1 месяц назад

This is the DeepSeek moment of Search? A small team of cracked engineers built a search API for AI agents that outperforms everything built with 20x the funding. AI systems are about to become the biggest users of information on Earth. They don’t need a better Google. They need a retrieval layer built for reasoning, scale, and access beyond the web. That’s what we’re building. 1/3
2:27

This is the DeepSeek moment of Search? A small team of cracked engineers built a search API for AI agents that outperforms everything built with 20x the funding. AI systems are about to become the biggest users of information on Earth. They don’t need a better Google. They need a retrieval layer built for reasoning, scale, and access beyond the web. That’s what we’re building. 1/3

Valyu

1,135,070 просмотров • 10 месяцев назад

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.
4:19

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

DegenCalls

20,124 просмотров • 1 месяц назад

THIS GUY GOT TIRED OF MANAGING AI AGENTS THROUGH TERMINALS AND DASHBOARDS SO HE BUILT THEM AN RPG WORLD 5 agents and each one has a pixel character, a station, and they actually walk around the space when enough unresolved issues pile up, the agents walk to a meeting point and hold a council session. four different models debating what to do next, not scripted. each one reads the live system state independently. in one session an agent pushed for cold outreach to close leads at 2am. another one said that's a terrible look for an autonomous system contacting strangers while the operator sleeps. they ended up pivoting to an inbound strategy that none of them originally proposed. single HTML file, node bridge, and phaser. runs on a Mac Mini. instead of reading logs and checking dashboards you just watch your little pixel agents walk around and talk to each other this is the most creative way i've seen anyone manage AI agents so far
0:32

THIS GUY GOT TIRED OF MANAGING AI AGENTS THROUGH TERMINALS AND DASHBOARDS SO HE BUILT THEM AN RPG WORLD 5 agents and each one has a pixel character, a station, and they actually walk around the space when enough unresolved issues pile up, the agents walk to a meeting point and hold a council session. four different models debating what to do next, not scripted. each one reads the live system state independently. in one session an agent pushed for cold outreach to close leads at 2am. another one said that's a terrible look for an autonomous system contacting strangers while the operator sleeps. they ended up pivoting to an inbound strategy that none of them originally proposed. single HTML file, node bridge, and phaser. runs on a Mac Mini. instead of reading logs and checking dashboards you just watch your little pixel agents walk around and talk to each other this is the most creative way i've seen anyone manage AI agents so far

Om Patel

653,793 просмотров • 4 месяцев назад

The builders on Walrus 🦭/acc never cease to amaze me. @Collective_memo is the perfect example. Last week, I sat down with Jonathan Saragossi, and I was blown away by what they are building: A social memory layer that is actually censorship resistant. Listen to this👇
0:55

The builders on Walrus 🦭/acc never cease to amaze me. @Collective_memo is the perfect example. Last week, I sat down with Jonathan Saragossi, and I was blown away by what they are building: A social memory layer that is actually censorship resistant. Listen to this👇

rebecca simmonds 🦭/acc

17,042 просмотров • 8 месяцев назад

The engineer who built Claude Code just dropped a 28-minute video on how to write prompts that actually work. I've seen $300 courses that don't cover what he shows in the first 10 minutes. CLAUDE.md files, memory shortcuts, parallel sessions, prompting patterns. Watch it, then read the guide below on the Claude features 99% of users never find.
27:17

The engineer who built Claude Code just dropped a 28-minute video on how to write prompts that actually work. I've seen $300 courses that don't cover what he shows in the first 10 minutes. CLAUDE.md files, memory shortcuts, parallel sessions, prompting patterns. Watch it, then read the guide below on the Claude features 99% of users never find.

Anatoli Kopadze

687,933 просмотров • 26 дней назад

Jensen Huang told a room of global investors that AI is not one industry. It is five stacked on top of each other. Most people are investing in layer four and ignoring layers one through three entirely. He called it the five-layer cake. Layer one is energy. Jensen said this is the single greatest opportunity for the energy industry in a hundred years. The first time in a century that the grid in most countries can actually attract serious capital. Nuclear, solar, wind, hydrogen, it does not matter what form. If it produces energy, it gets funded. Siemens, GE Vernova, Mitsubishi. That is why they are all doing so well right now. Layer two is chips, computers, networking, and silicon photonics. Everything that processes the intelligence. Layer three is infrastructure. Land, power, buildings, data center operations. Every single one in short supply today. Layer four is the model layer. OpenAI, Anthropic. The layer everyone talks about. Layer five is applications. Every startup applying AI to financial services, legal, healthcare, logistics, transportation. Last year alone, a hundred billion dollars of venture capital went into this layer. The single largest VC year in the history of humanity. Then he said the number that stopped me cold. We are putting one trillion dollars into this five-layer cake this year. That sounds enormous. Jensen thinks the AI industry will eventually run at twenty trillion dollars per year. We are one trillion in of a twenty trillion dollar per year ecosystem. Most people watching AI are staring at layer four. Jensen was describing layers one through five as a single compounding system where every layer feeds the one above it. The people who understand that will invest differently than the people who do not.
4:50

Jensen Huang told a room of global investors that AI is not one industry. It is five stacked on top of each other. Most people are investing in layer four and ignoring layers one through three entirely. He called it the five-layer cake. Layer one is energy. Jensen said this is the single greatest opportunity for the energy industry in a hundred years. The first time in a century that the grid in most countries can actually attract serious capital. Nuclear, solar, wind, hydrogen, it does not matter what form. If it produces energy, it gets funded. Siemens, GE Vernova, Mitsubishi. That is why they are all doing so well right now. Layer two is chips, computers, networking, and silicon photonics. Everything that processes the intelligence. Layer three is infrastructure. Land, power, buildings, data center operations. Every single one in short supply today. Layer four is the model layer. OpenAI, Anthropic. The layer everyone talks about. Layer five is applications. Every startup applying AI to financial services, legal, healthcare, logistics, transportation. Last year alone, a hundred billion dollars of venture capital went into this layer. The single largest VC year in the history of humanity. Then he said the number that stopped me cold. We are putting one trillion dollars into this five-layer cake this year. That sounds enormous. Jensen thinks the AI industry will eventually run at twenty trillion dollars per year. We are one trillion in of a twenty trillion dollar per year ecosystem. Most people watching AI are staring at layer four. Jensen was describing layers one through five as a single compounding system where every layer feeds the one above it. The people who understand that will invest differently than the people who do not.

Ihtesham Ali

97,887 просмотров • 2 месяцев назад

most agent memory is one file that grows forever and gets re-read every single turn. it overflows the context, overwrites old facts, loses the thread. that's why your agent feels sharp on day one and lost by week three. Sibyl Memory replaces the pile with a structure: → leaner context, lower token cost. a bloated agent file and flat memory get re-read in full every message. Sibyl Memory keeps a light hot layer and retrieves the rest on demand, so each turn carries only the tokens that matter. → relations are first-class. people link to projects, projects to deals, deals to the decisions behind them. ask about one partner and the agent surfaces the whole connected web around them. that relational context is what lets it help run a company. → one source of truth per fact, person, and project. no duplicates, no silent overwrites. works with hermes, claude code, and codex. beta open.
0:34

most agent memory is one file that grows forever and gets re-read every single turn. it overflows the context, overwrites old facts, loses the thread. that's why your agent feels sharp on day one and lost by week three. Sibyl Memory replaces the pile with a structure: → leaner context, lower token cost. a bloated agent file and flat memory get re-read in full every message. Sibyl Memory keeps a light hot layer and retrieves the rest on demand, so each turn carries only the tokens that matter. → relations are first-class. people link to projects, projects to deals, deals to the decisions behind them. ask about one partner and the agent surfaces the whole connected web around them. that relational context is what lets it help run a company. → one source of truth per fact, person, and project. no duplicates, no silent overwrites. works with hermes, claude code, and codex. beta open.

SIBYL

81,361 просмотров • 2 месяцев назад

so I've been running exactly 8 AI agents on discord for a while now. coordination works great, they split tasks, hand off work, deliver results in parallel etc.. but there are problems I keep hitting that no amount of prompt engineering could fix agents don't learn from each other. Scout finds something useful but Luna has no idea. they work in the same server but knowledge stays locked in silos.. there's no quality filter on what gets saved, and good insights sit next to outdated garbage in the same memory files that I manually clean up.. and when an agent makes a mistake I write it down in the rules discord channel ,core memory file and hope it reads it next time. theres no self-correction, no automatic pattern recognition so of course no learning loops.. the coordination layer is solved. agents can work together. but the intelligence layer is still missing. agents that actually remember, learn from each other, filter noise, and get smarter every run. saw Spark building something like this with around 166 agents sharing a collective persistent knowledge across sessions, so agents learn from other agents and get smarter over time they even have noise filtering and self correcting loops built in, so the knowledge actually compounds instead of rotting.. super interesting stuff.. here where you think Spark could be a good coordinator for your stack of agent swarm. I think the intelligence layer is the bottleneck because it requires collectivity.. no single agent can solve it alone.. the whole network has to evolve together. this isn't going to stay niche, the moment agent coordination becomes standard, everyone is going to hit the same wall I hit.. agents that work but don't learn, coordinate but don't evolve... the intelligence layer becomes the only thing that separates a useful system from a dumb one. right now most people are still figuring out how to run one agent. by the time they get to multi-agent setups, collective intelligence won't be optional, it will be the baseline. we're early and the gap between agents that coordinate and agents that evolve together is the next phase. step one is done. ------ left: agents that coordinate but don’t learn right: the intelligence layer.. agents that evolve together within the same system.
0:39

so I've been running exactly 8 AI agents on discord for a while now. coordination works great, they split tasks, hand off work, deliver results in parallel etc.. but there are problems I keep hitting that no amount of prompt engineering could fix agents don't learn from each other. Scout finds something useful but Luna has no idea. they work in the same server but knowledge stays locked in silos.. there's no quality filter on what gets saved, and good insights sit next to outdated garbage in the same memory files that I manually clean up.. and when an agent makes a mistake I write it down in the rules discord channel ,core memory file and hope it reads it next time. theres no self-correction, no automatic pattern recognition so of course no learning loops.. the coordination layer is solved. agents can work together. but the intelligence layer is still missing. agents that actually remember, learn from each other, filter noise, and get smarter every run. saw Spark building something like this with around 166 agents sharing a collective persistent knowledge across sessions, so agents learn from other agents and get smarter over time they even have noise filtering and self correcting loops built in, so the knowledge actually compounds instead of rotting.. super interesting stuff.. here where you think Spark could be a good coordinator for your stack of agent swarm. I think the intelligence layer is the bottleneck because it requires collectivity.. no single agent can solve it alone.. the whole network has to evolve together. this isn't going to stay niche, the moment agent coordination becomes standard, everyone is going to hit the same wall I hit.. agents that work but don't learn, coordinate but don't evolve... the intelligence layer becomes the only thing that separates a useful system from a dumb one. right now most people are still figuring out how to run one agent. by the time they get to multi-agent setups, collective intelligence won't be optional, it will be the baseline. we're early and the gap between agents that coordinate and agents that evolve together is the next phase. step one is done. ------ left: agents that coordinate but don’t learn right: the intelligence layer.. agents that evolve together within the same system.

JUMPERZ

34,181 просмотров • 6 месяцев назад

A screen recording is the best context you can give an AI agent. It's also the worst. A few seconds of video is thousands of images. Feed that to an agent and you instantly blow up its memory. So I built a tool that fixes it. How it works: Hit record and just do your thing. Click around, type, and talk out loud about what you're doing. While you record, it quietly captures the stuff that actually matters: your voice transcription, every click and the exact thing you clicked, what you typed, and the shortcuts you press. When you stop, it doesn't hand the agent the whole video. It writes a short, readable summary: a timeline of what you said and did. The agent reads that tiny summary first. Then, only when it needs to actually see a moment, it pulls that one exact frame from the video, like flipping to a single page instead of reading the whole book. The result: the agent understands everything you did! Full context. Less tokens.
1:54

A screen recording is the best context you can give an AI agent. It's also the worst. A few seconds of video is thousands of images. Feed that to an agent and you instantly blow up its memory. So I built a tool that fixes it. How it works: Hit record and just do your thing. Click around, type, and talk out loud about what you're doing. While you record, it quietly captures the stuff that actually matters: your voice transcription, every click and the exact thing you clicked, what you typed, and the shortcuts you press. When you stop, it doesn't hand the agent the whole video. It writes a short, readable summary: a timeline of what you said and did. The agent reads that tiny summary first. Then, only when it needs to actually see a moment, it pulls that one exact frame from the video, like flipping to a single page instead of reading the whole book. The result: the agent understands everything you did! Full context. Less tokens.

Milind S

12,376 просмотров • 1 месяц назад

"I woke up and he already built a website, created a product, set up Stripe, and launched." Here's my new episode with Nat Eliason on how he set up his OpenClaw bot, Felix Craft, to build a business that made $14,718 in 3 weeks. We talked about: ✅ The 3-layer memory system that prevents your bot from forgetting things ✅ How to run 5 chats with your bot at the same time ✅ How to safely give your bot Stripe, Vercel, and X access Some quotes from Nat: "Every time Felix asks me to do something, I ask: Can I remove this bottleneck so you never have to ask me this again?" "I'm never in Claude Code or Codex myself anymore. I just tell Felix to do it." "If you get the memory system and the proactivity right, it solves 90% of the frustrations that most people run into." 📌 Watch now: Thanks to our sponsors: Linear: The AI agent platform for modern teams Replit ⠕: From 0 to full stack app in 2 min.
0:40

"I woke up and he already built a website, created a product, set up Stripe, and launched." Here's my new episode with Nat Eliason on how he set up his OpenClaw bot, Felix Craft, to build a business that made $14,718 in 3 weeks. We talked about: ✅ The 3-layer memory system that prevents your bot from forgetting things ✅ How to run 5 chats with your bot at the same time ✅ How to safely give your bot Stripe, Vercel, and X access Some quotes from Nat: "Every time Felix asks me to do something, I ask: Can I remove this bottleneck so you never have to ask me this again?" "I'm never in Claude Code or Codex myself anymore. I just tell Felix to do it." "If you get the memory system and the proactivity right, it solves 90% of the frustrations that most people run into." 📌 Watch now: Thanks to our sponsors: Linear: The AI agent platform for modern teams Replit ⠕: From 0 to full stack app in 2 min.

Peter Yang

230,230 просмотров • 5 месяцев назад