A new session. Not a fresh start.

Your users should not have to repeat every preference and decision. Aether gives your agent application a persistent memory layer that can recall useful context after the conversation ends.

Illustrative example

Remember what matters, beyond the transcript.

Conversation history and memory solve different problems. A transcript records the exchange. Aether lets your application store useful facts and retrieve relevant context for a later question, even in a new session.

Carry useful facts forward.

Remember preferences and recurring context so your application can continue a conversation without asking the same introductory questions.

Recall for the question.

Retrieve context related to the current request, rather than adding the entire history to every prompt and hoping the important detail survives.

Keep identities explicit.

Scope memory to the relevant entity. Your application defines whose context it is working with and which information it should store.

Memory you can add to the agent you have.

Use Aether’s remember and recall interface from your application. The memory layer supplies context; your agent remains responsible for deciding what to say and which tools to use.

A closer look at Aether
AetherMemory

Persistent storage beyond an individual session

Entity-scoped semantic recall

First-party TypeScript, Python, Go, and .NET SDKs

Resume a developer’s preferred setup.

A developer tells an assistant they work in TypeScript and prefer short examples. In a later session, the application recalls those preferences before preparing its response.

  1. Store the preferences the application is permitted to retain.

  2. Begin a new session using the same entity identity.

  3. Recall relevant preferences and include them in the response context.

A few useful answers.

How is agent memory different from chat history?

Chat history contains the conversation in sequence. Persistent memory stores context for later retrieval. Your application can use both, while deciding what belongs in long-lived storage.

Will Aether remember everything automatically?

Your integration decides what to supply and when to retrieve it. Plan retention, user expectations, and access before storing personal information. Persistent does not mean every message should become memory.

Can memory include source documents?

Yes. Aether supports document retrieval as well as remembered facts. Use memory for recurring context and source retrieval when an answer should be supported by reference material.

Make the next conversation build on the last.

Talk through your workflow