Context Engine

Context Engine is a hosted service at app.contextengine.com that gives your AI agents and your human team members one shared memory. Claude, ChatGPT, Cursor and Claude Code save to it as they work and read from it when they start, while the people on your team open the same memory in the app to read it, ask it questions in plain words and add files of their own. You sign in with your email and there is no password; the free plan requires no card. Its main purpose is stated plainly on the site: nobody has to explain the same thing twice. The context gathered by one tool or one person becomes available to every connected tool and every teammate, instead of staying locked inside a single chat history. The problem Context Engine addresses is that every AI tool starts from nothing. Claude Code forgets what you decided yesterday, Cursor does not know what ChatGPT learned this morning, and you end up explaining the same project and the same rules again in every tool and every session. Multiply that across a team and the gap widens: what one person's AI learns stays in that person's chat history, where the rest of the team cannot see it. Important decisions, customer requests and contacts are made once and then lost. Context Engine positions itself as the memory that AI tools and human teams share, so context accumulates instead of being rebuilt from scratch each time a new session begins. Connecting the tools is the first step, and the site describes it as something you do once. You pick the app you use: ChatGPT and Claude take a few clicks from their connectors, Claude Code takes a single command followed by an Authenticate step, and Cursor uses an Add to Cursor link. Anything else that speaks MCP or HTTP connects with a key, so agents and scripts you build yourself can use the same memory. Each connection reaches only the engines you choose, and for the sign-in connectors there is no key to copy or keep safe. After that, memory continues automatically as you work. What gets saved is described in concrete terms: a decision, a customer's request, a new contact. Each memory carries a type, shows which tool saved it and keeps its history. The site's examples label memories as decision, customer, person, note and file, and show entries such as a card retry limit decided in Cursor, a new finance contact saved by Claude, or a database choice saved by Claude Code. Besides what the agents write, you can drop in files yourself, a whole folder or a .zip, so documents like a pricing review sit alongside the decisions they relate to. Memories are organised into engines, which the site defines as a memory with a purpose. You say in a sentence or two what an engine is for, and your AI tools read that purpose to decide what to save where, so a client's decisions land in that client's engine and your own notes stay yours. You can have as many as you need: one for yourself, one per client or project, or one for a team. There are walls between them, because a connection reaches only the engines you tick, each at Can read or Can read and save. A search across engines labels the engine every result came from, and a memory moved to another engine takes its history with it. When a connected tool starts, it does not begin from nothing: it gets a short brief covering what each engine is for, what happened recently and what changed since its last visit. If it needs more than the brief, it searches the memory, matching meaning as well as exact words rather than only literal terms. The person reads the same memory in the app, so what the tools know is always visible to you. The site is explicit that Context Engine is not a chatbot and does not run your agents. Your AI tools do the thinking, and the product is the memory they share. Context Engine also keeps itself in order without manual sorting. It writes summaries, a short account of each day rolled into weeks and months, from what was saved. It links related memories, so people, customers, decisions and files connect to each other and a map shows how. It catches duplicates, so when a tool tries to save something already there under the same name it is pointed to that memory to update instead of creating a second one. Every change records who made it, with which tool, and what the value was before. People can also ask their memory questions in plain words, and every answer names the memories it came from, so the result can be checked against its sources. The outcomes described are practical. If you build with AI, the decision you made with Claude Code on Monday is known to Cursor on Tuesday, so you stop re-explaining your conventions, your stack and why you chose it. For teams, everyone reads the same memories and gets the same answers whichever tool they use, and when someone leaves, what they saved stays in the engine, still credited to them. For people working across several clients, the site suggests one engine per client and a connection of its own for each, and notes that in Claude Code a project-scoped connection keeps each client's repository to that client's memory, so nothing crosses between them. Invitations work on any plan at no cost per person, with owner, admin, member and viewer roles, and you can see every tool that reaches an engine and cut one off in a click. Security and privacy are treated as part of the product. Every engine gets its own database, its own search index and its own running copy of the service on Cloudflare, so it never shares a table with anyone else's data. Your content is sent to models only to answer you; it is not used to train anything, not sold and not used for advertising. Support opens an engine only when you approve a request, for the time it names, and every visit is logged, with a legal or safety duty the one exception. Export gives you one ZIP of Markdown and JSON that opens without the product, deleting an engine is scheduled a day ahead so you can export first, you can choose the EU at setup to keep its database and files there, and two-step sign-in is built in. Enterprise puts Context Engine on your own server for your organisation alone. Pricing is per engine, never per person, and people are free on every plan. Free is $0 forever with 1 agent per engine, up to 3 when friends join, 1 GB of memory and no card required. Pro is $12 per month or $99 a year for 10 agents and 25 GB per engine. Unlimited is $39 per month or $299 a year for every agent you run and 100 GB per engine. Enterprise starts at $6,000 per year on your own server, run by Relote, with single sign-on for your own apps, updates and support included. Every plan lets your AI tools read and save as much as they need; what a plan sets is how many agents connect and how much memory the engine holds, and when memory is full a new memory is refused with the reason while nothing stored is deleted. Relote built and runs Context Engine. In short, Context Engine is shared memory for AI-assisted work rather than another assistant. Your agents keep doing the thinking, and the service makes sure the decisions, people, customers and files they produce stay in one place that every connected tool and every teammate can read, question and take with them.