f64353f0b5cf4258e802b6973b2e986b413f31bd
Making the store idempotent stopped redelivery duplicating the inbound record, but nothing consulted that result: respond() saved the message, ignored the fact that nothing had changed, and called the model anyway. The cost was a second billed turn, any tool side effects run a second time, and a second assistant reply appended -- replies carry no upstream reference, so they always get a fresh identity and always append. The stated problem, "a re-delivered update appends a duplicate turn", was only half fixed. PriorReply answers "have I already replied to this?" from the history the caller has already loaded, and the chat path replays that answer instead of regenerating it. A message with nothing after it was never answered -- the turn may have died partway -- so that still runs, since the user is owed a reply. CanonicalMessageID exposes the store's own derivation rather than letting the caller reimplement it, since a lookup that silently never matches is indistinguishable from a message never seen. Refs archie-core-i6q
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
133 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.7%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%