Files
buzz/.github
Salman Mohammed 4d08194ea9 Deduplicate thread context by ACP session delivery (#7620)
## Summary

Buzz can repeat a thread reply in later prompts after the provider
already received that event as context. The old fix treated every
message signed by the agent key as retained by the current provider
session. That could hide an unseen heartbeat reply because independent
sessions share the same signing key.

This PR now removes only exact event IDs already delivered to the live
ACP session. It uses bounded overfetch so removed events do not shrink
the new-context window, and it preserves unseen same-key replies from
other sessions.

The context header reports `truncated=true` whenever session history was
omitted. The harness calls `/count` only when the relay query finds a
sentinel beyond its fetch window.

This deliberately does not parse event IDs from shell output. A reply
that the agent just published may appear once in the next context delta;
after that event reaches the provider as context, later prompts omit it.

---------

Signed-off-by: Salman Mohammed <smohammed@squareup.com>
2026-09-15 10:24:27 -04:00
..
2026-07-09 12:16:51 -04:00