Skip to content
ThinkWork ThinkWork

Memory

Memory is how ThinkWork carries useful context forward without treating every backend as the product.

The clean model is:

  • Threads keep the full record of work
  • Memory decides what context should carry forward into the current turn
  • Agents act on that assembled context

That means Memory is not just one store, and it is not just long-term recall. It is the harness-owned context layer above changing retrieval and memory engines.

What belongs under Memory

Section titled “What belongs under Memory”

Memory in ThinkWork spans four related concerns:

  • Document knowledge for uploaded source material and grounded retrieval
  • Long-term memory for facts and context learned from prior work
  • Retrieval and context assembly for how those pieces reach a turn
  • Structured memory direction for future graph-shaped memory and knowledge

Document Knowledge

Retrieved source material from uploaded documents. Good for policies, runbooks, and reference content.

Long-term Memory

Carry-forward context learned from prior work. ThinkWork exposes one memory contract above pluggable engines.

Retrieval and Context

How thread history, retrieved documents, and recalled memories come together inside a turn.

Structured Memory Direction

Forward-looking direction for richer entity and relationship-aware memory. Roadmap, not current core product surface.

The current product truth

Section titled “The current product truth”

Today, the stable story should be read in this order:

  1. Threads are the record of work
  2. Memory is the context layer
  3. ThinkWork exposes a stable memory contract above memory engines
  4. Document retrieval and long-term recall are implementation paths under that contract

ThinkWork currently supports two long-term memory adapters:

Exactly one long-term memory engine is canonical per deployment.

Short-term and session context still come from thread history. Long-term memory should not masquerade as the thread record.

Why this framing matters

Section titled “Why this framing matters”

This keeps the product honest.

It avoids teaching people that:

  • memory is just another name for RAG,
  • AgentCore or Hindsight are the conceptual model,
  • or long-term memory replaces thread history.

The contract belongs to ThinkWork. Engines implement it.

Read this section

Section titled “Read this section”