Your work is summarised remembered.
Native Context Memory keeps what you’ve said, done and taught in the model itself. Tell it once; it’s there in every session.
Memory and knowledge, kept with the model.
The model provides the intelligence. AdaptiqAI adds memory and your knowledge. Native Context Memory is built to work across open models.
Memory is held by the engine that serves the model. The weights stay unchanged, and your apps share the memory for the model you choose.
Your apps and harnesses
All of them share one memory.
Native Memory
What you’ve done, kept between conversations.
Native Knowledge
Your documents — add, correct or remove them.
Open-weight model
The open model you choose.




Today, nothing is remembered. It is re-read.
It feels as if your AI tools remember. They don’t: the whole conversation is sent again with every message and read from the start, until it no longer fits. That re-reading is one of the reasons token use gets so high.
Without memory
Every message sends the whole conversation again. When it reaches the limit, it is summarised, and the reasons go first.
With Native Context Memory
No more compacting. Only the new message is read. The conversation is already held in memory by the engine that serves the model, so nothing is summarised away.
Work the way you always do.
You write to the model the way you always have, in the harness you already use. Behind it, every moment is kept with its time, and the model recalls the one it needs — from your conversations or your knowledge — without pasting it into the prompt. And you have far more context to work with: up to 5M-token context in each agent session.
See the recall benchmark- Kept with its time
- Recalled, not compacted
- Yours to review, edit or delete
- Add your own knowledge
Let your agent work for hours.
As the work grows, a 1M context window fills up. The context is compacted, the agent loses the thread and comes back to you. With up to 5M-token context in each agent session and no compacting, it keeps the thread from the first ticket to the last.
ExampleWork through 2,000 support tickets
Without Native Context Memory
1M context window. It compacts and asks.
With Native Context Memory
5M-token context. Nothing is compacted.
Four things it is not.And what it does instead.
Techniques it is often mistaken for. Most of them send text along with every call, and finetuning makes a new model.
Not a context window
A context window is how much fits in one call. All of it is sent and processed every time, and when it is full, something is cut.
Native Context Memory is held by the model’s serving engine, not re-sent in the prompt. Nothing is summarised away; when it is full, older conversations stop being recalled first.
Not RAG
Retrieval fetches passages that look like the question. It guesses before the model has seen anything, and what it fetches fills the prompt every time.
Nothing is fetched, so nothing is guessed.
Not finetuning
Finetuning changes the weights and produces a new model. Slow, expensive, and it cannot be taken apart again.
The model stays as it is. The knowledge can be added, edited and removed.
Not memory in an app
Chat products keep their memory inside the app. Change tool, and you start over.
It lives in the API, so every tool you connect to the same workspace and model has the same memory.
The short answers.
Give every tool you use the same memory.
Your agent, your editor and your own scripts draw on one memory. It keeps what you have worked on and what you have taught it, so the next session picks up where the last one left off. You decide what goes in, and you can edit or remove it whenever you like.
- Pi · Monday · savedLaunch: Friday 16 October
- Hermes · Thursday · recalledLaunch: Friday 16 October
Nobody pasted it into Hermes. Both tools read the same memory.