Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

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 görüntüleme • 3 ay önce •via X (Twitter)

31 Yorum

Hasan profil fotoğrafı
Hasan3 ay önce

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

Hasan profil fotoğrafı
Hasan3 ay önce

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.

Hasan profil fotoğrafı
Hasan3 ay önce

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.

Hasan profil fotoğrafı
Hasan3 ay önce

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:

Hasan profil fotoğrafı
Hasan3 ay önce

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

Abdul Sarfraj profil fotoğrafı
Abdul Sarfraj3 ay önce

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

NOVA profil fotoğrafı
NOVA3 ay önce

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

Max profil fotoğrafı
Max3 ay önce

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

Justin Brave💡 profil fotoğrafı
Justin Brave💡3 ay önce

Amazing share

Jaxon profil fotoğrafı
Jaxon3 ay önce

Awesome

Erina | AI Tools & News profil fotoğrafı
Erina | AI Tools & News3 ay önce

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.

Sagar Rahangdale profil fotoğrafı
Sagar Rahangdale3 ay önce

Quick install and it just works. No complicated setup

Swati Gupta profil fotoğrafı
Swati Gupta3 ay önce

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

pushkar soni profil fotoğrafı
pushkar soni3 ay önce

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

Evaa AI profil fotoğrafı
Evaa AI3 ay önce

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

安叫兽|Bird🕊️ 🔶 BNB profil fotoğrafı
安叫兽|Bird🕊️ 🔶 BNB3 ay önce

来回交代背景真的挺磨人

Rimsha Bhardwaj profil fotoğrafı
Rimsha Bhardwaj3 ay önce

The real problem is not choosing the best agent.

Emma Gomez profil fotoğrafı
Emma Gomez3 ay önce

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

Vikas gupta profil fotoğrafı
Vikas gupta3 ay önce

Just tested the cross-device part. Worked first try

To vv profil fotoğrafı
To vv3 ay önce

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?

Mehedi Hasan profil fotoğrafı
Mehedi Hasan3 ay önce

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

AnderSon profil fotoğrafı
AnderSon3 ay önce

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

DILESH GAUTAM profil fotoğrafı
DILESH GAUTAM3 ay önce

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

DILESH GAUTAM profil fotoğrafı
DILESH GAUTAM3 ay önce

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

Oleksandr profil fotoğrafı
Oleksandr3 ay önce

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

Evana_AI profil fotoğrafı
Evana_AI3 ay önce

Amazing

Shubham Singh profil fotoğrafı
Shubham Singh3 ay önce

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

Saman Ahmed profil fotoğrafı
Saman Ahmed3 ay önce

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

David Marco profil fotoğrafı
David Marco3 ay önce

Awesome share

Poonam profil fotoğrafı
Poonam3 ay önce

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

Jonson profil fotoğrafı
Jonson3 ay önce

Great share

Benzer Videolar

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