Compact an existing chat
- Open a longer conversation and wait for its active response to finish.
- Use the header control with the tooltip Compact earlier messages into a summary. It becomes available when there is enough history to shorten.
- Watch the inline progress and completion or failure notice. Expand the compacted-messages marker to read the summary, then check that the facts needed for your next request remain clear.
What compaction changes
Notely saves an archive of the conversation before compaction, summarizes older messages using AI, and keeps a recent portion verbatim. Normal compaction keeps the last ten messages; context-overflow recovery may preserve a smaller recent portion.
The active conversation uses the summary in place of the older messages. This uses provider requests and may lose nuance, so keep important requirements in a note or restate them explicitly. The archive is a separate workspace copy; compaction does not provide an in-chat Undo button.
Automatic compaction
With enough history, Notely can compact before the next send when reported input usage exceeds 80% of the configured context window. It can also attempt recovery after a provider reports that the context is too long.
Notely bounds large tool results when possible. A CLI provider can also manage its own context; the displayed context setting cannot raise the provider’s actual model limit.
If the chat is still too large
- Shorten the latest message, remove oversized attachments, or start a focused conversation with a brief and relevant sources.
- Check Context Window and Max Output Tokens Per Turn in Settings → Chat → General and any agent overrides. Input context and response length are different limits.
- If compaction fails, review the inline error and provider connection before retrying. Do not assume a summary contains every detail of the original conversation.