Reverse engineering suggests Instinct stores long-term memory in Git-managed Markdown files

Reverse engineering suggests Instinct stores long-term memory in Git-managed Markdown files

N
News Editor
2026-09-21 03:03:39
Supermemory founder Dhravya Shah said his reverse engineering of the personal agent assistant Instinct points to a long-term memory design built around Git-managed Markdown files rather than replaying entire chat logs into context. In Shah’s account, Instinct keeps an up-to-date user state, then uses a separate file-based store for more detailed records such as preferences, decisions, tasks, and person-specific facts. His black-box testing suggested that each conversation begins with a user state summary of about 4,250 tokens, covering background, operating preferences, and communication habits. Shah said he did not find signs of vector indexing or BM25 retrieval. Instead, detailed memory appears to be fetched with keyword search similar to grep, while a background process continuously reorganizes information: temporary details are grouped under tasks, experiences are distilled into long-term preferences, old facts are revised with new ones, and Git preserves version history. He added that the main agent appears to focus on reading memory, while the cleanup and merge work happens in backend workflows that he estimates run about once a day. According to Shah, the setup is close to Supermemory’s own view of how agents should manage memory, and he said the architecture can be largely replicated with Supermemory. He shared an example that used roughly 60 lines of code to plug user profiles, memory search, version history, and continuous updates back into an agent.

Dhravya Shah, founder of Supermemory, said his reverse engineering of the personal agent assistant Instinct suggests the product handles long-term memory with Git-managed Markdown files instead of stuffing full chat histories back into context.

According to Shah, Instinct organizes long-lived information into a file-based system and keeps an updated view of the user’s current state. Supermemory itself is built as long-term memory infrastructure for agents. Shah said it extracts facts from chats, files, and web pages, maintains relationships between people, tracks changes over time, and builds user profiles, then passes relevant memory to agents through APIs, MCP, and related interfaces.

What Shah says he found in Instinct

After breaking down Instinct, Shah said the two systems appear to share a very similar idea of how an agent should remember things.

In his black-box testing, Instinct appeared to receive a user state summary of about 4,250 tokens at the start of each conversation. That summary included life background, operating preferences, and communication habits.

More detailed records — including person-specific facts, preferences, decisions, and tasks — seemed to remain inside Markdown files and were pulled in only when needed through keyword search similar to grep.

Shah said he did not find evidence of vector indexing or BM25 retrieval.

Memory appears to be reorganized in the background

Shah said the memory store is also being continuously reworked behind the scenes. Temporary information is grouped into specific tasks. Experiences are condensed into long-term preferences. New facts overwrite or revise older ones. Git is used to preserve version history.

In that setup, the main agent appears to focus mostly on reading, while the actual organization and merging work is handled by backend processes. Shah estimated that this maintenance cycle runs about once per day.

Supermemory could largely reproduce the design, Shah says

Shah said the architecture can already be largely replicated with Supermemory. In the example he shared, roughly 60 lines of code were enough to reconnect user profiles, memory search, historical versions, and continuous updates to an agent.

Earlier, Reflexion co-author Ashwin Gopinath had speculated that Instinct’s edge might come from continuously maintaining a "current state" that can track what is still valid, what has expired, and what remains unfinished.

Based on Shah’s analysis, that state may not rely on any mysterious database. It may instead sit on top of a file system that is being continuously organized.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
2200

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.