Remembrall has shut down

By Tyler Mayberry · 1 October 2026 · Not affiliated with Reducto or the original Remembrall

If a link brought you here from LangChain's docs or the Remembrall repository: the long-term memory API that lived at this address went offline in August 2024. Its dashboard, sign-in, API keys and stored memories went with it, and nothing on this site can sign you in.

What Remembrall was

Remembrall described itself as "long-term memory for LLMs": add two lines to your OpenAI call, and replies would be personalised from a user's past conversations or your documents. It began as a prize-winning project at the Modal hackathon in New York and was published by Reducto (Y Combinator, Winter 2024), whose product today is document parsing.

It was a proxy in front of OpenAI's Chat Completions API. You changed the base URL to https://remembrall.dev/api/openai/v1, kept your own OpenAI key in the Authorization header, and added:

• x-gp-api-key: your Remembrall key;
• x-gp-remember: a user ID, usually an email, which turned on memory for that user;
• x-gp-context: a document set uploaded in the dashboard, for retrieval;
• x-gp-short: replayed the last 20 messages as short-term history.

After each call, a GPT-3.5 function call pulled facts out of the conversation and stored them as embeddings. Before the next call for the same user, the five closest memories were added to the prompt. There was a free tier, a $50-a-month Starter plan and, by 2024, an enterprise plan from $2,000 a month.

The Internet Archive last saw the site working on 13 August 2024. By 27 August a domain-parking page had replaced it. I found no public shutdown notice. LangChain's integration page still describes it, with links to the old sign-in and settings pages.

Moving off it

• From LangChain: remove openai_api_base and the x-gp-* headers from ChatOpenAI, and use LangGraph's long-term memory. Keep memories in a Store namespaced by the same user ID you sent as x-gp-remember, save facts during or after each turn, and search the store before replying.
• From a plain OpenAI call, in Python: the closest swap is Mem0's OpenAI-compatible client. It has the same chat.completions.create shape, with user_id in place of x-gp-remember, and it saves and recalls facts on each call. From other languages, use Mem0's REST API and add and search memories yourself.
• Document contexts (x-gp-context): these were retrieval over your files, not memory. Any vector store and retriever does that job.

Ways to give an agent memory now

Checked 30 September 2026. All of these can run on your own hardware; the "where it lives" column is where your agent's memories end up.

If you're building an app, Remembrall's job now falls to the first four. If what you wanted was one assistant that remembers you, the last two do it with memory you can open and read in a text editor, because it's ordinary files on the computer the agent runs on.

Memory on a computer you own

A self-hosted agent keeps its memory wherever it runs. Put it on a spare mini PC or old laptop and its notes, history and logins stay in your house, not in someone else's database, which is the failure Remembrall's users ran into. Self-Hosted AI Agent helps you check whether a computer you already have is enough, and Hermes vs OpenClaw compares the two agents above, including how each one remembers.

I set up and support agents on computers people own through my business, Cirlet.

Questions

Sources

• The Remembrall repository: github.com/reductoai/remembrall, including the proxy code.
• The site as archived on 15 September 2023, 13 August 2024 and 27 August 2024.
• LangChain's Remembrall integration page and the pull request that added it.
• Reducto on Y Combinator.
• The memory options' own documentation, linked in the table.