mirror of
https://github.com/getcompanion-ai/co-mono.git
synced 2026-04-15 19:05:11 +00:00
Clarify messagesToSummarize starts after last compaction
This commit is contained in:
parent
ee0befdfe1
commit
97bbd7a642
1 changed files with 2 additions and 2 deletions
|
|
@ -194,8 +194,8 @@ The `before_compact` event lets you implement custom compaction strategies. Unde
|
|||
|-------|-------------|
|
||||
| `entries` | All session entries (header, messages, model changes, previous compactions). Use this for custom schemes that need full session history. |
|
||||
| `cutPoint` | Where default compaction would cut. `firstKeptEntryIndex` is the entry index where kept messages start. `isSplitTurn` indicates if cutting mid-turn. |
|
||||
| `messagesToSummarize` | Messages that will be summarized and discarded (before cut point). |
|
||||
| `messagesToKeep` | Messages that will be kept verbatim after the summary (after cut point). |
|
||||
| `messagesToSummarize` | Messages that will be summarized and discarded (from after last compaction to cut point). |
|
||||
| `messagesToKeep` | Messages that will be kept verbatim after the summary (from cut point to end). |
|
||||
| `tokensBefore` | Current context token count (why compaction triggered). |
|
||||
| `model` | Model to use for summarization. |
|
||||
| `resolveApiKey` | Function to resolve API key for any model: `await resolveApiKey(model)` |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue