Dreams

An asynchronous memory-consolidation job that reads a memory store plus a set of session transcripts and writes consolidated memories into an output memory store — a new store by default, or an existing store chosen via output_behavior. The Dreams API is in research preview: the request and response shapes are volatile and may change without the deprecation period that applies to generally-available endpoints.

Failure detail for a Dream whose status is failed.

An input memory store the dream reads from. The dream never mutates this store unless it is also the destination: with output_behavior {type: "update_existing"} the job consolidates this store in place.

An input memory store the dream reads from. The dream never mutates this store unless it is also the destination: with output_behavior {type: "update_existing"} the job consolidates this store in place.

An output memory store the dream writes consolidated memories into.

Model identifier and configuration applied to every pipeline stage. Same wire shape as the Agents API ModelConfig.

Model identifier and configuration applied to every pipeline stage.

An output memory store the dream writes consolidated memories into.

Input session transcripts the dream reads.

Lifecycle status of a Dream.

Cumulative token usage for the dream across every pipeline stage.

The default destination: the job creates a new output memory store as a clone of the memory_store input and writes the consolidated memories into it. The input store is never mutated.

The default destination: the job creates a new output memory store as a clone of the memory_store input and writes the consolidated memories into it. The input store is never mutated.

The job writes the consolidated memories into this existing memory store instead of creating one. In EAP the store must be the job's own memory_store input, so the job consolidates the store in place.