---
title: "Long conversations"
description: "How earlier content is handled automatically in a long session."
lang: en
---

In a long conversation, the model can only reference a limited amount of content per turn. To keep the session going, Bi manages history automatically:

- The most recent turns are kept intact
- Earlier content is condensed into a summary that includes your key points, conclusions reached and files changed
- Very old content is dropped

Generating the summary does not consume extra model quota.

## What this means

The longer the conversation, the more likely early details are condensed away. If something still matters, restate it later or start a dedicated session for it.

## Context budget

Every turn has a hard prompt cap. When it is exceeded, stale tool results contract into placeholders so context cannot grow without bound. This is the other side of the same budget mechanism as history summarization: read less irrelevant material and spend the budget on the current task.

## Do you need to configure it?

The handling is automatic. Defaults suit most tasks and rarely need adjustment.

## Related

- [Add a model](/docs/configuration/providers)
- [Sessions](/docs/using-bi/sessions)