Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

You probably don’t use just one AI agent anymore. Maybe Codex for coding. Claude Code for research. Cursor for quick edits. Hermes for the rest. Each one is great at something different. But every time you switch, you have to start over — re-explaining your project, preferences, and the...

50,678 Aufrufe • vor 3 Monaten •via X (Twitter)

31 Kommentare

Profilbild von Hasan
Hasanvor 3 Monaten

give every agent a shared memory of you ; try memU free at

Profilbild von Hasan
Hasanvor 3 Monaten

the shift: memU stopped trying to decide what your agent remembers. the agent already knows what matters. memU just handles storage, embedding and retrieval. so what codex learned yesterday, claude code can use today. same memory, different agent, different machine.

Profilbild von Hasan
Hasanvor 3 Monaten

it does not stop at context either. memU can turn a full session log into a reusable skill. your agent learns a deployment flow once, then pulls it back the next time a similar task shows up. and the memory is plain markdown. readable, editable, yours. core logic sits around 500 lines.

Profilbild von Hasan
Hasanvor 3 Monaten

if you run more than one agent, this is worth 2 minutes. send your agent the install skill link and let it wire itself up. try it: github (open source): site: discord:

Profilbild von Hasan
Hasanvor 3 Monaten

I hope you've found this thread helpful. Follow me @Ubermenscchh for more. Like/Repost the quote below if you can:

Profilbild von Abdul Sarfraj
Abdul Sarfrajvor 3 Monaten

This is the kind of tool that actually makes multi-agent workflows practical

Profilbild von NOVA
NOVAvor 3 Monaten

Wait this is actually genius. I’ve been copy-pasting the same project context between Cursor and Claude for weeks

Profilbild von Max
Maxvor 3 Monaten

Anyone else notice it gets better the more you use different agents

Profilbild von Justin Brave💡
Justin Brave💡vor 3 Monaten

Amazing share

Profilbild von Jaxon
Jaxonvor 3 Monaten

Awesome

Profilbild von Erina | AI Tools & News
Erina | AI Tools & Newsvor 3 Monaten

We're moving from single AI assistants to AI ecosystems. The real advantage comes when every tool remembers your preferences and picks up exactly where the last one left off.

Profilbild von Sagar Rahangdale
Sagar Rahangdalevor 3 Monaten

Quick install and it just works. No complicated setup

Profilbild von Swati Gupta
Swati Guptavor 3 Monaten

Love that I can open the memory files and actually read/edit them

Profilbild von pushkar soni
pushkar sonivor 3 Monaten

If you use more than one coding agent, just try it for 10 minutes

Profilbild von Evaa AI
Evaa AIvor 3 Monaten

This is how multi-agent systems should feel — continuous instead of fragmented

Profilbild von 安叫兽|Bird🕊️ 🔶 BNB
安叫兽|Bird🕊️ 🔶 BNBvor 3 Monaten

来回交代背景真的挺磨人

Profilbild von Rimsha Bhardwaj
Rimsha Bhardwajvor 3 Monaten

The real problem is not choosing the best agent.

Profilbild von Emma Gomez
Emma Gomezvor 3 Monaten

Finally someone fixed the “re-explain everything every time” problem

Profilbild von Vikas gupta
Vikas guptavor 3 Monaten

Just tested the cross-device part. Worked first try

Profilbild von To vv
To vvvor 3 Monaten

The context tax between agents is real. I keep a one-page project brief (goals, constraints, decisions) and paste it first whenever I hop tools. Cuts the re-explain loop a lot. Do you keep that brief in-repo, or outside the codebase?

Profilbild von Mehedi Hasan
Mehedi Hasanvor 3 Monaten

The “agents already know what matters” approach is so much better than forced memory systems

Profilbild von AnderSon
AnderSonvor 3 Monaten

This is going to save me so much time switching between tools

Profilbild von DILESH GAUTAM
DILESH GAUTAMvor 3 Monaten

Wait, it turns full sessions into reusable skills automatically? That’s wild

Profilbild von DILESH GAUTAM
DILESH GAUTAMvor 3 Monaten

Shared personal memory was the obvious missing layer. Glad someone shipped it

Profilbild von Oleksandr
Oleksandrvor 3 Monaten

memU finally ends the endless re‑explain loop love the markdown‑editable memory, my agents now share a common brain

Profilbild von Evana_AI
Evana_AIvor 3 Monaten

Amazing

Profilbild von Shubham Singh
Shubham Singhvor 3 Monaten

Just shared the GitHub with my whole team. We’re all multi-agent now

Profilbild von Saman Ahmed
Saman Ahmedvor 3 Monaten

I've been waiting for shared memory more than another model release. Repeating the same context across every agent gets old fast.

Profilbild von David Marco
David Marcovor 3 Monaten

Awesome share

Profilbild von Poonam
Poonamvor 3 Monaten

Turning session logs into reusable skills automatically is such a smart design

Profilbild von Jonson
Jonsonvor 3 Monaten

Great share

Ähnliche Videos

HERMES AGENT CAN SHARE MEMORY WITH CODEX AND CLAUDE CODE THROUGH HINDSIGHT. ONE MEMORY BANK. ONE AGENT REMEMBERS, EVERY OTHER AGENT KNOWS. the problem: you use Hermes for orchestration. Codex for coding. Claude Code for debugging. each has its own memory. switch between them and you explain the same project three times. Hindsight fixes this. one shared memory bank that every agent reads and writes to. tell Codex: "the test color for this project is purple." switch to Hermes. ask: "what test color did I pick?" Hermes answers: "purple." no copy-paste. no re-explaining. instant recall. HOW IT WORKS: Hindsight runs as a Docker container on your machine. self-hosted. your data stays local. an LLM powers the memory processing (retain, recall, reflect). RETAIN: extracts facts from your conversations. entities, decisions, preferences, project context. saved to the memory bank automatically. RECALL: when you ask a question, Hindsight pulls from semantic search, keywords, graph connections, and temporal data. fused into one answer. REFLECT: deeper reasoning layer. connects memories across sessions. identifies patterns in your work. produces observations that get smarter over time. CONNECT TO HERMES: Desktop app: Settings → Memory and Context → switch provider from Namosin to Hindsight. set API URL to your local Docker container. set bank ID. done. CLI: hermes memory setup → select Hindsight. verify: hermes memory status should show: provider: hindsight, installed, available. CONNECT TO CODEX: npx hindsight-coding-agents install codex \ --self-hosted --server this installs lifecycle hooks: initialize memory on session start. recall context during work. retain the session when done. enable hooks in Codex: Settings → Hooks → trust all three. CONNECT TO CLAUDE CODE (same command): npx hindsight-coding-agents install all "all" connects every detected agent on your machine. Claude Code, Codex, Cursor, and others. one command. every agent shares the same bank. TAGS FOR FILTERING: every memory gets tagged by harness (Hermes, Codex, Claude Code) and optionally by project name. in the Hindsight control plane: filter by harness. see only Hermes memories. or only Codex memories. or search across everything. soft partitions inside one bank. not hard walls. cross-reference when you need to. ONE BANK OR MANY: one global bank: solo dev, related projects. all agents share everything. patterns emerge across projects. per-project banks: unrelated codebases. each project gets its own memory. no cross-contamination. your call. start with one. split when projects diverge. KNOWLEDGE PAGES (v0.9.0): Hindsight auto-generates living summaries from your accumulated memories. components, concepts, conventions, decisions. not static docs. projected from real agent conversations. auto-refresh as new memories land. WHAT TO KNOW: self-hosted via Docker. your data never leaves your machine. backup system built in (admin CLI + scheduled exports). works with any LLM (local Ollama, OpenAI, Codex subscription). memory defense: redact or block sensitive content automatically. 33,000+ memories accumulated in ~10 days of normal use.

YanXbt

29,658 Aufrufe • vor 2 Monaten