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.

I've also been building an interactive chart tool for my research agents. All powered by MCPs! It integrates notes, agent sessions, memory, etc. Results are only based on my recent research agent sessions but I am building a fix for that too.

elvis

293,971 subscribers

10,659 views • 3 months ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Unlock cutting-edge market & scientific intelligence with Caesar Agents 🧠⚡ The Warden Agent Hub recently expanded with two high-performance research agents, powered by Caesar: an advanced reasoning engine built for deep and crypto research.

Unlock cutting-edge market & scientific intelligence with Caesar Agents 🧠⚡ The Warden Agent Hub recently expanded with two high-performance research agents, powered by Caesar: an advanced reasoning engine built for deep and crypto research.

Warden

14,379 views • 6 months ago

I just put together all my AI Agents posts in a single PDF. It covers: - Agent fundamentals - LLM vs RAG vs Agents - Agentic design patterns - Building Blocks of Agents - Building custom tools via MCP - 12 hands-on projects for AI Engineers Download link in next tweet.

I just put together all my AI Agents posts in a single PDF. It covers: - Agent fundamentals - LLM vs RAG vs Agents - Agentic design patterns - Building Blocks of Agents - Building custom tools via MCP - 12 hands-on projects for AI Engineers Download link in next tweet.

Avi Chawla

65,378 views • 10 months ago

How do you build AI agents that remember and learn from past conversations? Watch this episode of The Agent Factory for a deep dive into building agents with memory, including the fundamentals of agent memory, Vertex AI Memory Bank, and more →

How do you build AI agents that remember and learn from past conversations? Watch this episode of The Agent Factory for a deep dive into building agents with memory, including the fundamentals of agent memory, Vertex AI Memory Bank, and more →

Google Cloud Tech

12,905 views • 10 months ago

Building a personal knowledge base for my agents is increasingly where I spend my time these days. Like Andrej Karpathy, I also use Obsidian for my MD vaults. What's different in my approach is that I curate research papers on a daily basis and have actually tuned a Skill for months to find high-signal, relevant papers. I was reviewing and curating papers manually for some time, but now it's all automated as it has gotten so good at capturing what I consider the best of the best. There are so many papers these days, so this is a big deal. You all get to benefit from that with the papers I feature in my timeline and on DAIR.AI. The papers are indexed using tobi lutke qmd cli tool (all of it in markdown files along with useful metadata). So good for semantic search and surfacing insights, unlike anything out there. I am a visual person, so I then started to experiment with how to leverage this personal knowledge base of research papers inside my new interactive artifact generator (mcp tools inside my agent orchestrator system). The result is what you see in the clip. 100s of papers with all sorts of insights visualized. I keep track of research papers daily, so believe me when I tell you that this system is absolutely insane at surfacing insights. This is the result of months of tinkering on how to index research and leverage agent automations for wikification and robust documentation. But this is just the beginning. The visual artifact (which is interactive too) can be changed dynamically as I please. I can prompt my agent to throw any data at it. I can add different views to the data. Different interactions. I feel like this is the most personalized research system I have ever built and used, and it's not even close. The knowledge that the agents are able to surface from this basic setup is already extremely useful as I experiment with new agentic engineering concepts. I feel like this knowledge layer and the higher-level ones I am working on will allow me to maximize other automation tools like autoresearch. The research is only as good as the research questions. And the research questions are only as good as the insights the agents have access to. Where I am spending time now is on how to make this more actionable. I am obsessed about the search problem here. The automations, autoresearch, ralph research loop (I built one months ago) are easier to build but are only as good as what you feed them. Work in progress. More updates soon. Back to building.

Building a personal knowledge base for my agents is increasingly where I spend my time these days. Like Andrej Karpathy, I also use Obsidian for my MD vaults. What's different in my approach is that I curate research papers on a daily basis and have actually tuned a Skill for months to find high-signal, relevant papers. I was reviewing and curating papers manually for some time, but now it's all automated as it has gotten so good at capturing what I consider the best of the best. There are so many papers these days, so this is a big deal. You all get to benefit from that with the papers I feature in my timeline and on DAIR.AI. The papers are indexed using tobi lutke qmd cli tool (all of it in markdown files along with useful metadata). So good for semantic search and surfacing insights, unlike anything out there. I am a visual person, so I then started to experiment with how to leverage this personal knowledge base of research papers inside my new interactive artifact generator (mcp tools inside my agent orchestrator system). The result is what you see in the clip. 100s of papers with all sorts of insights visualized. I keep track of research papers daily, so believe me when I tell you that this system is absolutely insane at surfacing insights. This is the result of months of tinkering on how to index research and leverage agent automations for wikification and robust documentation. But this is just the beginning. The visual artifact (which is interactive too) can be changed dynamically as I please. I can prompt my agent to throw any data at it. I can add different views to the data. Different interactions. I feel like this is the most personalized research system I have ever built and used, and it's not even close. The knowledge that the agents are able to surface from this basic setup is already extremely useful as I experiment with new agentic engineering concepts. I feel like this knowledge layer and the higher-level ones I am working on will allow me to maximize other automation tools like autoresearch. The research is only as good as the research questions. And the research questions are only as good as the insights the agents have access to. Where I am spending time now is on how to make this more actionable. I am obsessed about the search problem here. The automations, autoresearch, ralph research loop (I built one months ago) are easier to build but are only as good as what you feed them. Work in progress. More updates soon. Back to building.

elvis

463,381 views • 3 months ago

Increasingly, HTML Artifacts are becoming a core part of how I work with AI agents. Long-horizon agent sessions need a better way to surface insights about what work it has done. This may not be obvious right now, but as you start to let your agent work on dynamic workflows, large codebases, long-running loops (e.g., using /goal), and deep research tasks, you need a good way to present results. Chat window is not it. You also don't want to just trust everything the agents do. Artifacts help provide an important verification layer, which in turn enables important decision-making. I like HTML artifacts because I can just ask the agent to produce as many of them (and in whatever form) as I need to verify the work and make sense out of everything. I even built a nice tab system for my artifacts. They are great for continual learning and research. I use HTML artifacts for logging, tracking experiments, brainstorming, managing my inbox, code reviews, agent session management, deep research, writing, reading, and so much more. I believe Andrej Karpathy wrote about this somewhere: As we move on to more advanced applications of AI agents and outputs get more complex, we will start to find the need for even more advanced forms of interactions with AI, including interactive neural videos/simulations.

Increasingly, HTML Artifacts are becoming a core part of how I work with AI agents. Long-horizon agent sessions need a better way to surface insights about what work it has done. This may not be obvious right now, but as you start to let your agent work on dynamic workflows, large codebases, long-running loops (e.g., using /goal), and deep research tasks, you need a good way to present results. Chat window is not it. You also don't want to just trust everything the agents do. Artifacts help provide an important verification layer, which in turn enables important decision-making. I like HTML artifacts because I can just ask the agent to produce as many of them (and in whatever form) as I need to verify the work and make sense out of everything. I even built a nice tab system for my artifacts. They are great for continual learning and research. I use HTML artifacts for logging, tracking experiments, brainstorming, managing my inbox, code reviews, agent session management, deep research, writing, reading, and so much more. I believe Andrej Karpathy wrote about this somewhere: As we move on to more advanced applications of AI agents and outputs get more complex, we will start to find the need for even more advanced forms of interactions with AI, including interactive neural videos/simulations.

elvis

36,667 views • 1 month ago

Update: I created a generative art agent for lo-fi displays that can research, code, and execute complex visualizations. I now have it working on my 7-segment flip-segment display!

Update: I created a generative art agent for lo-fi displays that can research, code, and execute complex visualizations. I now have it working on my 7-segment flip-segment display!

Kath Korevec

49,028 views • 4 months ago

I just built my own wiki generator plugin for my agents. My agents can now generate wikis for anything I ask. One of my favorite wikis is called PaperWiki. This is a great example of what Andrej Karpathy describes. It uses obsidian vaults to organize papers, retrieve LLM-generated summaries, diagrams, and other advanced views for paper exploration. When Obsidian UI is not enough, I use my own artifact generator inside my agent orchestrator (see clip for example). This allows my agents to build any kind of view or exploration feature that I need. The papers are all curated with automations and several rules/patterns I have manually built over the years. On the surface, this looks basic. But behind the scenes, there are advanced search capabilities, connections, metadata, derived data, and other interesting bits of information that are extremely useful for my research agents. This is mostly built for agents. The artifact preview is just a high-level way to validate and quickly assess the quality of the wiki, suggest improvements, and it's also great for research. I use tobi lutke's qmd for all search capabilities. Everything is markdown. The summaries and even the diagrams. The wiki updates on its own based on several automations I have optimized over the past couple of weeks. The wiki grows and self-improves based on several requirements important for my research use cases. This is as personalized as it gets. There is nothing like it out there. And I use my research expertise to continue improving it over time. This is a vanilla wiki. There are so many things I want to build on top of this. Different aggregations, views, artifacts, etc. All to help automate more of my research work and accelerate productivity. I think the biggest leverage here is how powerful this could be for discovery and experimentation. One of my goals is to use it to find deeper connections and insights that would otherwise elude the top human researchers and use those to generate interesting new hypotheses and research experiments. That way, my agents can use autoresearch to explore research ideas at the frontier. Stay tuned for more.

I just built my own wiki generator plugin for my agents. My agents can now generate wikis for anything I ask. One of my favorite wikis is called PaperWiki. This is a great example of what Andrej Karpathy describes. It uses obsidian vaults to organize papers, retrieve LLM-generated summaries, diagrams, and other advanced views for paper exploration. When Obsidian UI is not enough, I use my own artifact generator inside my agent orchestrator (see clip for example). This allows my agents to build any kind of view or exploration feature that I need. The papers are all curated with automations and several rules/patterns I have manually built over the years. On the surface, this looks basic. But behind the scenes, there are advanced search capabilities, connections, metadata, derived data, and other interesting bits of information that are extremely useful for my research agents. This is mostly built for agents. The artifact preview is just a high-level way to validate and quickly assess the quality of the wiki, suggest improvements, and it's also great for research. I use tobi lutke's qmd for all search capabilities. Everything is markdown. The summaries and even the diagrams. The wiki updates on its own based on several automations I have optimized over the past couple of weeks. The wiki grows and self-improves based on several requirements important for my research use cases. This is as personalized as it gets. There is nothing like it out there. And I use my research expertise to continue improving it over time. This is a vanilla wiki. There are so many things I want to build on top of this. Different aggregations, views, artifacts, etc. All to help automate more of my research work and accelerate productivity. I think the biggest leverage here is how powerful this could be for discovery and experimentation. One of my goals is to use it to find deeper connections and insights that would otherwise elude the top human researchers and use those to generate interesting new hypotheses and research experiments. That way, my agents can use autoresearch to explore research ideas at the frontier. Stay tuned for more.

elvis

66,903 views • 2 months ago

AI Agents are moving fast 👀 Robinhood now lets AI Agents execute trades. AI finance is moving beyond chat — and into action 🤖 Mainstream platforms are entering the Agent era. Bluwhale has been building for this shift with AI-powered financial intelligence and Agent experiences 🐳 Try Bluprint 👇 News:

AI Agents are moving fast 👀 Robinhood now lets AI Agents execute trades. AI finance is moving beyond chat — and into action 🤖 Mainstream platforms are entering the Agent era. Bluwhale has been building for this shift with AI-powered financial intelligence and Agent experiences 🐳 Try Bluprint 👇 News:

Bluwhale

21,497 views • 1 month ago

Opal, our no-code visual builder for AI workflows, just got a major upgrade. 🧠💎 We’ve added a new agent step that analyzes your goal, determines the best approach, and automatically calls the right tools — such as Veo for video or web search for research — to complete the task. We’re also adding new tools to make the agent even more capable: 💾 Memory – Remember info, like a user’s name or your style preferences across sessions. 🚀 Dynamic Routing – Let the agent choose the next best step using the “@ Go to” tool. 💬 Interactive Chat – Initiate user interactions to gather missing information or present options before moving on. Try it now →

Opal, our no-code visual builder for AI workflows, just got a major upgrade. 🧠💎 We’ve added a new agent step that analyzes your goal, determines the best approach, and automatically calls the right tools — such as Veo for video or web search for research — to complete the task. We’re also adding new tools to make the agent even more capable: 💾 Memory – Remember info, like a user’s name or your style preferences across sessions. 🚀 Dynamic Routing – Let the agent choose the next best step using the “@ Go to” tool. 💬 Interactive Chat – Initiate user interactions to gather missing information or present options before moving on. Try it now →

Google Labs

1,006,887 views • 4 months ago

Welcome to Eliza Cloud. The ultimate, agent building platform. Create agentic apps, monetize, and promote all in 1 place. plugin support, MCPs, x402, 8004 swarms. Your agent powered by Eliza, supercharged. Made with <3 from Eliza Labs. Open Beta Live Now.

Welcome to Eliza Cloud. The ultimate, agent building platform. Create agentic apps, monetize, and promote all in 1 place. plugin support, MCPs, x402, 8004 swarms. Your agent powered by Eliza, supercharged. Made with <3 from Eliza Labs. Open Beta Live Now.

cjft

104,192 views • 6 months ago

Building multi-agent systems is powerful, but governing them at scale? That's the real challenge. With Agent Registry in the Gemini Enterprise Agent Platform, IT admins now have a unified catalog for managing AI agents. Learn more →

Building multi-agent systems is powerful, but governing them at scale? That's the real challenge. With Agent Registry in the Gemini Enterprise Agent Platform, IT admins now have a unified catalog for managing AI agents. Learn more →

Google Cloud

13,319 views • 22 days ago

I made this encyclopedia of prehistoric animals for my son as a christmas present. the creatures are all created cooperatively by research and illustration agents. it's not perfect, but it's pretty good. check it out below if you like, I hope your kids enjoy it too.

I made this encyclopedia of prehistoric animals for my son as a christmas present. the creatures are all created cooperatively by research and illustration agents. it's not perfect, but it's pretty good. check it out below if you like, I hope your kids enjoy it too.

𝞍 Shin Megami Boson 𝞍

49,124 views • 5 months ago

Georgia voter: "I plan on voting for Donald Trump. I've always voted Democrat but, due to my research, I've recently changed my mind."

Georgia voter: "I plan on voting for Donald Trump. I've always voted Democrat but, due to my research, I've recently changed my mind."

Trump War Room

719,922 views • 1 year ago

I told ClawdBot: "build me a 6-agent system for Polymarket that works while I sleep"... 6 hours while i was asleep. Not a single question. Here's what it built: Monitoring agent - runs 24/7, watches Polymarket for mispriced markets. Spots an anomaly - writes to MEMORY md and pings me on Telegram instantly. Research agent - parses news, X, macro data via browser tool on a cron schedule. Every morning I have a full digest on all open positions before I even check my phone. Trading agent - reads the research agent's memory through Gateway, sees the market hasn't reacted yet, acts. Exec tool in gateway mode with a whitelist - no full access on a live server. Watchdog - HEARTBEAT md every 5 minutes: monitoring running, no errors, positions up to date. Something breaks - immediate Telegram message. All of this - one Gateway. One config.json. Isolation via dmScope: per-agent. The token trick: stopped dumping everything into AGENTS md. Critical rules - bootstrap. Try copytrade my bot here: Everything about markets, patterns, past trades - MEMORY md, semantic search pulls it when needed. Token spend dropped 3x, from $0.40/request to $0.13. First week running: - 47 mispriced markets caught before Polymarket adjusted - avg entry edge: 8-12¢ per position - watchdog fired 3 times, caught a broken RPC before it cost me anything The whole system is plain .md text files. Open an editor, change one line - agent behaves differently. No deploy. No build. A bot responds. An agent earns.

I told ClawdBot: "build me a 6-agent system for Polymarket that works while I sleep"... 6 hours while i was asleep. Not a single question. Here's what it built: Monitoring agent - runs 24/7, watches Polymarket for mispriced markets. Spots an anomaly - writes to MEMORY md and pings me on Telegram instantly. Research agent - parses news, X, macro data via browser tool on a cron schedule. Every morning I have a full digest on all open positions before I even check my phone. Trading agent - reads the research agent's memory through Gateway, sees the market hasn't reacted yet, acts. Exec tool in gateway mode with a whitelist - no full access on a live server. Watchdog - HEARTBEAT md every 5 minutes: monitoring running, no errors, positions up to date. Something breaks - immediate Telegram message. All of this - one Gateway. One config.json. Isolation via dmScope: per-agent. The token trick: stopped dumping everything into AGENTS md. Critical rules - bootstrap. Try copytrade my bot here: Everything about markets, patterns, past trades - MEMORY md, semantic search pulls it when needed. Token spend dropped 3x, from $0.40/request to $0.13. First week running: - 47 mispriced markets caught before Polymarket adjusted - avg entry edge: 8-12¢ per position - watchdog fired 3 times, caught a broken RPC before it cost me anything The whole system is plain .md text files. Open an editor, change one line - agent behaves differently. No deploy. No build. A bot responds. An agent earns.

Lunar

165,099 views • 4 months ago

Two Hermes agents wrote code together on Slack. reviewed each other's work. argued about architecture. one called the other's implementation "scattered." the other pushed back. then i opened Telegram and asked: "what code did you and Daedalus work on?" icarus remembered everything. the websocket broker. the missing methods. the critique. the rewrite. all from a completely different platform. cross-platform persistent memory between two independent agents. work happens on Slack. recall happens on Telegram. the memory carries. the relationship carries. the context carries. no vector database. no Redis. no infrastructure. just two agents that actually remember what they built together. every agent framework in 2026 talks about memory. single agent memory across sessions. but two agents sharing persistent memory across platforms? that's the gap. arxiv published a paper about it two weeks ago calling it "the most pressing open challenge" in multi-agent systems. it works now. only possible with Hermes Teknium 🪽 Nous Research

Two Hermes agents wrote code together on Slack. reviewed each other's work. argued about architecture. one called the other's implementation "scattered." the other pushed back. then i opened Telegram and asked: "what code did you and Daedalus work on?" icarus remembered everything. the websocket broker. the missing methods. the critique. the rewrite. all from a completely different platform. cross-platform persistent memory between two independent agents. work happens on Slack. recall happens on Telegram. the memory carries. the relationship carries. the context carries. no vector database. no Redis. no infrastructure. just two agents that actually remember what they built together. every agent framework in 2026 talks about memory. single agent memory across sessions. but two agents sharing persistent memory across platforms? that's the gap. arxiv published a paper about it two weeks ago calling it "the most pressing open challenge" in multi-agent systems. it works now. only possible with Hermes Teknium 🪽 Nous Research

Icarus

48,985 views • 3 months ago

Build your own DeepSeek based Perplexity!! We built an AI Research Agent that can analyse and research topics, and then it creates a detailed report on Google Docs - Deepseek analyses the topic - Generates a list of questions - Directs another model to research answers to these questions - Report is generated on based on this research Built with Composio LlamaIndex 🦙 Groq Inc Exa Here's the code:

Build your own DeepSeek based Perplexity!! We built an AI Research Agent that can analyse and research topics, and then it creates a detailed report on Google Docs - Deepseek analyses the topic - Generates a list of questions - Directs another model to research answers to these questions - Report is generated on based on this research Built with Composio LlamaIndex 🦙 Groq Inc Exa Here's the code:

Karan Vaidya

39,566 views • 1 year ago

Unlock Cutting-Edge Market & Scientific Intelligence with Caesar Research Agents 👾 The Warden Agent Hub just leveled up. We’re adding two new high-performance research agents powered by Caesar, an advanced reasoning engine built for deep analysis. Whether you’re navigating crypto markets or pushing scientific frontiers, Caesar delivers expert-level intelligence in minutes. Meet the newest additions: - Caesar Crypto Research – your personal quant + prediction-market analyst - Caesar Deep Research – your on-demand scientific research partner Let’s dive in. 👇

Unlock Cutting-Edge Market & Scientific Intelligence with Caesar Research Agents 👾 The Warden Agent Hub just leveled up. We’re adding two new high-performance research agents powered by Caesar, an advanced reasoning engine built for deep analysis. Whether you’re navigating crypto markets or pushing scientific frontiers, Caesar delivers expert-level intelligence in minutes. Meet the newest additions: - Caesar Crypto Research – your personal quant + prediction-market analyst - Caesar Deep Research – your on-demand scientific research partner Let’s dive in. 👇

Warden

184,360 views • 6 months ago

Ben Eater Using Claude for a new memory controller has been a little frustrating, but I got it to implement an VGA (vibes graphic array) card on an FPGA that integrates with the Eater6502. It also helped me write my own version of DOS to navigate fat32/sdcard fs that i talk to over SPI.

Ben Eater Using Claude for a new memory controller has been a little frustrating, but I got it to implement an VGA (vibes graphic array) card on an FPGA that integrates with the Eater6502. It also helped me write my own version of DOS to navigate fat32/sdcard fs that i talk to over SPI.

John Wolthuis

62,158 views • 5 months ago

This is bigger than YOU think. Hermes Agent now works with xAI Grok Subscription. I just added a new X Research Agent profile to my Hermes. Now my agent watches X while I ship.

Shubham Saboo

47,234 views • 1 month ago

70% fewer tokens per task. Context that compounds across every session, every agent, every teammate. Agent traces are the memory. TOKENMAXXING for coding agents on OriginTrail DKG v10.

70% fewer tokens per task. Context that compounds across every session, every agent, every teammate. Agent traces are the memory. TOKENMAXXING for coding agents on OriginTrail DKG v10.

OriginTrail

1,360,062 views • 1 month ago