Conversation context compaction
How long Fast and Think threads keep working when context grows. Compaction summarizes older turns automatically.
Conversation context compaction automatically summarizes older messages in long Fast and Think threads so you can keep working without immediately hitting length limits. It preserves key context while freeing space for new questions.
This is not limited to Think mode. Current chat routes enable compaction for both Fast and Think. Beyond runs assemble bounded context per step and do not use the same chat compaction path.
How it works
When a long Fast or Think conversation approaches the route's threshold, compaction can trigger automatically. The product may show a brief status (for example "Compacting our conversation…") while older turns are summarized, then continue the thread.
If compaction is not enough or the route still errors, start a new conversation. Prefer a fresh thread when you switch clients, frameworks, or upload a large new pack.
What happens to history
Compaction summarizes older messages while retaining important details (controls discussed, decisions, open gaps). Recent exchanges stay detailed. You can still reference earlier topics; if something was over-summarized, restate the control ID or decision in your next message.
Best practices
- Use workspaces to separate clients and programs.
- Start a new conversation for unrelated frameworks or project phases.
- Upload core documents early when the whole analysis depends on them.
- For multi-step deliverables, prefer Beyond (guide).