Skip to main content
A context strategy says what happens to the conversation history when the flow moves to a node.

Strategy Types

  • APPEND (default): the new node’s messages are added to the existing context. The full history is kept and the context grows as the conversation goes on.
  • RESET: the context is cleared and replaced with the new node’s messages. Use it when the earlier history is no longer relevant, or would confuse the task at hand.
A third strategy, RESET_WITH_SUMMARY, is deprecated and will be removed in 2.0, and is not available in a flow config. Use Pipecat’s native context summarization instead; to summarize at a transition, push an LLMSummarizeContextFrame in a pre-action.

Global Configuration

The default strategy for every node is set on the FlowManager constructor, in both forms of flow:

Per-Node Configuration

A node can override the global strategy:
A node’s context_strategy is either append or reset. Omit it to use the FlowManager’s strategy.