Oracle Adds Linked Memory to AI Agents So New Facts Can Replace Old Ones

An AI agent that remembers an old delivery promise needs more than a newer search result. It needs to know the promise changed. Oracle’s AI Agent Memory 26.8 adds links between saved records so an agent can retrieve a current fact alongside the history that explains it. The release also adds image-aware memory and controls for managing stored context.

A record can explain another record

Oracle calls the new feature Graph Memory. It connects memory records with directed, named relationships: one record can supersede, refine, support, contradict or duplicate another. In Oracle’s support example, a revised delivery window can supersede an earlier preference. The link gives a future agent a reason to favor the new record, rather than treating two different delivery times as equally current.

A superseded, refined or duplicate memory can become invalid without being deleted. That distinction lets the application retain a trail of what changed. Search still starts with a direct match, but graph-aware retrieval can follow links to bring back related records. Developers can limit how far it follows those links and how many linked results it returns.

Who decides that a fact changed?

Applications can create a link explicitly when a workflow confirms the relationship. A replacement shipment, for instance, could supersede an earlier delivery commitment. That route uses information the application already knows; it does not ask memory extraction to infer what happened.

Oracle also offers automatic linking as memories are extracted. The default mode looks for candidate relationships after writing new memories; another mode presents candidates during extraction. Developers can turn automatic linking off. Oracle says the during-extraction approach can improve relationship quality, but requires more work inside the extraction prompt.

That leaves a judgment at the heart of the feature: a confirmed workflow event and an inferred relationship are not the same kind of evidence. Oracle provides both paths, but its announcement does not establish how accurately automatic linking will identify changed or conflicting facts in a particular application.

The storage changes beneath the feature

Graph Memory needs a database change, not just a new search setting. Managed schema version 13 adds a table and indexes for memory links, fields that track record status, and an Oracle SQL Property Graph over memories and links. Oracle’s companion notebook shows how to create or upgrade the schema for a demonstration. For production startup after migration, Oracle advises requiring an existing schema so upgrades remain deliberate.

The notebook compares ordinary and graph-aware search using a small support scenario. It also shows explicit links before turning to automatic linking. That makes it a way to inspect the new behavior, rather than a demonstration of how every relationship will hold up in a larger memory store.

Pictures and boundaries join the memory store

Version 26.8 also lets applications persist images as document records and search them through supplied descriptions or generated captions. A support screenshot or receipt can therefore become durable context. Oracle says image search does not return the raw image bytes by default, a distinction between finding a relevant image record and sending the image itself back to an agent.

The release also includes metadata scoping, Oracle Deep Data Security integration, persisted summaries and pruning support. Those controls address a different consequence of persistent memory: keeping stored context within an intended scope and manageable over time. The central test for linked memory remains whether an application can preserve useful history while consistently putting the current fact first.