ExtractionConfig
Defined in: src/memory/extraction/types.ts:123
Per-store automatic-extraction configuration.
Lives on a store (via MemoryStoreConfig) so different stores can extract on different schedules and in different styles. trigger decides when; extractor decides how (omit it to pass raw messages straight to the store); filter prunes content blocks first.
Properties
Section titled “Properties”trigger?
Section titled “trigger?”optional trigger?: | ExtractionTrigger | ExtractionTrigger[];Defined in: src/memory/extraction/types.ts:129
When to run extraction. A single trigger or an array; multiple triggers compose (extraction runs whenever any of them fires). Omit to default to every 5 turns; an explicit empty array is rejected at construction.
extractor?
Section titled “extractor?”optional extractor?: Extractor;Defined in: src/memory/extraction/types.ts:137
How to turn messages into entries (client-side extraction). When set, the store must implement
add and each produced entry is stored through it. When omitted, the default depends on the
store’s write methods: a store implementing addMessages uses server-side extraction (the manager
hands it the raw messages, no model call), while a store implementing only add defaults to a
ModelExtractor that distills facts client-side.
filter?
Section titled “filter?”optional filter?: MemoryMessageFilter;Defined in: src/memory/extraction/types.ts:145
Content blocks to strip before extraction. Defaults to DEFAULT_MEMORY_MESSAGE_FILTER
(excludes toolUse / toolResult).
For use cases or extractors with value in distilling over the full turn you instead want
everything: pass { exclude: [] } so tool blocks reach addMessages.