Bounded Prompt History

You can cap runtime prompt history by applying a constant limit to trim older turns, preserving the most recent conversation context while preventing unbounded prompt growth and increasing latency.

Bounded prompt history limits the total conversation turns retained in runtime context. You need it for multi-turn contexts like editor prompts and reviewer summaries where recency matters but total history must remain constrained.

Configure newest-first ordering by enabling the newestFirst parameter in your conversation query function, then apply deterministic sorting in the formatter to ensure prompts remain predictable across runs.

Yes, bounded prompt history works with editor prompts, reviewer summaries, and any multi-turn context where recency matters. It applies a cap constant and deterministic formatting to keep prompts predictable across runs.

Trimming conversation history to a fixed size discards older turns to prioritize recent context. This approach loses earlier conversation details, making it unsuitable when comprehensive historical reasoning across all turns is required.