hermes - 💡(How to fix) Fix [BUG] Context compaction causes duplicate responses after compression [1 participants]

TL;DR

Update the agent's logic to ignore summary content and only respond to new messages after the compaction point by adding a COMPACTED_BOUNDARY flag and checking it in the agent prompt.

Guidance

• Add a COMPACTED_BOUNDARY flag in run_agent.py and set it to True after compaction, along with the LAST_PROCESSED_TURN ID.
• Update the agent prompt to check the COMPACTED_BOUNDARY flag and ignore summary content if it's True.
• Ensure the agent only responds to messages with a turn ID greater than the LAST_PROCESSED_TURN ID when COMPACTED_BOUNDARY is True.
• Verify that old tasks in the summary are marked as "already completed" and not re-processed after compaction.

Example

if COMPACTED_BOUNDARY:
    # Ignore summary content and only respond to new messages
    if message_turn_id > LAST_PROCESSED_TURN:
        # Respond to the new message
        pass
    else:
        # Treat the message as already processed
        pass

Notes

This fix assumes that the LAST_PROCESSED_TURN ID is correctly updated after compaction and that the agent's prompt is properly updated to check the COMPACTED_BOUNDARY flag.

Recommendation

Apply the proposed workaround by adding the COMPACTED_BOUNDARY flag and updating the agent prompt, as this directly addresses the root cause of the issue and ensures the agent only responds to new messages after compaction.