Duplicate inbound user turn persistence fixes
Cluster 104653 · gateway. Data as of
1 open item. Fix merged in #105334 on 7 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 6 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #105334. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These issues and PRs address a bug where inbound user turns were being persisted twice—once by the gateway and once by the agent flush—sometimes with mismatched platform_message_id values. Fixes span deduplication logic, error recovery paths, and removal of redundant user echo persistence.
Open issues0
Open PRs1
- PR#79610fix(gateway): platform_message_id 数据库级去重，终止 Telegram 重试循环会话膨胀
Fixes on record
-
#104899 fix(codex): accepted inputs no longer appear twice in session history (#104653)
files:
agent/codex_runtime.py,agent/transports/codex_app_server_session.py,evals/codex_echo/README.md,evals/codex_echo/fixture_server.py,evals/codex_echo/probe.py,tests/agent/test_codex_echo_ownership.py,tests/agent/transports/test_codex_app_server_session.py,website/docs/developer-guide/session-storage.md -
#105334 fix(gateway): error recovery no longer duplicates accepted inputs (#104653)
files:
agent/turn_context.py,evals/gateway_failure_ownership/README.md,evals/gateway_failure_ownership/foreign_writer.py,evals/gateway_failure_ownership/probe.py,gateway/run_turn.py,gateway/run_turn_runner.py,gateway/session_transcript.py,gateway/turn_context.py,hermes_state_messages.py,tests/gateway/test_failure_writer_ownership.py,website/docs/developer-guide/session-storage.md
2 PRs closed without merging
From the close comments: superseded by another PR 1 · won't fix / by design 1
Closed issues · 1
- Closed#104653[Bug]: inbound user turns are persisted twice (gateway + agent flush); platform_message_id is set on one row and NULL on the other
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab