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

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

Возникла проблема при загрузке этого видео. Это может быть связано с временными проблемами сети или видео может быть недоступно.

На главную

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 просмотров • 5 месяцев назад •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

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

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

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

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

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 просмотров • 1 год назад

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

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

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,974 просмотров • 2 месяцев назад

This is genuinely insane 🤯 I sent the same prompt to 2 Claude Opus 5 agents 1 agent used no MCPs 1 agent used 2 MCPS the goal was to clone a very famous game, that has over 4 billion downloads and the results are scary.. The 1st agents game looks pretty basic. but has all the mechanics in place and even has power ups. The 2nd agents game looks polished especially for 1 single prompt. the 2nd agent used higgsfield mcp to create images for all of the assets then sent those images to Meshy AI with a prompt to create them it also generated all the UI elements. the results speak for themselves. you need to start MCP maxxing

This is genuinely insane 🤯 I sent the same prompt to 2 Claude Opus 5 agents 1 agent used no MCPs 1 agent used 2 MCPS the goal was to clone a very famous game, that has over 4 billion downloads and the results are scary.. The 1st agents game looks pretty basic. but has all the mechanics in place and even has power ups. The 2nd agents game looks polished especially for 1 single prompt. the 2nd agent used higgsfield mcp to create images for all of the assets then sent those images to Meshy AI with a prompt to create them it also generated all the UI elements. the results speak for themselves. you need to start MCP maxxing

Ernesto Lopez

68,858 просмотров • 21 дней назад

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,104 просмотров • 6 месяцев назад

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

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

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,008,068 просмотров • 5 месяцев назад

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 просмотров • 7 месяцев назад

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 просмотров • 5 месяцев назад

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

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

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 просмотров • 7 месяцев назад

I need some help from a building expert. I've been told by a structural engineer that there is no evidence of a roof leak in my apartment, so I am wondering if there is a technical term for what's going on here? 😉

I need some help from a building expert. I've been told by a structural engineer that there is no evidence of a roof leak in my apartment, so I am wondering if there is a technical term for what's going on here? 😉

Dan Bruce

16,153 просмотров • 2 лет назад

The Gemini 2.0 era is here. And we’re excited for you to start building with it. A quick rewind of what we just released ⏪ Gemini 2.0 Flash ⚡ comes with low latency and better performance. 🔵 You can now access an experimental version in G3mini on the web, while Gemini Advanced users can try Deep Research, a new AI research assistant. 🔵 Developers can begin building through the Gemini API in Google AI Studio and Vertex AI 2.0 is also enabling new research prototypes of AI agents, including: 🔵 Project Astra, which explores future capabilities of a universal AI assistant 🔵 Project Mariner, which shows what’s possible for human-agent interaction, starting with your browser 🔵 Jules, an experimental AI-powered coding agent Finally, we’re exploring how 2.0 can be used in agents across domains — from navigating the virtual world of video games to applying its spatial reasoning capabilities to robotics. 🤖

The Gemini 2.0 era is here. And we’re excited for you to start building with it. A quick rewind of what we just released ⏪ Gemini 2.0 Flash ⚡ comes with low latency and better performance. 🔵 You can now access an experimental version in G3mini on the web, while Gemini Advanced users can try Deep Research, a new AI research assistant. 🔵 Developers can begin building through the Gemini API in Google AI Studio and Vertex AI 2.0 is also enabling new research prototypes of AI agents, including: 🔵 Project Astra, which explores future capabilities of a universal AI assistant 🔵 Project Mariner, which shows what’s possible for human-agent interaction, starting with your browser 🔵 Jules, an experimental AI-powered coding agent Finally, we’re exploring how 2.0 can be used in agents across domains — from navigating the virtual world of video games to applying its spatial reasoning capabilities to robotics. 🤖

Google DeepMind

231,798 просмотров • 1 год назад

Tavily Agent Skills are now here ⚡ Your agents can now: search the live web pull fresh docs & pages research markets, competitors and products cite sources all without leaving the terminal. We also shipped tavily-best-practices. A skill that teaches agents how to build production-ready web-connected AI built on real-world lessons from builders like you. Works wherever you’re building agents: Claude · Cursor · Google Antigravity Install now with one line.

Tavily Agent Skills are now here ⚡ Your agents can now: search the live web pull fresh docs & pages research markets, competitors and products cite sources all without leaving the terminal. We also shipped tavily-best-practices. A skill that teaches agents how to build production-ready web-connected AI built on real-world lessons from builders like you. Works wherever you’re building agents: Claude · Cursor · Google Antigravity Install now with one line.

Tavily

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

Writing release notes is fun if you enjoy spelunking through recent ships, commits, and agent sessions. For everyone else: Dispatches. Now live on Entire Web. Scope recent work by repo and date range, then turn it into a markdown update your team can actually read, because apparently "just check the commits" is not a communication strategy.

Writing release notes is fun if you enjoy spelunking through recent ships, commits, and agent sessions. For everyone else: Dispatches. Now live on Entire Web. Scope recent work by repo and date range, then turn it into a markdown update your team can actually read, because apparently "just check the commits" is not a communication strategy.

Entire

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

.Sentient has just integrated Messari 's data and research into its AI-powered search platform, Sentient Chat. This partnership basically allows users to access Messari’s research directly through the Agent Hub in Sentient Chat where they can get instant answers and insights from Messari reports. The integration is done via Messari Copilot, which means users can now easily get to Messari’s crypto data without having to dig through extensive reports themselves. Messari's data and research now feeds into Sentient’s Agentic Perplexity, here users can access this in the Agent Hub for all their crypto related questions. Integrating Messari’s research now helps provide an open & community-driven platform for AI-powered search, ensuring that users have access to the best crypto data and insights in real time, while also expanding the functionality of Sentient’s Agent Hub, where users can find and use a growing library of AI agents for various tasks. Now I don't know about you but I know where I'll be getting my stats from moving forward.

.Sentient has just integrated Messari 's data and research into its AI-powered search platform, Sentient Chat. This partnership basically allows users to access Messari’s research directly through the Agent Hub in Sentient Chat where they can get instant answers and insights from Messari reports. The integration is done via Messari Copilot, which means users can now easily get to Messari’s crypto data without having to dig through extensive reports themselves. Messari's data and research now feeds into Sentient’s Agentic Perplexity, here users can access this in the Agent Hub for all their crypto related questions. Integrating Messari’s research now helps provide an open & community-driven platform for AI-powered search, ensuring that users have access to the best crypto data and insights in real time, while also expanding the functionality of Sentient’s Agent Hub, where users can find and use a growing library of AI agents for various tasks. Now I don't know about you but I know where I'll be getting my stats from moving forward.

Polygon Stats

32,701 просмотров • 1 год назад

1/ 🔥🔥 Big news: We’re launching Percival, the first AI agent that can evaluate and fix other AI agents! 🤖 Percival is an evaluation agent that doesn’t just detect failures in agent traces — it can fix them. Percival outperformed SOTA LLMs by 2.9x on the TRAIL dataset, containing human annotated errors from GAIA and SWE-Bench. 🦾 Here’s what Percival can do for you: - Automatically suggest prompt fixes for your agent - Catch 20+ types of agent failures spanning tool use, planning and coordination, domain specific errors - Reduce manual debugging time from hours to < 1 minute

1/ 🔥🔥 Big news: We’re launching Percival, the first AI agent that can evaluate and fix other AI agents! 🤖 Percival is an evaluation agent that doesn’t just detect failures in agent traces — it can fix them. Percival outperformed SOTA LLMs by 2.9x on the TRAIL dataset, containing human annotated errors from GAIA and SWE-Bench. 🦾 Here’s what Percival can do for you: - Automatically suggest prompt fixes for your agent - Catch 20+ types of agent failures spanning tool use, planning and coordination, domain specific errors - Reduce manual debugging time from hours to < 1 minute

PatronusAI

24,051 просмотров • 1 год назад

I set a Ralph loop using agent-browser + Parallel Web Systems to do a ton of market research. Perfect way to have an agent working while I do other things. Decided to setup my iMac for a lot of the looping tasks because it makes it easier to keep the repo clones and work product separated.

I set a Ralph loop using agent-browser + Parallel Web Systems to do a ton of market research. Perfect way to have an agent working while I do other things. Decided to setup my iMac for a lot of the looping tasks because it makes it easier to keep the repo clones and work product separated.

Ryan Carson

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

Since subscribers can now use their existing Grok credentials directly within the Hermes xai shipped grok-via-oauth for hermes. your grok sub works inside the agent now. so i hooked icarus up to it. when hermes finds a thread worth saving, it lands in my obsidian vault as a note. handle. pages, topic pages, backlinks. graph view fills itself out. icarus plugin for hermes agents is why my agent doesn't forget. memory is just markdown in a folder. you can read it, grep it, edit it. Congrats to Teknium 🪽 and Nous Research

Since subscribers can now use their existing Grok credentials directly within the Hermes xai shipped grok-via-oauth for hermes. your grok sub works inside the agent now. so i hooked icarus up to it. when hermes finds a thread worth saving, it lands in my obsidian vault as a note. handle. pages, topic pages, backlinks. graph view fills itself out. icarus plugin for hermes agents is why my agent doesn't forget. memory is just markdown in a folder. you can read it, grep it, edit it. Congrats to Teknium 🪽 and Nous Research

Icarus

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

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

elvis

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