Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

This is the most insane application of MCP I've used. Context is king! Your coding agents thrive on high-quality context. Qodo Aware is a production-ready deep research agent that solves this. This is huge! Watch how I use it in Codex to retrieve context from large codebases.

elvis

265,603 subscribers

80,225 views • 11 months ago •via X (Twitter)

Science & Technology Education

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

🚀Announcing Qodo Aware 🚀 Your AI coding assistant is flying blind. It sees a few hops from your current file, but misses a LOT of context that matters. Qodo Aware is the first and ONLY deep research agent built for finding the right context across large, complex codebases: 10 repos or 1,000. 🔥 Read the blog here ->

🚀Announcing Qodo Aware 🚀 Your AI coding assistant is flying blind. It sees a few hops from your current file, but misses a LOT of context that matters. Qodo Aware is the first and ONLY deep research agent built for finding the right context across large, complex codebases: 10 repos or 1,000. 🔥 Read the blog here ->

Qodo

19,510 views • 11 months ago

Nia by @NozomioAI is an MCP that gives coding agents 10x more developer context. It indexes external repos and docs, so any coding agent always has the right context. Congrats on the launch, Arlan!

Nia by @NozomioAI is an MCP that gives coding agents 10x more developer context. It indexes external repos and docs, so any coding agent always has the right context. Congrats on the launch, Arlan!

Y Combinator

33,333 views • 1 year ago

Introducing Inspector's context-aware screenshot tool! Screenshots as context for your coding agent is a pain. I decided I was tired of it and shipped something today to help with that.

Introducing Inspector's context-aware screenshot tool! Screenshots as context for your coding agent is a pain. I decided I was tired of it and shipped something today to help with that.

mikeBuildsMore

21,962 views • 9 months ago

This is Repo Prompt 2.0 A fully integrated agent, that makes it seamless to use RP's powerful MCP tools, with a built-in oracle and context builder. A first class experience showcasing how much better and efficient your agents can be with good context engineering tools.

This is Repo Prompt 2.0 A fully integrated agent, that makes it seamless to use RP's powerful MCP tools, with a built-in oracle and context builder. A first class experience showcasing how much better and efficient your agents can be with good context engineering tools.

eric provencher

38,921 views • 5 months ago

Anthropic engineer: “80% of our engineers are using Loops. Now everyone is exploring how to build right Context for agents.” in 3-6 months, we’ll all become context engineers. Context is the most important part of agents.” in this 1-hour talk, Anthropic engineer shows how to build a self-improving agents from sratch. It’s worth more than a $500 agentic course. Watch this video, then read the article below on how to become a context architect.

Anthropic engineer: “80% of our engineers are using Loops. Now everyone is exploring how to build right Context for agents.” in 3-6 months, we’ll all become context engineers. Context is the most important part of agents.” in this 1-hour talk, Anthropic engineer shows how to build a self-improving agents from sratch. It’s worth more than a $500 agentic course. Watch this video, then read the article below on how to become a context architect.

Codez

35,798 views • 20 days ago

your coding agent sucks because it lacks context. so I built nia to fix that. here is how you can 10x your coding agent (thread):

your coding agent sucks because it lacks context. so I built nia to fix that. here is how you can 10x your coding agent (thread):

Arlan

54,135 views • 1 year ago

Anthropic engineer: “80% of our engineers are using self-improving loops. Now everyone is exploring how to build the right Context for agents.” in 3-6 months, we’ll all become context engineers. Context is the most important part of building agents.” In this 40-minute lecture, an Anthropic engineer shows how to build a self-improving agentic workflow from scratch. It’s worth more than a $500 agentic course. Watch this video, then read the article below on how to become a context architect.

Anthropic engineer: “80% of our engineers are using self-improving loops. Now everyone is exploring how to build the right Context for agents.” in 3-6 months, we’ll all become context engineers. Context is the most important part of building agents.” In this 40-minute lecture, an Anthropic engineer shows how to build a self-improving agentic workflow from scratch. It’s worth more than a $500 agentic course. Watch this video, then read the article below on how to become a context architect.

Movez

21,046 views • 20 days ago

The new company brain. Context is the soul of your company, I learned today. Since I wrote a book, “Age of Context,” years ago I see that context is what we now call our private data. That data should be stored in a way to let AI agents and humans get more and more use out of it. This is precisely what PromptQL does and here Tanmai Gopal goes deep on how it now is a company brain, or, rather, a wiki that everyone updates and uses.

The new company brain. Context is the soul of your company, I learned today. Since I wrote a book, “Age of Context,” years ago I see that context is what we now call our private data. That data should be stored in a way to let AI agents and humans get more and more use out of it. This is precisely what PromptQL does and here Tanmai Gopal goes deep on how it now is a company brain, or, rather, a wiki that everyone updates and uses.

Robert Scoble

18,314 views • 1 month ago

This is Claude Sonnet 4.6: our most capable Sonnet model yet. It’s a full upgrade across coding, computer use, long-context reasoning, agent planning, knowledge work, and design. It also features a 1M token context window in beta.

This is Claude Sonnet 4.6: our most capable Sonnet model yet. It’s a full upgrade across coding, computer use, long-context reasoning, agent planning, knowledge work, and design. It also features a 1M token context window in beta.

Claude

7,600,438 views • 6 months ago

this is next-level vibe coding! 🤯 watch me use windsurf's new preview feature to make quick ui improvements all within my coding environment! this feature is insane! agentic capabilities + long-context awareness in full display

this is next-level vibe coding! 🤯 watch me use windsurf's new preview feature to make quick ui improvements all within my coding environment! this feature is insane! agentic capabilities + long-context awareness in full display

elvis

67,487 views • 1 year ago

🇸🇦🇺🇸 DAVID SACKS: MCP IS THE NEXT BIG WAVE IN AI "MCP {Model Context Protocol} is a new standard that allows agents to talk to existing SaaS applications or any kind of application, and it's really going to enable this agentic future that I think is the next big wave in AI." Source: David Sacks

🇸🇦🇺🇸 DAVID SACKS: MCP IS THE NEXT BIG WAVE IN AI "MCP {Model Context Protocol} is a new standard that allows agents to talk to existing SaaS applications or any kind of application, and it's really going to enable this agentic future that I think is the next big wave in AI." Source: David Sacks

Mario Nawfal

123,179 views • 1 year ago

This is wild. OpenAI just dropped GPT-5.4 and it will completely change the AI agent game. 1M context, huge leap for coding + agents, and native computer use. 7 wild examples. Bookmark this. 1. Build & Play 3D chess game

This is wild. OpenAI just dropped GPT-5.4 and it will completely change the AI agent game. 1M context, huge leap for coding + agents, and native computer use. 7 wild examples. Bookmark this. 1. Build & Play 3D chess game

Min Choi

326,322 views • 5 months ago

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Jurij Skornik

11,166 views • 2 months ago

👋 Meet the Model Context Protocol (MCP): the open standard allowing apps to feed vital context to LLMs. Why is this protocol so important? Because context is what turns those generic AI replies into relevant, useful assistance tailored to your work. In this video, ☁️ Chris Reddington explains how MCP delivers this crucial info and why it makes such a difference for AI pair programmers like GitHub Copilot. 💡

👋 Meet the Model Context Protocol (MCP): the open standard allowing apps to feed vital context to LLMs. Why is this protocol so important? Because context is what turns those generic AI replies into relevant, useful assistance tailored to your work. In this video, ☁️ Chris Reddington explains how MCP delivers this crucial info and why it makes such a difference for AI pair programmers like GitHub Copilot. 💡

GitHub

35,316 views • 1 year ago

Claude 3.7 Sonnet has serious competition! Gemini 2.5 Pro is a legit good model for code. - code quality is really good - 1M token context - native multimodality - long code generation - understand large codebases I used it with Windsurf to generate an AI search agent app:

Claude 3.7 Sonnet has serious competition! Gemini 2.5 Pro is a legit good model for code. - code quality is really good - 1M token context - native multimodality - long code generation - understand large codebases I used it with Windsurf to generate an AI search agent app:

elvis

211,476 views • 1 year ago

Coding agents suck at using a browser. Playwright MCP burns through your context window before you even send your first prompt. That is why I built Dev Browser, a Claude Skill to let your agent close the loop without eating up tokens.

Coding agents suck at using a browser. Playwright MCP burns through your context window before you even send your first prompt. That is why I built Dev Browser, a Claude Skill to let your agent close the loop without eating up tokens.

Sawyer Hood

312,803 views • 8 months ago

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!

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 views • 1 year ago

AI that senses coding frustration, is this the future of learning? In our latest GitHub Podcast episode we talk to Angie Jones about Goose, Block’s open source AI agent and reference implementation of the Model Context Protocol (MCP).

AI that senses coding frustration, is this the future of learning? In our latest GitHub Podcast episode we talk to Angie Jones about Goose, Block’s open source AI agent and reference implementation of the Model Context Protocol (MCP).

GitHub

16,414 views • 8 months ago

Big moment for Postgres! AI agents broke the idea of what a database is supposed to do. Traditional databases were built for humans, and Agents broke that model. - They branch endlessly. - They run ten experiments at once. - They need isolation, context, memory, structured reasoning, and safe sandboxes. Letting agents touch production systems is terrifying because the old model of Postgres was never built for this kind of behavior. Agentic Postgres is an agent-ready version of Postgres by TimescaleDB (by Tiger Data) that solves this. I think it is one of the biggest upgrades to the Agent stack this year and Tiger Data is working with me on this post to share what they did. Some key features: > It instantly creates branches of an entire database, which is perfect for parallel agent evals, safe experiments, migrations, or isolated testing. Forks take seconds and cost almost nothing. > It comes with a built-in MCP server, which agents can use to get schema guidance, best practices, and safe, structured access to Postgres. This is also helpful to run migrations with a real understanding. > It comes with actual hybrid search (vector search and BM25), so Agents can retrieve data directly inside the database. > The database is Memory native. This gives a persistent context for Agents to evolve. This is one of the first times I have seen Postgres feel ready for the AI native era.

Big moment for Postgres! AI agents broke the idea of what a database is supposed to do. Traditional databases were built for humans, and Agents broke that model. - They branch endlessly. - They run ten experiments at once. - They need isolation, context, memory, structured reasoning, and safe sandboxes. Letting agents touch production systems is terrifying because the old model of Postgres was never built for this kind of behavior. Agentic Postgres is an agent-ready version of Postgres by TimescaleDB (by Tiger Data) that solves this. I think it is one of the biggest upgrades to the Agent stack this year and Tiger Data is working with me on this post to share what they did. Some key features: > It instantly creates branches of an entire database, which is perfect for parallel agent evals, safe experiments, migrations, or isolated testing. Forks take seconds and cost almost nothing. > It comes with a built-in MCP server, which agents can use to get schema guidance, best practices, and safe, structured access to Postgres. This is also helpful to run migrations with a real understanding. > It comes with actual hybrid search (vector search and BM25), so Agents can retrieve data directly inside the database. > The database is Memory native. This gives a persistent context for Agents to evolve. This is one of the first times I have seen Postgres feel ready for the AI native era.

Avi Chawla

94,290 views • 9 months ago

this is how it feels to say 67 in a regular context nowadays

this is how it feels to say 67 in a regular context nowadays

jerry

594,319 views • 3 months ago