Skip to main content
Control how much prior task output each step receives — pass only what the next task needs instead of the full conversation history.
The user runs a sequential team workflow; each step receives either just the prior task output or the full history, depending on retain_full_context.

How It Works

Quick Start

1

Create tasks with context control

Configuration Options

OptionTypeDefaultDescription
retain_full_contextboolFalseWhen True, pass all prior task outputs; when False, pass only the immediate predecessor’s output

Common Patterns

Pipeline pattern

Each step passes only its own output forward — ideal for large intermediate data:

Checkpoint pattern

Periodically retain full context so a later task can see the full history:

Summarisation checkpoints

Insert a summary task that reads full context, then continue with minimal context:

Best Practices

Map which tasks need full history versus only the previous output before running long workflows. Data-loading steps usually need retain_full_context=False; final synthesis steps often need True.
For workflows with many steps, add periodic summary or checkpoint tasks with retain_full_context=True so downstream tasks can recover context without carrying every intermediate payload.
If later tasks hit context limits, set retain_full_context=False on early heavy tasks and pass summaries instead of raw data.
Pair selective retention with Context Window Management for automatic overflow protection on agents.

Context Window Management

Automatic token management for agents

Workflow Validation

Validation loops with controlled context