Context Engineering is the future of AI Agents - here’s why
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
Matt Pocock’s Agentic Engineering Workflow (just copy him)
David Ondrej
58.6k views
This AI Agent can actually self-evolve… just watch
David Ondrej
28.0k views
This 100% minimal AI Agent can do anything… just watch
David Ondrej
28.3k views
This 100% self-improving AI Agent is insane… just watch
David Ondrej
34.5k views
This 100% private AI Agent can do anything… just watch
David Ondrej
24.7k views
Context Engineering for AI Agents with LangChain and Manus
LangChain
67.0k views
What is AI Engineering
Telusko
67.6k views
I spend $2,000/mo on AI tools, here are the best ones
David Ondrej
44.5k views
Context Engineering is All You NEED!
Prompt Engineering
38.7k views
Context Engineering for Agents
LangChain
189.5k views
Top Comments (10)
This method will quickly overwhelm the context window when applied to the complexities of real-world problems. This is why my architecture uses workflows instead of agents, and why I use a multi-layered memory (state) management system which is hardcoded into my architecture. I have agentic workflows which manage the memory spaces of the system and its components so that only information relevant to a specific task is given to the context window of that specific agent within the workflow. This micro-management of memory states according to task really makes a difference in the reliability of my MAS.
It reminds me of something I've already encountered in the Novelcrafter program, which uses AI to write stories. But they did something more there. When you write a new scene in a story, the AI also includes summaries of previous scenes in your instructions, allowing the narrative to be maintained. However, in addition, the program automatically includes in the prompt descriptions of important people, places, and objects that appear in your instructions, so that the LLM writing the next scene has this information. Example: your instruction: "The next scene describes a quarrel between Tom and Jessica". The program will add summaries of previous scenes and descriptions of the characters - Tom and Jessica, to this instruction. The program contains a database of key characters, places, and objects related to the story.
Honestly, this just makes sense. Whenever I design a system, I typically reach for paralellism last. Paralellism is great for getting large tasks accomplished more quickly, but you need to be sure that all the necessary input is available (in this case, the "context") and that the operations can be run in isolation from other processes/workflows without them requiring or impacting one another.
🤖Join the New Society and get free Vectal Pro for one month- Go here: https://www.skool.com/new-society ✨July only offer!
Love the comments. Discussion is a better source of knowledge than a lecture
Very insightful and inspiring video. Great job!
Now this… is quality content 👌
I really liked the intellectual drive to admit mistakes, even in past videos. It's clear that you're a serious guy, that you're smart, that you work well, that you love what you do and that you do it well.
As always well, focused and condensly presented. Thanks for your effort and input 🎉 Good to have you.
Could not agree more. Ive hit a brick wall after working on a huge (for me) multi agent project over the last 6 months. Sharing context and an application level memory layered on top of the agent memory. Appreciate the vid man, youve made a few things clearer for me.
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)
This method will quickly overwhelm the context window when applied to the complexities of real-world problems. This is why my architecture uses workflows instead of agents, and why I use a multi-layered memory (state) management system which is hardcoded into my architecture. I have agentic workflows which manage the memory spaces of the system and its components so that only information relevant to a specific task is given to the context window of that specific agent within the workflow. This micro-management of memory states according to task really makes a difference in the reliability of my MAS.
It reminds me of something I've already encountered in the Novelcrafter program, which uses AI to write stories. But they did something more there. When you write a new scene in a story, the AI also includes summaries of previous scenes in your instructions, allowing the narrative to be maintained. However, in addition, the program automatically includes in the prompt descriptions of important people, places, and objects that appear in your instructions, so that the LLM writing the next scene has this information. Example: your instruction: "The next scene describes a quarrel between Tom and Jessica". The program will add summaries of previous scenes and descriptions of the characters - Tom and Jessica, to this instruction. The program contains a database of key characters, places, and objects related to the story.
Honestly, this just makes sense. Whenever I design a system, I typically reach for paralellism last. Paralellism is great for getting large tasks accomplished more quickly, but you need to be sure that all the necessary input is available (in this case, the "context") and that the operations can be run in isolation from other processes/workflows without them requiring or impacting one another.
🤖Join the New Society and get free Vectal Pro for one month- Go here: https://www.skool.com/new-society ✨July only offer!
Love the comments. Discussion is a better source of knowledge than a lecture
Very insightful and inspiring video. Great job!
Now this… is quality content 👌
I really liked the intellectual drive to admit mistakes, even in past videos. It's clear that you're a serious guy, that you're smart, that you work well, that you love what you do and that you do it well.
As always well, focused and condensly presented. Thanks for your effort and input 🎉 Good to have you.
Could not agree more. Ive hit a brick wall after working on a huge (for me) multi agent project over the last 6 months. Sharing context and an application level memory layered on top of the agent memory. Appreciate the vid man, youve made a few things clearer for me.