Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

Your Nous Research Hermes agent has a 2,200-character memory. Its notes live inside the instructions it loads at session start, so the space never grows. Hit the cap and the next thing it learns gets rejected - to remember something new, it has to delete something it already knew.... show more

mem0

19,954 subscribers

18,540 görüntüleme • 11 gün önce •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,186 görüntüleme • 3 ay önce

Have you checked out your Memory Graph in the Hermes Desktop? Team at Nous Research ships so much that even I miss some new features 😅 I think this has been out for a while, but the Memory Graph lets you see how your agent has developed, and how memories impacted skills. Check it out!

Have you checked out your Memory Graph in the Hermes Desktop? Team at Nous Research ships so much that even I miss some new features 😅 I think this has been out for a while, but the Memory Graph lets you see how your agent has developed, and how memories impacted skills. Check it out!

tonbi

135,563 görüntüleme • 1 ay önce

HERMES AGENT LEARNS FROM ITS OWN MISTAKES. UPDATES ITS MEMORY. CREATES ITS OWN SKILLS. NO CLOUD. EVERYTHING STORED LOCALLY. THIS IS HOW THE SELF-IMPROVING LOOP WORKS. most agents start from zero every session. Hermes carries forward what it learned. THREE MEMORY SYSTEMS: 1. PROCEDURAL MEMORY (how to act) stored in ~/.hermes/skills/ as SKILL.md files. when the agent repeats a complex workflow, it saves the procedure as a reusable skill. next time the same task comes up, it follows the skill instead of figuring it out again. you can also create skills explicitly: "create a skill called video-prep that captures how I format my video scripts. spoken english, define jargon inline, no em-dashes, close with a catchphrase." the agent writes the SKILL.md. available as a slash command from that moment. Hermes ships with 90+ skills. the number grows the longer you use it. 2. SEMANTIC MEMORY (durable facts about you) stored in ~/.hermes/memory/memory.md the agent scans conversations for facts worth remembering. preferences, habits, corrections, project details. real example from the video: agent tried to scrape a YouTube channel. URL was wrong. it failed. it updated memory.md with the correct URL pattern so it never makes the same mistake again. you can also save explicitly: "save to memory that my favorite testing framework is pytest" the agent updates memory.md immediately. this file loads into context on every session. the agent knows you better every week. 3. EPISODIC MEMORY (chat history) stored in ~/.hermes/state.db (local SQLite). every conversation. every tool call. every result. searchable with FTS5 full-text search. "search our past sessions. what was the first thing I ever said to you?" the agent queries state.db and finds it. over time, auxiliary models consolidate episodic memory into semantic memory. distilling recurring patterns into durable facts. THE SELF-IMPROVING LOOP: every agent run follows this cycle: → you send a prompt → working memory loads: SOUL.md + memory.md + relevant skills + chat history → agent calls tools (terminal, browser, delegate_task) → agent completes the task, replies to you → AFTER the reply: agent checks "did I learn something worth saving?" → if yes: updates memory.md or creates a new skill → next session starts smarter than the last this happens automatically. you don't ask the agent to learn. it decides what to remember on its own. WHAT MAKES THIS DIFFERENT FROM CLAUDE CODE: Claude Code has memory too. but Hermes stores everything locally. no cloud. your data never leaves your machine. Claude Code doesn't auto-create skills from experience. Hermes turns repeated workflows into reusable procedures. Claude Code memory is instruction-based. Hermes memory is conversational and self-updating. over months of usage, Hermes builds a knowledge base of your preferences, your projects, your mistakes, and the procedures that work for your specific workflow. the agent that remembers your birthday also remembers why your last deploy failed. NO EMBEDDINGS. PLAIN TEXT. Hermes does not use embeddings or RAG for memory. skill and memory search runs on plain text keyword matching. simpler. faster. no vector database to maintain. works entirely offline on your local machine. DELEGATE TO CLAUDE CODE: Hermes can spawn a sub-agent that runs Claude Code in headless mode: "spawn a sub-agent using Claude CLI to build a Python script that fetches the top 5 Hacker News stories to markdown." Hermes delegates. Claude Code writes the code. result returns to Hermes. Hermes runs the script and delivers the output. use Hermes for orchestration. use Claude Code for heavy coding. both tools. not competitors. WHAT HERMES DOES NOT HAVE: no built-in eval or LMOps system. no LangSmith, no LangFuse integration out of the box. trajectory export and logs exist but there is no automated quality tracking. if you need eval, build it yourself or connect external tools. the loop is self-improving. measuring how well it improves is on you. comment LOOP and I'll send you the configs that control how fast Hermes learns and what it remembers. memory limits, skill auto-creation triggers, and the auxiliary model that runs the learning. Replace your entire team with 8 hermes agents👇

HERMES AGENT LEARNS FROM ITS OWN MISTAKES. UPDATES ITS MEMORY. CREATES ITS OWN SKILLS. NO CLOUD. EVERYTHING STORED LOCALLY. THIS IS HOW THE SELF-IMPROVING LOOP WORKS. most agents start from zero every session. Hermes carries forward what it learned. THREE MEMORY SYSTEMS: 1. PROCEDURAL MEMORY (how to act) stored in ~/.hermes/skills/ as SKILL.md files. when the agent repeats a complex workflow, it saves the procedure as a reusable skill. next time the same task comes up, it follows the skill instead of figuring it out again. you can also create skills explicitly: "create a skill called video-prep that captures how I format my video scripts. spoken english, define jargon inline, no em-dashes, close with a catchphrase." the agent writes the SKILL.md. available as a slash command from that moment. Hermes ships with 90+ skills. the number grows the longer you use it. 2. SEMANTIC MEMORY (durable facts about you) stored in ~/.hermes/memory/memory.md the agent scans conversations for facts worth remembering. preferences, habits, corrections, project details. real example from the video: agent tried to scrape a YouTube channel. URL was wrong. it failed. it updated memory.md with the correct URL pattern so it never makes the same mistake again. you can also save explicitly: "save to memory that my favorite testing framework is pytest" the agent updates memory.md immediately. this file loads into context on every session. the agent knows you better every week. 3. EPISODIC MEMORY (chat history) stored in ~/.hermes/state.db (local SQLite). every conversation. every tool call. every result. searchable with FTS5 full-text search. "search our past sessions. what was the first thing I ever said to you?" the agent queries state.db and finds it. over time, auxiliary models consolidate episodic memory into semantic memory. distilling recurring patterns into durable facts. THE SELF-IMPROVING LOOP: every agent run follows this cycle: → you send a prompt → working memory loads: SOUL.md + memory.md + relevant skills + chat history → agent calls tools (terminal, browser, delegate_task) → agent completes the task, replies to you → AFTER the reply: agent checks "did I learn something worth saving?" → if yes: updates memory.md or creates a new skill → next session starts smarter than the last this happens automatically. you don't ask the agent to learn. it decides what to remember on its own. WHAT MAKES THIS DIFFERENT FROM CLAUDE CODE: Claude Code has memory too. but Hermes stores everything locally. no cloud. your data never leaves your machine. Claude Code doesn't auto-create skills from experience. Hermes turns repeated workflows into reusable procedures. Claude Code memory is instruction-based. Hermes memory is conversational and self-updating. over months of usage, Hermes builds a knowledge base of your preferences, your projects, your mistakes, and the procedures that work for your specific workflow. the agent that remembers your birthday also remembers why your last deploy failed. NO EMBEDDINGS. PLAIN TEXT. Hermes does not use embeddings or RAG for memory. skill and memory search runs on plain text keyword matching. simpler. faster. no vector database to maintain. works entirely offline on your local machine. DELEGATE TO CLAUDE CODE: Hermes can spawn a sub-agent that runs Claude Code in headless mode: "spawn a sub-agent using Claude CLI to build a Python script that fetches the top 5 Hacker News stories to markdown." Hermes delegates. Claude Code writes the code. result returns to Hermes. Hermes runs the script and delivers the output. use Hermes for orchestration. use Claude Code for heavy coding. both tools. not competitors. WHAT HERMES DOES NOT HAVE: no built-in eval or LMOps system. no LangSmith, no LangFuse integration out of the box. trajectory export and logs exist but there is no automated quality tracking. if you need eval, build it yourself or connect external tools. the loop is self-improving. measuring how well it improves is on you. comment LOOP and I'll send you the configs that control how fast Hermes learns and what it remembers. memory limits, skill auto-creation triggers, and the auxiliary model that runs the learning. Replace your entire team with 8 hermes agents👇

YanXbt

22,720 görüntüleme • 2 ay önce

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.

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,852,130 görüntüleme • 6 ay önce

HERMES AGENT + OBSIDIAN IS A COMBINATION NOBODY IS TALKING ABOUT. Hermes ships with a bundled Obsidian skill. read, search, and create notes in your vault out of the box. why this combination is powerful: Hermes built-in memory is capped. MEMORY.md: 2,200 chars (~800 tokens). USER.md: 1,375 chars (~500 tokens). Obsidian vault has no cap. your agent writes research, session summaries, project context, and learned patterns as linked markdown notes. unlimited depth. the agent creates indexed notes by design. timestamps, backlinks, tags. every note connects to the knowledge graph. three ways to integrate: 1. BUNDLED OBSIDIAN SKILL (simplest) ships with Hermes. reads, searches, creates notes in your vault directly. hermes skills list | grep obsidian 2. OBSIDIAN MCP SERVER (deepest) 30+ tools: full-text search, tag lookup, note management, vault analysis, link analysis, orphan detection. add it via: hermes mcp 3. TELEGRAM + CRON → VAULT (always-on) set a cron job that writes daily summaries, research findings, or task reports directly into your Obsidian vault. your agent feeds the vault while you sleep. you review in Obsidian when you're ready. the unlock: Hermes memory handles what the agent needs to know per session (capped, injected). Obsidian handles everything the agent has ever learned (uncapped, searchable). short-term in Hermes. long-term in Obsidian. both accessible. both persistent. keep the vault scope narrow at first. start with one /Hermes folder. expand once you trust the workflow. 8 Loops Indise Hermes Agent👇

HERMES AGENT + OBSIDIAN IS A COMBINATION NOBODY IS TALKING ABOUT. Hermes ships with a bundled Obsidian skill. read, search, and create notes in your vault out of the box. why this combination is powerful: Hermes built-in memory is capped. MEMORY.md: 2,200 chars (~800 tokens). USER.md: 1,375 chars (~500 tokens). Obsidian vault has no cap. your agent writes research, session summaries, project context, and learned patterns as linked markdown notes. unlimited depth. the agent creates indexed notes by design. timestamps, backlinks, tags. every note connects to the knowledge graph. three ways to integrate: 1. BUNDLED OBSIDIAN SKILL (simplest) ships with Hermes. reads, searches, creates notes in your vault directly. hermes skills list | grep obsidian 2. OBSIDIAN MCP SERVER (deepest) 30+ tools: full-text search, tag lookup, note management, vault analysis, link analysis, orphan detection. add it via: hermes mcp 3. TELEGRAM + CRON → VAULT (always-on) set a cron job that writes daily summaries, research findings, or task reports directly into your Obsidian vault. your agent feeds the vault while you sleep. you review in Obsidian when you're ready. the unlock: Hermes memory handles what the agent needs to know per session (capped, injected). Obsidian handles everything the agent has ever learned (uncapped, searchable). short-term in Hermes. long-term in Obsidian. both accessible. both persistent. keep the vault scope narrow at first. start with one /Hermes folder. expand once you trust the workflow. 8 Loops Indise Hermes Agent👇

YanXbt

20,617 görüntüleme • 2 ay önce

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

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,891 görüntüleme • 5 ay önce

I just built my second brain with Hermes Agent. It remembers people, companies, projects, and decisions. It pulls from meeting notes, docs, anything I feed it, and cites the source every time. It's this repo called Gbrain, open-sourced by Y Combinator president Garry Tan. install it by pasting this into Hermes: "Install Gbrain following the instructions at Set up the embedding provider, then run gbrain init and gbrain doctor to verify." Add the MCP server so Hermes can call it directly: "Add the Gbrain MCP server and reload." The graph builds itself. Pattern matching on the people and companies already in your notes. 31 points more precise than plain vector search, by their own benchmark. The data from the video is made up so I could show you how it works. Hermes' memory remembers our conversations. Gbrain remembers my world. Open source. Runs local, no server, no Docker.

I just built my second brain with Hermes Agent. It remembers people, companies, projects, and decisions. It pulls from meeting notes, docs, anything I feed it, and cites the source every time. It's this repo called Gbrain, open-sourced by Y Combinator president Garry Tan. install it by pasting this into Hermes: "Install Gbrain following the instructions at Set up the embedding provider, then run gbrain init and gbrain doctor to verify." Add the MCP server so Hermes can call it directly: "Add the Gbrain MCP server and reload." The graph builds itself. Pattern matching on the people and companies already in your notes. 31 points more precise than plain vector search, by their own benchmark. The data from the video is made up so I could show you how it works. Hermes' memory remembers our conversations. Gbrain remembers my world. Open source. Runs local, no server, no Docker.

Alvaro Cintas

16,800 görüntüleme • 1 ay önce

Hermes is an AI Harness from Nous Research that is truly yours: you can shape its persona, it remembers you across sessions, and it gets better the longer you use it. We ran it fully local on QVAC. The persona, the memory, the skills it learns, all of it stays on your machine.

Hermes is an AI Harness from Nous Research that is truly yours: you can shape its persona, it remembers you across sessions, and it gets better the longer you use it. We ran it fully local on QVAC. The persona, the memory, the skills it learns, all of it stays on your machine.

QVAC

65,586 görüntüleme • 1 ay önce

I built Caduceus for Hermes Desktop Nous Research Two snakes, one staff Caduceus runs parallel AI agents in perfect sync, on any model you already have It sizes up every task and picks the path: • Easy → answered instantly • Hard → a live to-do plan + agents fanned out in parallel, verified before it calls it done Caduceus has a UI right inside Hermes so you watch every agent build your project in real time Full demo 👇

I built Caduceus for Hermes Desktop Nous Research Two snakes, one staff Caduceus runs parallel AI agents in perfect sync, on any model you already have It sizes up every task and picks the path: • Easy → answered instantly • Hard → a live to-do plan + agents fanned out in parallel, verified before it calls it done Caduceus has a UI right inside Hermes so you watch every agent build your project in real time Full demo 👇

Terp

17,006 görüntüleme • 3 ay önce

ANTHROPIC KILLED THE VECTOR DATABASE AND REPLACED IT WITH A FOLDER no embeddings. no black-box retrieval. no special memory tools. the agent just reads and writes a folder the insight: your agent already knows how to use a filesystem. so Anthropic made long-term memory a directory of small markdown files, mounted straight into the agent's sandbox at /mnt/memory the agent manages it with the tools it already has, bash, read, write, edit, grep, and Anthropic auto-injects a note into the system prompt so the agent always knows the memory is there and where to look the result: > every change is an immutable version: full audit trail, point-in-time recovery, redaction > read-only or read-write per store, so many agents can safely share one memory > workspace-scoped and persistent, memory that survives every session end most teams bolt on a vector DB and pray retrieval works. Anthropic went the opposite way: compiled knowledge as plain, human-readable files you can open, diff, and edit yourself and there's a second layer. Anthropic's "Dreaming" runs offline, reviews past sessions and the store, and rewrites it into a cleaner, higher-signal version. the agent literally consolidates memory in its sleep. bookmark this. the most production-grade agent memory right now is just a well-organized folder, and Anthropic proved it.

ANTHROPIC KILLED THE VECTOR DATABASE AND REPLACED IT WITH A FOLDER no embeddings. no black-box retrieval. no special memory tools. the agent just reads and writes a folder the insight: your agent already knows how to use a filesystem. so Anthropic made long-term memory a directory of small markdown files, mounted straight into the agent's sandbox at /mnt/memory the agent manages it with the tools it already has, bash, read, write, edit, grep, and Anthropic auto-injects a note into the system prompt so the agent always knows the memory is there and where to look the result: > every change is an immutable version: full audit trail, point-in-time recovery, redaction > read-only or read-write per store, so many agents can safely share one memory > workspace-scoped and persistent, memory that survives every session end most teams bolt on a vector DB and pray retrieval works. Anthropic went the opposite way: compiled knowledge as plain, human-readable files you can open, diff, and edit yourself and there's a second layer. Anthropic's "Dreaming" runs offline, reviews past sessions and the store, and rewrites it into a cleaner, higher-signal version. the agent literally consolidates memory in its sleep. bookmark this. the most production-grade agent memory right now is just a well-organized folder, and Anthropic proved it.

NO1ennn

13,359 görüntüleme • 28 gün önce

Martin Keen from IBM just explained the one thing separating "chatbot users" from $300K AI architects > most people use Claude Opus 4.8 as a temporary tool -> the pros build it a permanent memory it's called the CoALA framework. the 4 layers your agent actually needs: > Working Memory - the context window. fast but resets every session. this is the RAM, not the brain > Semantic Memory - your knowledge base. CLAUDE.md, rules, facts the agent never forgets regardless of session > Procedural Memory - skills. workflows and instructions that load only when a specific task begins > Episodic Memory - past lessons. the agent remembers every bug it fixed yesterday so it doesn't repeat it today if your agent doesn't have all four, it's a fancy autocomplete the 2026 job market isn't looking for prompt engineers > it's looking for people who can build AI brains - and the ones doing it now aren't waiting for job postings save this or watch someone else use it to get your next raise 👇

Martin Keen from IBM just explained the one thing separating "chatbot users" from $300K AI architects > most people use Claude Opus 4.8 as a temporary tool -> the pros build it a permanent memory it's called the CoALA framework. the 4 layers your agent actually needs: > Working Memory - the context window. fast but resets every session. this is the RAM, not the brain > Semantic Memory - your knowledge base. CLAUDE.md, rules, facts the agent never forgets regardless of session > Procedural Memory - skills. workflows and instructions that load only when a specific task begins > Episodic Memory - past lessons. the agent remembers every bug it fixed yesterday so it doesn't repeat it today if your agent doesn't have all four, it's a fancy autocomplete the 2026 job market isn't looking for prompt engineers > it's looking for people who can build AI brains - and the ones doing it now aren't waiting for job postings save this or watch someone else use it to get your next raise 👇

Mr. Buzzoni

10,442 görüntüleme • 2 ay önce

Hermes agent just left the terminal. 𝗛𝗲𝗿𝗺𝗲𝘀 𝗗𝗲𝘀𝗸𝘁𝗼𝗽 dropped yesterday. native app for macOS, Windows, and Linux. for months Hermes was the agent that learned your projects, wrote its own skills, and built a model of who you are. all of it buried in terminal logs. now it has a window. the important part is that it's not a wrapper. it runs the same agent core, the same sessions, memory, and skills as the CLI. you can start a task in the terminal and finish it in the app without anything resetting. the state is shared across every interface, not copied between them. what the GUI actually adds: → streaming chat that shows live tool calls and inline reasoning instead of a spinner → a preview rail that renders pages, code, and images right beside the conversation → an artifacts panel that collects every file the agent has ever produced → remote gateway mode, so you can point the app at a VPS and run the heavy work elsewhere → skills, cron, profiles, and gateways managed point-and-click instead of through YAML → voice mode, drag-drop files, and inline image generation remote gateway mode is the one worth slowing down on. the agent runs 24/7 on a $5 server while you control it from your laptop like a local app. other agent UIs are chatboxes with a logo. this one shows the autonomy instead of hiding it, so you watch the skills load, the tools fire, and the artifacts pile up as it works. it was teased in Jensen's GTC keynote. MIT licensed, local-first, no telemetry. if you already run Hermes, download it and everything is already there. your chats, memory, and skills carry straight over. i wrote a full masterclass on Hermes Agent that walks through the SOUL. md identity layer, the three-tier memory system, the self-evolving skills loop, and how to run three specialized agents 24/7. desktop is the interface that finally does all of it justice. the article is quoted below.

Akshay 🚀

51,540 görüntüleme • 3 ay önce

A GUY MAKING $100K/MONTH WITH AI JUST SHOWED HIS ENTIRE SETUP. IT'S ONE FOLDER OF NOTES AND NOTHING ELSE no framework. no $500 course. he opens his screen and it's just obsidian - a plain notes app - wired into claude here's what he did: -> he pulled claude's memory files out of their default folder and dumped them into one vault -> had claude rename and merge them: 107 messy files collapsed into 17 clean ones -> every folder gets one master note that links to all the others that last part is the whole trick the agent reads the master note, follows the links and by the time it's done it has read every file in the folder. one instruction, full context here's the part most people miss: everyone's trying to make the AI smarter. he made the AI's memory smaller fewer files, better organized, all linked. the agent isn't scanning hundreds of notes anymore - it walks a path you built that's why his agent actually finishes jobs instead of forgetting what it was doing halfway through then he goes one step further: at the end of every session, the agent writes its own daily note. what it did, when, indexed at the top so it can find it again in seconds so he never re-explains anything. the agent looks up what it already did now he types "create a campaign for this offer" and walks away. it reads the product notes, reads the process notes, and comes back with the campaign done you don't need any of the complicated agent tools people are selling you. you need structure and instructions save this. the people winning with AI aren't using better models. they're just the only ones who bothered to organize what it remembers

A GUY MAKING $100K/MONTH WITH AI JUST SHOWED HIS ENTIRE SETUP. IT'S ONE FOLDER OF NOTES AND NOTHING ELSE no framework. no $500 course. he opens his screen and it's just obsidian - a plain notes app - wired into claude here's what he did: -> he pulled claude's memory files out of their default folder and dumped them into one vault -> had claude rename and merge them: 107 messy files collapsed into 17 clean ones -> every folder gets one master note that links to all the others that last part is the whole trick the agent reads the master note, follows the links and by the time it's done it has read every file in the folder. one instruction, full context here's the part most people miss: everyone's trying to make the AI smarter. he made the AI's memory smaller fewer files, better organized, all linked. the agent isn't scanning hundreds of notes anymore - it walks a path you built that's why his agent actually finishes jobs instead of forgetting what it was doing halfway through then he goes one step further: at the end of every session, the agent writes its own daily note. what it did, when, indexed at the top so it can find it again in seconds so he never re-explains anything. the agent looks up what it already did now he types "create a campaign for this offer" and walks away. it reads the product notes, reads the process notes, and comes back with the campaign done you don't need any of the complicated agent tools people are selling you. you need structure and instructions save this. the people winning with AI aren't using better models. they're just the only ones who bothered to organize what it remembers

Paone

23,833 görüntüleme • 1 ay önce

Shadows of The Shining Exploring the latent space of The Shining is to approach the film as one approaches a memory. Here, artificial intelligence acts as a second consciousness: it does not reproduce — it remembers. It reconstructs The Shining from its traces, its echoes, from what has survived the narrative. The latent space becomes a mental territory, an inner Overlook where the ghosts of the image, the logic of dreams, and the mechanisms of visual memory unfold once again. The aim is to turn the exploration of the latent space into a mnemonic experience of cinema itself.

Shadows of The Shining Exploring the latent space of The Shining is to approach the film as one approaches a memory. Here, artificial intelligence acts as a second consciousness: it does not reproduce — it remembers. It reconstructs The Shining from its traces, its echoes, from what has survived the narrative. The latent space becomes a mental territory, an inner Overlook where the ghosts of the image, the logic of dreams, and the mechanisms of visual memory unfold once again. The aim is to turn the exploration of the latent space into a mnemonic experience of cinema itself.

Benjamin Bardou

37,527 görüntüleme • 10 ay önce

HERMES AGENT SHIPS WITH A BUNDLED SKILL FOR ANDREJ KARPATHY'S LLM WIKI PATTERN. A SELF-IMPROVING KNOWLEDGE BASE THAT GROWS EVERY TIME YOU FEED IT. mentioned this briefly in the overnight workflow article. here is the full breakdown. what it is: a self-improving knowledge base built as interlinked markdown files. unlike RAG (which rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. cross-references stay linked. contradictions get flagged automatically. synthesis reflects everything ingested so far. why this matters for Hermes memory: Hermes built-in memory knows YOU. it remembers your conversations, your preferences, your business context across sessions. but it doesn't know your inbox. or your meeting transcripts. or that article you saved last week. or the expert framework you want it to learn. the LLM Wiki solves that. THE DIVISION OF LABOR human curates sources and directs analysis. agent summarizes, cross-references, files, and maintains consistency. you drop in articles, transcripts, notes. Hermes indexes them, links related concepts, flags contradictions, updates affected pages. your knowledge base grows itself. SETUP IS ONE COMMAND the skill ships with Hermes. enable it. set WIKI_PATH in ~/.hermes/.env: WIKI_PATH=/Users/you/wiki defaults to ~/wiki if unset. then drop anything into it: "index this article into my wiki: [paste URL or text]" Hermes reads it, builds a source page, updates related entries, flags contradictions. THE OBSIDIAN ANGLE set OBSIDIAN_VAULT_PATH to the same directory. now your wiki is visible in Obsidian's graph view. nodes, links, backlinks. all built by Hermes. for headless servers: install obsidian-headless. syncs vaults without a GUI. agent writes from the server, you read on your laptop. THE COMPOUND EFFECT Hermes knows you. the wiki knows your world. combine them and the agent answers questions using BOTH contexts at once. month 1: you explain things twice. month 3: the agent references the wiki on its own. answers get sharper because the knowledge base got sharper. AUTOMATIONS THAT FEED THE WIKI set cron jobs to ingest automatically: "every day at 9am, check Granola for new meetings. add any new transcripts to my wiki under meeting notes." "every morning, scan my Gmail starred items. add anything worth keeping to the wiki." "every week, check arXiv for new papers in [your niche]. summarize and file." your wiki grows while you sleep. Hermes never forgets what gets indexed. THE LIMITATION TO KNOW unlike Hermes memory (which is conversational and lives across sessions), the wiki is a separate knowledge layer. Hermes won't pull from the wiki automatically unless you reference it or save it as a skill. best setup: build an LLM Wiki personality that tells Hermes to consult the wiki when answering strategy questions or domain-specific queries. full HERMES AGENT OVERNIGHT WORKFLOW👇

HERMES AGENT SHIPS WITH A BUNDLED SKILL FOR ANDREJ KARPATHY'S LLM WIKI PATTERN. A SELF-IMPROVING KNOWLEDGE BASE THAT GROWS EVERY TIME YOU FEED IT. mentioned this briefly in the overnight workflow article. here is the full breakdown. what it is: a self-improving knowledge base built as interlinked markdown files. unlike RAG (which rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. cross-references stay linked. contradictions get flagged automatically. synthesis reflects everything ingested so far. why this matters for Hermes memory: Hermes built-in memory knows YOU. it remembers your conversations, your preferences, your business context across sessions. but it doesn't know your inbox. or your meeting transcripts. or that article you saved last week. or the expert framework you want it to learn. the LLM Wiki solves that. THE DIVISION OF LABOR human curates sources and directs analysis. agent summarizes, cross-references, files, and maintains consistency. you drop in articles, transcripts, notes. Hermes indexes them, links related concepts, flags contradictions, updates affected pages. your knowledge base grows itself. SETUP IS ONE COMMAND the skill ships with Hermes. enable it. set WIKI_PATH in ~/.hermes/.env: WIKI_PATH=/Users/you/wiki defaults to ~/wiki if unset. then drop anything into it: "index this article into my wiki: [paste URL or text]" Hermes reads it, builds a source page, updates related entries, flags contradictions. THE OBSIDIAN ANGLE set OBSIDIAN_VAULT_PATH to the same directory. now your wiki is visible in Obsidian's graph view. nodes, links, backlinks. all built by Hermes. for headless servers: install obsidian-headless. syncs vaults without a GUI. agent writes from the server, you read on your laptop. THE COMPOUND EFFECT Hermes knows you. the wiki knows your world. combine them and the agent answers questions using BOTH contexts at once. month 1: you explain things twice. month 3: the agent references the wiki on its own. answers get sharper because the knowledge base got sharper. AUTOMATIONS THAT FEED THE WIKI set cron jobs to ingest automatically: "every day at 9am, check Granola for new meetings. add any new transcripts to my wiki under meeting notes." "every morning, scan my Gmail starred items. add anything worth keeping to the wiki." "every week, check arXiv for new papers in [your niche]. summarize and file." your wiki grows while you sleep. Hermes never forgets what gets indexed. THE LIMITATION TO KNOW unlike Hermes memory (which is conversational and lives across sessions), the wiki is a separate knowledge layer. Hermes won't pull from the wiki automatically unless you reference it or save it as a skill. best setup: build an LLM Wiki personality that tells Hermes to consult the wiki when answering strategy questions or domain-specific queries. full HERMES AGENT OVERNIGHT WORKFLOW👇

YanXbt

30,804 görüntüleme • 2 ay önce

The Man Who Runs CERN Said Something That Nobody Talks About What is CERN doing? You know that feeling when you remember something with complete certainty and then find out it never happened? Not just you. Millions of people. The same specific wrong memory. Shared by strangers who never met and never compared notes. That is the Mandela Effect. Most people treat it as a fun internet thing. But here is what most people are not connecting. The most powerful particle accelerator ever built, a machine designed to smash atoms apart at nearly the speed of light and access dimensions of reality we have never observed — came online in 2008. The Mandela Effect as a documented widespread phenomenon started in 2009. And the man running the experiments said something publicly that year that almost nobody has heard. In this video we get into all of it. The machine. The memories. The quote. And the question that I think deserves a serious answer.

The Man Who Runs CERN Said Something That Nobody Talks About What is CERN doing? You know that feeling when you remember something with complete certainty and then find out it never happened? Not just you. Millions of people. The same specific wrong memory. Shared by strangers who never met and never compared notes. That is the Mandela Effect. Most people treat it as a fun internet thing. But here is what most people are not connecting. The most powerful particle accelerator ever built, a machine designed to smash atoms apart at nearly the speed of light and access dimensions of reality we have never observed — came online in 2008. The Mandela Effect as a documented widespread phenomenon started in 2009. And the man running the experiments said something publicly that year that almost nobody has heard. In this video we get into all of it. The machine. The memories. The quote. And the question that I think deserves a serious answer.

Jordan Chain

54,622 görüntüleme • 11 gün önce

Hermes Agent by Nous Research natively integrates with Give Hermes any URL and find a skill for it in our catalog, or create your own. Watch it find the NASA picture of the day for me.

Hermes Agent by Nous Research natively integrates with Give Hermes any URL and find a skill for it in our catalog, or create your own. Watch it find the NASA picture of the day for me.

Kyle Jeong

91,766 görüntüleme • 3 ay önce

while the self-learning poll runs, here is how to actually look at what your agent has picked up: type '/journey' in Hermes Desktop and enjoy a day-by-day timeline of every skill and memory your agent has learned since day one. it also lists each node, so you can see your interconnected skills and memories.

while the self-learning poll runs, here is how to actually look at what your agent has picked up: type '/journey' in Hermes Desktop and enjoy a day-by-day timeline of every skill and memory your agent has learned since day one. it also lists each node, so you can see your interconnected skills and memories.

witcheer

38,705 görüntüleme • 1 ay önce

Kimi CEO Zhilin Yang: "a smart agent isn't enough - it has to run long Kimi 3 new attention makes the context 10x faster, so the agent never has to stop" here's how built it: step 1 → chase token efficiency, not compute - Muon optimizer, 2x more learning per token step 2 → make context cheap, not just long - new attention runs 10x faster, so the agent never stalls step 3 → let it run 200-300 steps alone - K2 already solves problems its own builders can't step 4 → give it a strong prior - the agent searches less and finds the answer faster step 5 → stop chasing a smarter model - chase one that never has to stop in 26-min talk is him revealing the exact architecture behind K3 and how to properly build agents on it watch & bookmark - start with the article below ↓

Kimi CEO Zhilin Yang: "a smart agent isn't enough - it has to run long Kimi 3 new attention makes the context 10x faster, so the agent never has to stop" here's how built it: step 1 → chase token efficiency, not compute - Muon optimizer, 2x more learning per token step 2 → make context cheap, not just long - new attention runs 10x faster, so the agent never stalls step 3 → let it run 200-300 steps alone - K2 already solves problems its own builders can't step 4 → give it a strong prior - the agent searches less and finds the answer faster step 5 → stop chasing a smarter model - chase one that never has to stop in 26-min talk is him revealing the exact architecture behind K3 and how to properly build agents on it watch & bookmark - start with the article below ↓

codila

11,941 görüntüleme • 1 ay önce