The Responses API's killer feature for multi-turn conversations: previous_response_id. Instead of resending entire conversation history, you just reference the prior response.
Context Management
The conversation parameter provides an alternative to previous_response_id for automatic history management. store defaults to true — set store=False for zero data retention (use encrypted reasoning for stateless multi-turn).
The chain is a tree
Two responses with the same previous_response_id create two children of one parent. They run independently; neither knows about the other. This is the right primitive for A/B prompt testing, parallel exploration, or 'try both styles and let the user pick' UX flows.
Server-side retention is ~30 days by default. For audit, compliance, or your own analytics, persist a copy of every response — JSONL append-only is the canonical shape. See the Production track on JSONL logging.