Back to Signal Feed
ProductionTracked since May 18, 2026

Revert Codex Stop session-end chaining to prevent early session closure

Release v0.9.20 reverts the v0.9.19 change that chained `session-end.mjs` from Codex `Stop`, because `Stop` can fire before a conversation is truly finished and later observations were being written under an `endedAt`-marked closed record. The hotfix restores `Stop` to summarize-only behavior and keeps the broader SessionEnd-based completion design open in issue #493.

Codex Stopsession-end.mjsendedAtsession tracking

What Happened

  • Release v0.9.20 reverts the v0.9.19 change that chained `session-end.mjs` from Codex `Stop`, because `Stop` can fire before a conversation is truly finished and later observations were being written under an `endedAt`-marked closed record. The hotfix restores `Stop` to summarize-only behavior and keeps the broader SessionEnd-based completion design open in issue #493.
  • Release v0.9.20 reverts the v0.9.19 change that chained `session-end.mjs` from Codex `Stop`, because `Stop` can fire before a conversation is truly finished and later observations were being written under an `endedAt`-marked closed record. The hotfix restores `Stop` to summarize-only behavior and keeps the broader SessionEnd-based completion design open in issue #493.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Rolled back the v0.9.19 behavior where Codex `Stop` triggered the session-end chain, eliminating premature session completion and ensuring late observations are no longer attached to already-ended session records.

Why Track This

Why It Matters

Operators and developers using agentmemory will no longer see conversations marked complete too early, so later assistant observations stay in the active session instead of being stored against a closed one, reducing lost-context incidents and postmortem confusion in production runs. The fix is a targeted rollback: `Stop` again performs summarize-only actions rather than invoking `session-end.mjs`, while the SessionEnd-oriented completion path remains unresolved and should be tracked via issue #493 to ensure real session boundaries are eventually handled without reintroducing early-close regressions.

Impact

Operators and developers using agentmemory will no longer see conversations marked complete too early, so later assistant observations stay in the active session instead of being stored against a closed one, reducing lost-context incidents and postmortem confusion in production runs. The fix is a targeted rollback: `Stop` again performs summarize-only actions rather than invoking `session-end.mjs`, while the SessionEnd-oriented completion path remains unresolved and should be tracked via issue #493 to ensure real session boundaries are eventually handled without reintroducing early-close regressions.

What To Watch Next

  • Watch whether Codex Stop becomes a repeated pattern.
  • Track follow-up changes around Agent Memory and Context Engineering.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: premature_stop_fires_during_active_turns, false_session_completion_records.
Open Topic TimelineOpen Technical EventOpen Original Sourcepremature_stop_fires_during_active_turns / false_session_completion_records / sessionend_solution_still_pending

Supporting Evidence

GITHUB RELEASEHigh Trust

v0.9.20 — hotfix: revert Codex Stop session-end

Revert Codex Stop hook session-end chain so that post-merge field-testing confirms `Stop` could fire before conversation completion, causing premature session completion.