cmd/claw-bridge/main.go, line 1427-1433 (link)

Duplicate message sent to gateway on lifecycle-error retry

sendMessageOnce fails via two distinct paths: sendReq failure (message never reached the gateway) and inf.done lifecycle error (message was delivered, the LLM returned a transient error). In the second case — which is the exact scenario the retry logic targets — the outer loop calls sendReq a second time with the same message payload. For a stateful persistent session, this sends the user message twice into the conversation context, which could produce double-processing or corrupt the session's turn history. Consider distinguishing the two failure modes and only retrying a full sendReq when the original send itself failed.