tylerrecall

4 ms·

1. 1.▲
   by tylerrecall 10mo ago

   Also happy to discuss the technical architecture - the entire system runs on Supabase + pgvector, with SDKs for Python, TypeScript, and LangChain. Docs are at recallbricks.com. One interesting challenge has been balancing recall speed vs. d
2. 2.▲
   RecallBricks – Persistent memory infrastructure for AI agents(recallbricks.com)

   2 points by tylerrecall 10mo ago|2 comments
3. 3.▲
   by tylerrecall 10mo ago

   Hi HN – I'm the founder of RecallBricks. I built this after repeatedly running into the same issue while building agents: once agents run beyond a single session, memory falls apart. Context disappears, feedback gets lost, and agents s
4. 4.▲
   by tylerrecall 11mo ago

   Interesting approach. The challenge I keep hitting with AI-generated documentation is that it lacks the persistent context of how the codebase actually evolved - the decisions, the "why we didn't do X" knowledge, the patterns
5. 5.▲
   by tylerrecall 11mo ago

   I'm building RecallBricks - persistent memory infrastructure for AI coding tools. The problem: Every time you switch between Cursor, Claude, ChatGPT, your AI forgets everything. You spend half your time rebuilding context instead of co
6. 6.▲
   by tylerrecall 11mo ago

   This is exactly why I'm building persistent memory for AI coding tools. LLMs hallucinate facts partly because they lose context between sessions. When they "remember" your project structure, past decisions, and error patterns