Загрузка видео...

Не удалось загрузить видео

На главную

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 просмотров • 3 месяцев назад •via X (Twitter)

Комментарии: 31

Фото профиля Hasan
Hasan3 месяцев назад

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

Фото профиля Hasan
Hasan3 месяцев назад

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
Hasan3 месяцев назад

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
Hasan3 месяцев назад

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
Hasan3 месяцев назад

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

Фото профиля Abdul Sarfraj
Abdul Sarfraj3 месяцев назад

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

Фото профиля NOVA
NOVA3 месяцев назад

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

Фото профиля Max
Max3 месяцев назад

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

Фото профиля Justin Brave💡
Justin Brave💡3 месяцев назад

Amazing share

Фото профиля Jaxon
Jaxon3 месяцев назад

Awesome

Фото профиля Erina | AI Tools & News
Erina | AI Tools & News3 месяцев назад

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
Sagar Rahangdale3 месяцев назад

Quick install and it just works. No complicated setup

Фото профиля Swati Gupta
Swati Gupta3 месяцев назад

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

Фото профиля pushkar soni
pushkar soni3 месяцев назад

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

Фото профиля Evaa AI
Evaa AI3 месяцев назад

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

Фото профиля 安叫兽|Bird🕊️ 🔶 BNB
安叫兽|Bird🕊️ 🔶 BNB3 месяцев назад

来回交代背景真的挺磨人

Фото профиля Rimsha Bhardwaj
Rimsha Bhardwaj3 месяцев назад

The real problem is not choosing the best agent.

Фото профиля Emma Gomez
Emma Gomez3 месяцев назад

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

Фото профиля Vikas gupta
Vikas gupta3 месяцев назад

Just tested the cross-device part. Worked first try

Фото профиля To vv
To vv3 месяцев назад

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
Mehedi Hasan3 месяцев назад

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

Фото профиля AnderSon
AnderSon3 месяцев назад

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

Фото профиля DILESH GAUTAM
DILESH GAUTAM3 месяцев назад

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

Фото профиля DILESH GAUTAM
DILESH GAUTAM3 месяцев назад

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

Фото профиля Oleksandr
Oleksandr3 месяцев назад

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

Фото профиля Evana_AI
Evana_AI3 месяцев назад

Amazing

Фото профиля Shubham Singh
Shubham Singh3 месяцев назад

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

Фото профиля Saman Ahmed
Saman Ahmed3 месяцев назад

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

Фото профиля David Marco
David Marco3 месяцев назад

Awesome share

Фото профиля Poonam
Poonam3 месяцев назад

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

Фото профиля Jonson
Jonson3 месяцев назад

Great share

Похожие видео

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 просмотров • 2 месяцев назад