teknium1 77da3bbc95 fix: use correct role for summary message in context compressor ...

The summary message was always injected as 'user' role, which causes
consecutive user messages when the last preserved head message is also
'user'. Some APIs reject this (400 error), and it produces malformed
training data.

Fix: check the role of the last head message and pick the opposite role
for the summary — 'user' after assistant/tool, 'assistant' after user.

Based on PR #328 by johnh4098. Closes #328.

2026-03-08 23:09:04 -07:00

14 KiB

Raw Blame History

View Raw