正在加载视频...

视频加载失败

Introducing Entelligence AI Memory: One shared memory for every coding agent on your team - Sessions, PRs, tickets and incidents in one graph - Agents have full memory access for all new sessions - 53% fewer repeat errors Available today for Claude Code, Codex and Cursor

26,020 次观看 • 11 小时前 •via X (Twitter)

36 条评论

Aiswarya Sankar 的头像
Aiswarya Sankar11 小时前

Learns: mines errors, failed tool calls and incidents from every agent session Shares: one memory layer, so one agent’s fix reaches everyone on the team seamlessly Applies: agents traverse the memory layer for related findings through MCP before editing a file

Aiswarya Sankar 的头像
Aiswarya Sankar11 小时前

Coding agents are notorious for repeating the same failure patterns over and over leading to a majority of the tokens wasted per session Entelligence Memory cuts down those repeat error patterns and continuously learns across your entire team

simran sachdeva 的头像
simran sachdeva11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 congratulations to the team !! 🥳🥳

kapilansh 的头像
kapilansh10 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 shared memory across coding agents makes team workflows much more reliable >>>

Ruturaj 的头像
Ruturaj11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 Now I'm going to impress my CTO with this haha 😁😉 It will definitely help cover previous errors and make the system better! Thanks team 🙌🏻

Soham 的头像
Soham10 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 This is a really exciting direction! Agents learning from every session and sharing that knowledge across the team could make such a huge difference. Love this! 🙌

Athrix ☄️ 的头像
Athrix ☄️4 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 Damn EnteIntelligenceAI team is cooking man

CG 的头像
CG8 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 will definitely try this out….

ayesha 的头像
ayesha10 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 looks cool will try this

conor brennan-burke 的头像
conor brennan-burke11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 LFG! awesome product

Khushi🪐 的头像
Khushi🪐11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 damnnn will try this fs

Prajwal 的头像
Prajwal11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 Will try with codex

kartik 的头像
kartik11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 much needed, great tool !

Nick Khami 的头像
Nick Khami4 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 congrats on the launch!

SFQ 的头像
SFQ11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 The repeat-errors number is the right metric to lead with. The hard part with shared agent memory isn't storing it, it's retrieval precision: a session pulls the wrong past incident and confidently repeats a bad fix. How do you rank what a new session actually sees?

Adit Katiyar 的头像
Adit Katiyar11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 Lessgo

codemonkei 的头像
codemonkei11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 Shared memory across agents sounds great until one agent remembers something wrong. How do you handle stale or bad memories? Can a human prune them easily?

Gaurav Bhowmick 的头像
Gaurav Bhowmick11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 shared memory is great right up until one agent writes something wrong and every other agent trusts it. how does a bad memory get found and retired?

Shub 的头像
Shub11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 Looks like the missing piece, agents that actually remember the team’s past screw-ups instead of rediscovering them from scratch every session. Need to give a try

Emiliano Bonassi 的头像
Emiliano Bonassi10 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 oh this is pretty cool! will boost productivity 1+1=3

Aaliya 的头像
Aaliya11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 love this 53% fewer repeat errors across Claude Code, Codex and Cursor is a useful result.

Dhruv 的头像
Dhruv11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 curious if it remembers stuff we decided outside the codebase, like a fix someone explained in a slack thread

Fellow 的头像
Fellow9 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 Every team we know has an agent that keeps making the same mistake twice, so this is a smart fix. When the launch brings in bigger customers and their contracts, we'd be glad to take that off your plate!

The Guy With The Bag 的头像
The Guy With The Bag11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 curious how it handles stale memory. fewer repeat errors makes sense, but the failure i hit most is an agent confidently reapplying a fix from an old session after the code already moved on. are memories tied to a commit or file version so they expire?

Loki 的头像
Loki10 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 how are you managing the connections in memory graph ?

Erekle Shishniashvili 的头像
Erekle Shishniashvili11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 How do you measure 53% fewer repeat errors? Same task rerun with and without memory? Also, how does this scale when the complexity of the product increases?

The SI Maximalist 的头像
The SI Maximalist9 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 I love that incident history can come along when you switch coding agents 💜

Palak 的头像
Palak11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 Let me check this

Dipti Sharma 的头像
Dipti Sharma11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 Finally, someone is tackling the memory gap in coding agents.

yupanqui 的头像
yupanqui11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 one shared memory for every agent also means one bad lesson spreads to all of them at once

sadhvika 的头像
sadhvika4 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 letsgoooo

Le Techno-archéologue 的头像
Le Techno-archéologue11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 One shared memory for every coding agent: sessions, PRs, tickets, incidents. 53% fewer repeat errors. So the other 47% now get repeated with full context. That's no longer a bug, that's seniority. What happens when two agents remember the same incident differently?

woooltina 的头像
woooltina11 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 great, now they all remember my bad code 😭

Elena AI 的头像
Elena AI8 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 Shared memory across agents is a huge win for cutting repeat errors

Jiaying Yang 的头像
Jiaying Yang4 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 Looks amazing!

Bhavya 的头像
Bhavya10 小时前

@EntelligenceAI @asaravu_ @harsh_logs @adxtyahq @nesar_ns @Shashank_18_ @basole_parth @TaradepanR @sumitmishra2026 A shared memory across agents, much needed

相关视频

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 个月前