Sensitive content

This media may contain sensitive content.

Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

LLMs are stateless. We built Dria Mem Agent to change that: Making memory a first-class feature. A 4B agent with local interoperable memory across Claude, ChatGPT and LM Studio. It turns LLMs from stateless chat into stateful agents with persistent human-readable memory.

driaforall's profile picture

Dria

14,302 subscribers

170,393 Aufrufe • vor 10 Monaten •via X (Twitter)

NSFW
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

⚒️ How to build an AI agent with persistent memory? Watch Shaw (spirit/acc) building an agent from scratch with elizaOS & showing how external, queryable memory based on OriginTrail gives agents context and extends their memory beyond a single session. 02:15 – Set up your first agent 08:55 – Initializing runtime & memory foundations 12:50 – Wiring message handling & agent memory 24:45 – Persistent conversational memory in action 38:00 – Extending agents with plugins
1:05:27

⚒️ How to build an AI agent with persistent memory? Watch Shaw (spirit/acc) building an agent from scratch with elizaOS & showing how external, queryable memory based on OriginTrail gives agents context and extends their memory beyond a single session. 02:15 – Set up your first agent 08:55 – Initializing runtime & memory foundations 12:50 – Wiring message handling & agent memory 24:45 – Persistent conversational memory in action 38:00 – Extending agents with plugins

OriginTrail

37,242 Aufrufe • vor 6 Monaten

New course: Agent Memory: Building Memory-Aware Agents, built in partnership with Oracle and taught by Richmond Alake and Nacho Martínez. Many agents work well within a single session but their memory resets once the session ends. Consider a research agent working on dozens of papers across multiple days: without memory, it has no way to store and retrieve what it learned across sessions. This short course teaches you to build a memory system that enables agents to persist memory and thereby learn across sessions. You'll design a Memory Manager that handles different memory types, implement semantic tool retrieval that scales without bloating the context, and build write-back pipelines that let your agent autonomously update and refine what it knows over time. Skills you'll gain: - Build persistent memory stores for different agent memory types - Implement a Memory Manager that orchestrates how your agent reads, writes, and retrieves memory - Treat tools as procedural memory and retrieve only relevant ones at inference time using semantic search Join and learn to build agents that remember and improve over time!
1:37

New course: Agent Memory: Building Memory-Aware Agents, built in partnership with Oracle and taught by Richmond Alake and Nacho Martínez. Many agents work well within a single session but their memory resets once the session ends. Consider a research agent working on dozens of papers across multiple days: without memory, it has no way to store and retrieve what it learned across sessions. This short course teaches you to build a memory system that enables agents to persist memory and thereby learn across sessions. You'll design a Memory Manager that handles different memory types, implement semantic tool retrieval that scales without bloating the context, and build write-back pipelines that let your agent autonomously update and refine what it knows over time. Skills you'll gain: - Build persistent memory stores for different agent memory types - Implement a Memory Manager that orchestrates how your agent reads, writes, and retrieves memory - Treat tools as procedural memory and retrieve only relevant ones at inference time using semantic search Join and learn to build agents that remember and improve over time!

Andrew Ng

160,148 Aufrufe • vor 4 Monaten

Agents are scaling. So are the token costs. CIOs are shifting to AI PCs as strategic nodes. Ryzen AI Max 400 series changes the equation with 192GB of memory for local LLMs and agent swarms. You overheard it here first at Computex.
1:29

Agents are scaling. So are the token costs. CIOs are shifting to AI PCs as strategic nodes. Ryzen AI Max 400 series changes the equation with 192GB of memory for local LLMs and agent swarms. You overheard it here first at Computex.

AMD

11,342 Aufrufe • vor 1 Monat

Andrej Karpathy just explained the 5 shifts turning LLMs into agentic systems. 00:00 - Memory turns chat into personal AI 06:41 - Multimodal AI reads the world 16:58 - Thinking models solve harder tasks 24:51 - Search makes LLMs live 30:58 - Tools turn LLMs into workers Most people are still treating LLMs like chatbots. Karpathy is showing the full stack: Memory → Vision → Reasoning → Search → Tools Prompting is the old workflow. Agentic systems are the new one. This 40-minute talk is worth more than most paid AI agent courses. Bookmark and watch it before everyone catches up. Then read how to turn LLMs into self-improving agent loops below
42:43

Andrej Karpathy just explained the 5 shifts turning LLMs into agentic systems. 00:00 - Memory turns chat into personal AI 06:41 - Multimodal AI reads the world 16:58 - Thinking models solve harder tasks 24:51 - Search makes LLMs live 30:58 - Tools turn LLMs into workers Most people are still treating LLMs like chatbots. Karpathy is showing the full stack: Memory → Vision → Reasoning → Search → Tools Prompting is the old workflow. Agentic systems are the new one. This 40-minute talk is worth more than most paid AI agent courses. Bookmark and watch it before everyone catches up. Then read how to turn LLMs into self-improving agent loops below

Lunar

324,507 Aufrufe • vor 1 Tag

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!
2:57

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,788 Aufrufe • vor 1 Jahr

5 huge AI agents, MCP, and LLM updates today: 1. Mem0 just dropped OpenMemory MCP server that adds persistent memory across MCP clients. Create a shared memory layer with style, topics, emotions, etc. that works Claude, Cursor, Windsurf, and others. 100% local and opensource.
2:24

5 huge AI agents, MCP, and LLM updates today: 1. Mem0 just dropped OpenMemory MCP server that adds persistent memory across MCP clients. Create a shared memory layer with style, topics, emotions, etc. that works Claude, Cursor, Windsurf, and others. 100% local and opensource.

Unwind AI

63,243 Aufrufe • vor 1 Jahr

🚨 KEEP CALM AND AI - AUTONOMOUS AGENTS WITH INFINITE MEMORY We are launching the ability to create arbitrary agents that run on schedule and have access to a persistent and infinite memory The agents will be able to store, retrieve, and update information across sessions and perform repetitive tasks that require persistent memory Another step towards AGI and automating white-collar work 🚀🚀🚀
1:10

🚨 KEEP CALM AND AI - AUTONOMOUS AGENTS WITH INFINITE MEMORY We are launching the ability to create arbitrary agents that run on schedule and have access to a persistent and infinite memory The agents will be able to store, retrieve, and update information across sessions and perform repetitive tasks that require persistent memory Another step towards AGI and automating white-collar work 🚀🚀🚀

Bindu Reddy

12,626 Aufrufe • vor 6 Monaten

Meet Hermes Agent, the open source agent that grows with you. Hermes Agent remembers what it learns and gets more capable over time, with a multi-level memory system and persistent dedicated machine access.
0:49

Meet Hermes Agent, the open source agent that grows with you. Hermes Agent remembers what it learns and gets more capable over time, with a multi-level memory system and persistent dedicated machine access.

Nous Research

3,674,907 Aufrufe • vor 5 Monaten

HERMES AGENT OS JUST DROPPED AND LETS YOU RUN HERMES, CLAUDE, CODEX, AND OPENCLAW FROM ONE DASHBOARD WITH SHARED MEMORY. 12 agent profiles, built-in studio, and SEO tools deploying ranked content to 5 websites simultaneously.
19:05

HERMES AGENT OS JUST DROPPED AND LETS YOU RUN HERMES, CLAUDE, CODEX, AND OPENCLAW FROM ONE DASHBOARD WITH SHARED MEMORY. 12 agent profiles, built-in studio, and SEO tools deploying ranked content to 5 websites simultaneously.

0xMarioNawfal

22,059 Aufrufe • vor 2 Monaten

Holy shit... One month before Andrej Karpathy dropped the “LLM Wiki” idea… someone had already built it. Not theory. Not hype. A working system. LLMs today restart from zero every time. No memory. No evolution. No learning. That’s broken. Most people use CLAUDE.md / AGENTS.md → Manual updates → Easy to forget → Knowledge gets lost That’s not intelligence. That’s a notepad. So I built dynamic memory for LLMs: • Learns automatically • Stores without manual effort • Weakens irrelevant data over time • Strengthens what actually matters Before the “LLM Wiki” idea went viral, this already had: • Brain-like decay/boost memory • Smart deduplication (no noise) • Experience tracking per tech • Cross-referenced knowledge graph • Loss-proof backups • Auto-grouped tool sessions Then I added: • memory_audit (clean + optimize memory) • Memory injection directly into tools Now this isn’t just a concept. It’s a live system that turns LLMs from stateless tools → evolving intelligence. Using it daily: → ~5K tokens → Zero manual work → Memory that actually compounds Link in comments. RT & Bookmark — this will be standard soon.
0:32

Holy shit... One month before Andrej Karpathy dropped the “LLM Wiki” idea… someone had already built it. Not theory. Not hype. A working system. LLMs today restart from zero every time. No memory. No evolution. No learning. That’s broken. Most people use CLAUDE.md / AGENTS.md → Manual updates → Easy to forget → Knowledge gets lost That’s not intelligence. That’s a notepad. So I built dynamic memory for LLMs: • Learns automatically • Stores without manual effort • Weakens irrelevant data over time • Strengthens what actually matters Before the “LLM Wiki” idea went viral, this already had: • Brain-like decay/boost memory • Smart deduplication (no noise) • Experience tracking per tech • Cross-referenced knowledge graph • Loss-proof backups • Auto-grouped tool sessions Then I added: • memory_audit (clean + optimize memory) • Memory injection directly into tools Now this isn’t just a concept. It’s a live system that turns LLMs from stateless tools → evolving intelligence. Using it daily: → ~5K tokens → Zero manual work → Memory that actually compounds Link in comments. RT & Bookmark — this will be standard soon.

Nainsi Dwivedi

15,726 Aufrufe • vor 3 Monaten

our big bet with WALRUS MEMORY is that memory becomes a fully composable, transactable part of what ai agents need to do in the future and it's going to be an incredibly valuable asset and we've built a primitive that lets you fully own and carry it across every agent you use
1:20

our big bet with WALRUS MEMORY is that memory becomes a fully composable, transactable part of what ai agents need to do in the future and it's going to be an incredibly valuable asset and we've built a primitive that lets you fully own and carry it across every agent you use

Adeniyi.sui

26,501 Aufrufe • vor 1 Monat

We analyzed Anthropic’s memory architecture and built something better: a persistent, human-inspectable, and token-efficient memory layer that scales with your projects. Today, it’s OPEN-SOURCE. ByteRover CLI gives agents (like OpenClaw, Claude Code, and Hermes) persistent, structured memory. Built on the exact architecture that became the #1 memory system for OpenClaw (30,000+ downloads in a week), it lets developers curate project knowledge into a file-based hierarchy. This guarantees highly accurate, lightning-fast retrieval, even with lightweight models. 👉Highly Accurate: >92% retrieval accuracy across long-running sessions - the highest proven production accuracy on the market. ⚡Fast: ~1.6s average retrieval time. 💰Economic: Maintains >90% accuracy even with lightweight models, saving 50-70% on token costs. ☁ Portable: Runs locally by default, with cloud-sync to share memory across agents and teammates.
1:19

We analyzed Anthropic’s memory architecture and built something better: a persistent, human-inspectable, and token-efficient memory layer that scales with your projects. Today, it’s OPEN-SOURCE. ByteRover CLI gives agents (like OpenClaw, Claude Code, and Hermes) persistent, structured memory. Built on the exact architecture that became the #1 memory system for OpenClaw (30,000+ downloads in a week), it lets developers curate project knowledge into a file-based hierarchy. This guarantees highly accurate, lightning-fast retrieval, even with lightweight models. 👉Highly Accurate: >92% retrieval accuracy across long-running sessions - the highest proven production accuracy on the market. ⚡Fast: ~1.6s average retrieval time. 💰Economic: Maintains >90% accuracy even with lightweight models, saving 50-70% on token costs. ☁ Portable: Runs locally by default, with cloud-sync to share memory across agents and teammates.

andy nguyen

28,980 Aufrufe • vor 4 Monaten

Anthropic's Claude team just showed how to build an AI agent with real memory in under 30 minutes. 24-minutes. free. by the people who built Claude. one person + 10 agents with memory = a team that runs 24/7, remembers every customer improves itself. worth than $500 vibe-coding course.
24:23

Anthropic's Claude team just showed how to build an AI agent with real memory in under 30 minutes. 24-minutes. free. by the people who built Claude. one person + 10 agents with memory = a team that runs 24/7, remembers every customer improves itself. worth than $500 vibe-coding course.

Codez

1,613,107 Aufrufe • vor 2 Monaten

Memory for OpenClaw is now Native! Our first OpenClaw Memory Skill was a massive success: 30k+ downloads in a week and 500k+ organic impressions overnight for launch post. But we knew memory needed to be native. On March 21, OpenClaw merged PR #50848, allowing us to go beyond the skill layer and integrate directly into the agent’s context assembly flow. We try to make OpenClaw a truly 24/7 employee capable of complex workflows. The technical setup isn’t the hardest part but the real challenge is giving it a "brain" that remembers exact project details, past decisions, and team changes over time. The Native Memory Plugin is now live on NPM & ClawHub. Here is what it brings to your OpenClaw agents: 👉 Native Integration: Automatically manages a Three-Layer Memory architecture (Context Tree, Workspace Memory, Daily Memory). 👉 Git-like Stateful Memory: Organizes memory into a semantic hierarchy of human-readable, diffable Markdown files. You always get updated knowledge and can actually see and fix what your agent learns. 👉 Top Market Accuracy: Achieves an industry-leading 92.2% retrieval accuracy (LoCoMo & LongMemEval benchmarks), maintaining 90% accuracy even with cheap, lightweight models. 👉 Local-first & Portable: Local-by-default, fully portable for multi-agent teams. 👉 Super Easy Setup
1:46

Memory for OpenClaw is now Native! Our first OpenClaw Memory Skill was a massive success: 30k+ downloads in a week and 500k+ organic impressions overnight for launch post. But we knew memory needed to be native. On March 21, OpenClaw merged PR #50848, allowing us to go beyond the skill layer and integrate directly into the agent’s context assembly flow. We try to make OpenClaw a truly 24/7 employee capable of complex workflows. The technical setup isn’t the hardest part but the real challenge is giving it a "brain" that remembers exact project details, past decisions, and team changes over time. The Native Memory Plugin is now live on NPM & ClawHub. Here is what it brings to your OpenClaw agents: 👉 Native Integration: Automatically manages a Three-Layer Memory architecture (Context Tree, Workspace Memory, Daily Memory). 👉 Git-like Stateful Memory: Organizes memory into a semantic hierarchy of human-readable, diffable Markdown files. You always get updated knowledge and can actually see and fix what your agent learns. 👉 Top Market Accuracy: Achieves an industry-leading 92.2% retrieval accuracy (LoCoMo & LongMemEval benchmarks), maintaining 90% accuracy even with cheap, lightweight models. 👉 Local-first & Portable: Local-by-default, fully portable for multi-agent teams. 👉 Super Easy Setup

andy nguyen

169,136 Aufrufe • vor 4 Monaten

Atomic has launched Atomic Agent, a new open-source local agent for llama.cpp! > It can operate browsers through ARIA snapshots. > Able to edit files and run approved shell commands. > Has persistent memory across sessions. Fully local 👀
0:59

Atomic has launched Atomic Agent, a new open-source local agent for llama.cpp! > It can operate browsers through ARIA snapshots. > Able to edit files and run approved shell commands. > Has persistent memory across sessions. Fully local 👀

🚨 AI News | TestingCatalog

11,013 Aufrufe • vor 13 Tagen

Claude Tag is the next evolution of agents. It's a proactive, multiplayer agent with memory and identity, built on top of Claude Code. Learn more about how Claude Tag works and best practices for using it in this deep dive.
6:33

Claude Tag is the next evolution of agents. It's a proactive, multiplayer agent with memory and identity, built on top of Claude Code. Learn more about how Claude Tag works and best practices for using it in this deep dive.

ClaudeDevs

449,955 Aufrufe • vor 1 Monat

The barrier to deploying AI agents just hit zero. Akash Agents is a streamlined way to launch your OpenClaw or Hermes agent with a few simple clicks. Deploy instantly. No terminal, YAML, or cloud console required. Just your agent's logic, memory, and capabilities. Hermes by Nous Research ships with 40+ built-in tools, persistent memory, and subagent parallelization, making the experience best-in-class out of the box. → Try it for free at Built by our community member Sandeep Narahari
0:21

The barrier to deploying AI agents just hit zero. Akash Agents is a streamlined way to launch your OpenClaw or Hermes agent with a few simple clicks. Deploy instantly. No terminal, YAML, or cloud console required. Just your agent's logic, memory, and capabilities. Hermes by Nous Research ships with 40+ built-in tools, persistent memory, and subagent parallelization, making the experience best-in-class out of the box. → Try it for free at Built by our community member Sandeep Narahari

Akash Network

22,841 Aufrufe • vor 4 Monaten

We just launched a new primitive for AI Walrus Memory gives your agents persistent, portable memory that you own, and it drops straight into the platforms you already build on. Anthropic Claude, OpenAI ChatGPT, and Google Gemini, you name it plus native MCP and SDKs, added in a few lines of code LIVE TODAY
1:04

We just launched a new primitive for AI Walrus Memory gives your agents persistent, portable memory that you own, and it drops straight into the platforms you already build on. Anthropic Claude, OpenAI ChatGPT, and Google Gemini, you name it plus native MCP and SDKs, added in a few lines of code LIVE TODAY

Adeniyi.sui

46,164 Aufrufe • vor 2 Monaten

New short course: Long-Term Agentic Memory with LangGraph. Learn to build an agent with long-term memory in this course developed in collaboration with taught by its Co-Founder and CEO, Harrison Chase! Personal assistance and productivity tasks have become important use cases for agents. An important feature of an AI assistant, such as a coding or calendar assistant, is its ability to keep improving over time from its experience. Agent memory is the key capability that enables this. To add memory to an agent, you must first figure out what to store and what to retrieve when it is time to use the information. Additionally, you’ll have to decide when to update the stored information. For example, you might update in each iteration loop of the agent or perform updates in the background, with a helper agent. In this course, you will learn a mental framework to build agents with long-term memory. You'll create a useful email assistant that can respond, ignore, and notify using writing, scheduling, and memory-management tools. You’ll develop your agent's memory by adding facts to its memory store, provide examples to learn the user's preferences, and optimize system prompts to evolve instructions based on previous responses. In detail, you’ll: - Learn how the three types of memory--semantic, episodic, and procedural–and the two update mechanisms–via hot path and in the background–apply to your agents. - Build an email agent with writing, scheduling, and availability tools, along with a router that triages incoming email and handles it accordingly by ignoring, responding, or notifying the user. - Add tools to your email agent that allow it to operate on semantic memory by learning facts about the user, storing them in a long-term memory store, and searching over them in future interactions. - Incorporate episodic memory, in the form of few-shot examples, in the triage step of your agents to help them learn and update user preferences. - Add procedural memory as system prompts, optimized with feedback to improve the instructions the agent follows. Learn how to approach memory in agents, and start building agents with long-term memory with LangGraph! Please sign up here:
2:06

New short course: Long-Term Agentic Memory with LangGraph. Learn to build an agent with long-term memory in this course developed in collaboration with taught by its Co-Founder and CEO, Harrison Chase! Personal assistance and productivity tasks have become important use cases for agents. An important feature of an AI assistant, such as a coding or calendar assistant, is its ability to keep improving over time from its experience. Agent memory is the key capability that enables this. To add memory to an agent, you must first figure out what to store and what to retrieve when it is time to use the information. Additionally, you’ll have to decide when to update the stored information. For example, you might update in each iteration loop of the agent or perform updates in the background, with a helper agent. In this course, you will learn a mental framework to build agents with long-term memory. You'll create a useful email assistant that can respond, ignore, and notify using writing, scheduling, and memory-management tools. You’ll develop your agent's memory by adding facts to its memory store, provide examples to learn the user's preferences, and optimize system prompts to evolve instructions based on previous responses. In detail, you’ll: - Learn how the three types of memory--semantic, episodic, and procedural–and the two update mechanisms–via hot path and in the background–apply to your agents. - Build an email agent with writing, scheduling, and availability tools, along with a router that triages incoming email and handles it accordingly by ignoring, responding, or notifying the user. - Add tools to your email agent that allow it to operate on semantic memory by learning facts about the user, storing them in a long-term memory store, and searching over them in future interactions. - Incorporate episodic memory, in the form of few-shot examples, in the triage step of your agents to help them learn and update user preferences. - Add procedural memory as system prompts, optimized with feedback to improve the instructions the agent follows. Learn how to approach memory in agents, and start building agents with long-term memory with LangGraph! Please sign up here:

Andrew Ng

131,850 Aufrufe • vor 1 Jahr

🚀 Introducing the first-ever Agent UI 🚀 This is hands-down my favorite product! Chat with local Agents tailored to my needs. Local memory, storage, knowledge and tools 🔥 ⚡️ Your data, your control 🧠 Compatible with any LLM 🤝 Run multiple agents or a team of agents
8:33

🚀 Introducing the first-ever Agent UI 🚀 This is hands-down my favorite product! Chat with local Agents tailored to my needs. Local memory, storage, knowledge and tools 🔥 ⚡️ Your data, your control 🧠 Compatible with any LLM 🤝 Run multiple agents or a team of agents

Ashpreet Bedi

69,015 Aufrufe • vor 1 Jahr