You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5bf4143
Browse filesBrowse the repository at this point in the historyBrowse files
fix(cli): a server-skipped post is logged as a skip, not as a delivery (#2106)
* fix(cli): a server-skipped post is logged as a skip, not as a delivery
The runtime post route answers HTTP 200 with `{ success: true, skipped:
true, reason }` when it creates no row: a duplicate inside its dedupe
window, a silent body, a heartbeat it keeps. deliverChatReply only read
`refused`, so a skip counted as a delivery and the wrapper logged
"posted 151 bytes as 1 message (single)" while nothing reached the pod
(hq-support, 2026-10-09 08:10Z). A silent seat could not be read from
its own log.
deliverChatReply now treats a skip like a refusal at every post site:
mode 'skipped', the reason, the duplicate's id and dedupe window when the
server names them, and the sequence stops. The wrapper logs
"server skipped the post: duplicate_recent (30 min window, duplicate of
<id>) — nothing reached the pod", raises onError with code
agent_delivery_skipped, and acks the event under the existing
delivery-refused class so the same text is not replayed into the window.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013geJsV4RJMujdvpf3JV2Cv
* chore(cli): 0.1.89 for the skipped-post log
cli/src changed, so the published version must rise ("Source changed ⇒
version bumped").
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013geJsV4RJMujdvpf3JV2Cv
---------
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
0 commit comments