Engram Blog
How we build Engram, what we've learned, and what we'd do differently. Mostly technical, occasionally opinionated.
· 5 min read · import, chatgpt, how-it-works, deduplication
Afraid re-importing your ChatGPT export will double everything? Engram deduplicates by conversation — re-upload as often as you like, and only genuinely new conversations get added. Here's exactly how it works, honestly.
· 8 min read · memory, codex, claude-code, verbatim, comparison
ChatGPT, Claude, and Codex all ship "memory" now — but every one of them stores a compressed summary, not your actual words. Here's the evidence from Codex's own database, why they all work this way, and what verbatim memory looks like instead.
· 7 min read · chatgpt, export, backup, tutorial
Your ChatGPT conversations are locked in one app. Here's how to export your full history, back it up permanently, and make every conversation searchable from ChatGPT, Claude, Cursor, and any AI you use.
· 7 min read · chatgpt, cross-platform, mcp, tutorial
Connect Engram to ChatGPT in 30 seconds. Then connect it to Claude Code, Cursor, or any MCP client. Research in one tool, execute in another — same memory, zero copy-paste.
· 8 min read · team, agents, shared-memory, architecture
A seat on Engram's Team plan doesn't have to be a person. It can be a deploy bot, a support agent, a code reviewer — any AI agent that needs shared context with the rest of your team.
· 7 min read · claude-code, mcp, tutorial
Claude Code resets its context every session. Here's how to add cross-session memory using Engram and the Model Context Protocol, so your agent remembers past decisions, investigations, and context.
· 8 min read · comparison, memory, mcp
A fair comparison of three agent memory servers — Mem0, Zep, and Engram — covering storage models, protocols, search, pricing, and when to pick each.
· 6 min read · cursor, mcp, tutorial
Cursor resets context every session. With one MCP config block, you can give it memory that persists across sessions, projects, and machines — using Engram.
· 9 min read · engineering, cloudflare, architecture
Why we picked D1 + Vectorize + Workers AI over the obvious stacks for Engram, what the latency math looks like, and where the edges of each service actually are.