The Death of RAG?
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
Ben Shapiro Reacts To The Death Of Spirit Airlines
Ben Shapiro
16.3k views
The RL Irony in LLMs
bycloud
23.0k views
THE DEATH OF MAGA | The Kyle Kulinski Show
Secular Talk
154.0k views
The biggest Mystery of LLMs have just been solved
bycloud
102.6k views
The Chinese AI Iceberg
bycloud
107.4k views
The Death of Todd Stermer | Full Episode
48 Hours
1.1m views
The Death of Streaming
penguinz0
1.7m views
The Side Effects of Overusing ChatGPT For Homework
bycloud
26.6k views
The LLM's RL Revelation We Didn't See Coming
bycloud
142.3k views
How DeepSeek Built The Current "Best" Math Prover AI
bycloud
36.9k views
Top Comments (10)
It's basically the same idea used in Claude Code or in Codex with subagents.
i remember reading infini-attention paper too i believe it when i see it working....
this isn't really a recursive language model -- all of the other papers on this topic talk about recursion happening in the model architecture. This is just a context orchestration algorithm, like a tool chain or agent loop. Not an LM architecture.
The needle in a heystack test should start utilizing vagueness in the query more.
-this literally is an agent -RAG doesn't necessitate using vector db, navigating folders with descriptions is rag. -sparse attention like Deepseek did, is the equivalent and more straightforward lazy approach. -rag will never die, a focused context window is necessary for reasoning, like this shows. -this thing is underwhelming, it should restructure context, and save the decomposition.
Isnt' Claude code doing the same thing?
9:00 and you just described RLM.... I really don't think why we need a distinction between RLM and an Agent, I mean in a sense RLM is agentic context management....
good idea . ill have my agents work on it
Check out Inngest and let your AI agents wear a harness now! https://www.inngest.com/docs?utm_source=youtube&utm_medium=video&utm_campaign=yt-bycl-3
3:33 I love your humor
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (10)
It's basically the same idea used in Claude Code or in Codex with subagents.
i remember reading infini-attention paper too i believe it when i see it working....
this isn't really a recursive language model -- all of the other papers on this topic talk about recursion happening in the model architecture. This is just a context orchestration algorithm, like a tool chain or agent loop. Not an LM architecture.
The needle in a heystack test should start utilizing vagueness in the query more.
-this literally is an agent -RAG doesn't necessitate using vector db, navigating folders with descriptions is rag. -sparse attention like Deepseek did, is the equivalent and more straightforward lazy approach. -rag will never die, a focused context window is necessary for reasoning, like this shows. -this thing is underwhelming, it should restructure context, and save the decomposition.
Isnt' Claude code doing the same thing?
9:00 and you just described RLM.... I really don't think why we need a distinction between RLM and an Agent, I mean in a sense RLM is agentic context management....
good idea . ill have my agents work on it
Check out Inngest and let your AI agents wear a harness now! https://www.inngest.com/docs?utm_source=youtube&utm_medium=video&utm_campaign=yt-bycl-3
3:33 I love your humor