Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

this is f**king insane researchers built a 4-agent coding system that learns from every problem instead of resetting after each run [4 agents, 1 evolving memory] 1. Planner picks the strategy 2. Solver writes the code 3. Oracle verifies the result 4. Hacker tries to break it 5. pass/fail...

10,312 Aufrufe • vor 2 Monaten •via X (Twitter)

43 Kommentare

Profilbild von Gipp 🦅
Gipp 🦅vor 2 Monaten

I found this graph here

Profilbild von sopersone
sopersonevor 2 Monaten

if the system can actually carry lessons from failed runs into the next task without retraining, that's a huge shift for coding agents

Profilbild von Gafae Boran
Gafae Boranvor 2 Monaten

It’s called Claude.

Profilbild von Yarchi
Yarchivor 2 Monaten

Bro this is gold!

Profilbild von Gipp 🦅
Gipp 🦅vor 2 Monaten

bro, you're damn right because I just found out about this recently and I love it so much

Profilbild von delost
delostvor 2 Monaten

the real upgrade is learning between runs

Profilbild von Ridark
Ridarkvor 2 Monaten

Powerful stuff here, sharing with all my friends now

Profilbild von Skaly_Bull
Skaly_Bullvor 2 Monaten

a 4-agent coding system with an evolving memory graph that learns from every bug is the ultimate breakthrough

Profilbild von Gipp 🦅
Gipp 🦅vor 2 Monaten

learning from your mistakes is a very useful feature for agents

Profilbild von Mikadzyki🌙
Mikadzyki🌙vor 2 Monaten

cyberpunk detected

Profilbild von slash1s
slash1svor 2 Monaten

this is for real insane bro..

Profilbild von wast3
wast3vor 2 Monaten

four agents enough to handle all the tasks?

Profilbild von Gipp 🦅
Gipp 🦅vor 2 Monaten

I think so, maybe even 1 agent would be enough

Profilbild von Avid
Avidvor 2 Monaten

This is really nice

Profilbild von Gipp 🦅
Gipp 🦅vor 2 Monaten

Thanks Avid, by the way, have you seen this yet or not?

Profilbild von Avid
Avidvor 2 Monaten

Yes 🙌🏻

Profilbild von Gipp 🦅
Gipp 🦅vor 2 Monaten

this is very cool🫡

Profilbild von shmidt
shmidtvor 2 Monaten

this is genuinely the future of ai right here

Profilbild von Gipp 🦅
Gipp 🦅vor 2 Monaten

In fact, this graph stores almost all the important notes and articles, and its operating principle is similar to obsidian but it's more like a library

Profilbild von Hussain Hashim | Building SundayBack
Hussain Hashim | Building SundayBackvor 2 Monaten

@gippp69 pretty wild. wonder how long til it codes itself out of a job 😂

Profilbild von James Banks
James Banksvor 2 Monaten

This is formalised in Dynamic Contradiction Logic as Multi-Mirror Computing. Shared memory is the mutual projection of each agent’s fractal DCL intelligence. The shared Tapestry is the projection space itself.

Profilbild von Lutchyn
Lutchynvor 2 Monaten

Agents need experience, not just context

Profilbild von Hanako
Hanakovor 2 Monaten

memory turns every solved problem into leverage

Profilbild von marfin
marfinvor 2 Monaten

this is a real evolution in the agent's work

Profilbild von Gipp 🦅
Gipp 🦅vor 2 Monaten

yes, for agents it's a salvation, to be honest

Profilbild von grokked
grokkedvor 2 Monaten

no way its real bruh

Profilbild von pearson
pearsonvor 2 Monaten

graph memory is the ultimate meta

Profilbild von Fokki
Fokkivor 2 Monaten

Every agents knows what to do

Profilbild von Synthra
Synthravor 2 Monaten

The interesting part isn’t the 4 agents. It’s that failures stop becoming expensive resets.

Profilbild von beamnxw ./
beamnxw ./vor 2 Monaten

i need system like that

Profilbild von Bober_smart
Bober_smartvor 2 Monaten

You inspired me to try this

Profilbild von starmex
starmexvor 2 Monaten

bookmarked gipp, ur loop engineering piece pairs perfect with this

Profilbild von Nico
Nicovor 2 Monaten

what's the forgetting mechanism? learning from every run is also how it locks in its own bad habits

Profilbild von Saman Ahmed
Saman Ahmedvor 2 Monaten

The system gets better by changing what it remembers, not what it weighs.

Profilbild von ALEXYZ
ALEXYZvor 2 Monaten

Evolving memory makes multi agent coding feel inevitable.

Profilbild von magsimich
magsimichvor 2 Monaten

i save it

Profilbild von rewind
rewindvor 2 Monaten

memory actually compounds

Profilbild von Gojo Satoru
Gojo Satoruvor 2 Monaten

The interesting shift is that the agents aren’t just collaborating. They’re accumulating institutional memory. If the memory stays reliable, every solved bug becomes a better starting point instead of another cold start. That could matter more than adding another agent.

Profilbild von unicode
unicodevor 2 Monaten

4 agents and 1 memory that's all you need

Profilbild von NeuralDigger
NeuralDiggervor 2 Monaten

Where did it mention it's agent-based? This website existed even before LLMs got this hype. I've been using this website for the last 3-4 years. It was tremendous human coded tool

Profilbild von Francesco
Francescovor 2 Monaten

agents improve the task

Profilbild von MAX
MAXvor 2 Monaten

I should try this out 🤯

Profilbild von Miles S.
Miles S.vor 2 Monaten

i’d read the hacker’s notes first

Ähnliche Videos

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

23,088 Aufrufe • vor 4 Monaten

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,643 Aufrufe • vor 5 Monaten