Summary

• change gateway busy-input handling so the default behavior is to queue follow-up user messages instead of interrupting the active turn
• preserve continuity across automatic session resets by extracting a compact carryover summary from the previous transcript and injecting it into the next session when appropriate
• flush memory hooks before auto-reset boundaries and keep /stop semantics fresh by suppressing carryover for manual-stop suspensions

Problem / user-visible failures

This fixes two UX failures in the gateway:

1. Incoming follow-up messages interrupted active work too aggressively

   • A user asking for progress, sending a quick follow-up, or receiving a media echo during an active turn could interrupt the model call mid-flight.
   • The gateway already had display.busy_input_mode: queue, but that behavior only applied during restart/stop drain mode, not during ordinary busy turns.
   • Result: users could accidentally cancel the very task they were waiting on.

2. Automatic session reset felt like sudden amnesia

   • After a crash/interruption or other auto-reset boundary, the gateway would open a new session and tell the user the previous conversation history was cleared.
   • If the old session had not yet been distilled into durable memory, the next turn lost continuity even though the user expected the agent to keep going.
   • Result: the agent felt like it “forgot” what it had just been doing.

What changed

Busy-session behavior

• busy_input_mode now governs normal active-session follow-ups, not only restart drain mode.
• Default behavior is now queue, while explicit interrupt config/env still restores the old behavior.
• Added an explicit interrupt phrase allowlist for busy turns so users can still deliberately interrupt without using /stop.
• Kept restart/drain queueing behavior intact.

Auto-reset continuity

• Added reset_context_summary to SessionEntry.
• On auto-reset, SessionStore builds an extractive carryover summary from recent user/assistant transcript turns.
• The next session injects that summary into the system context and updates the user-facing reset notice so it’s clear continuity was preserved.
• Added pre-reset boundary handling to flush memory hooks before the session rolls over.
• Manual /stop suspensions still start truly fresh: no carryover summary is injected for manual_stop suspensions.

Tests

Targeted tests run locally:

• python -m pytest tests/gateway/test_restart_drain.py tests/gateway/test_session_reset_notify.py tests/gateway/test_session_race_guard.py tests/gateway/test_session_model_reset.py tests/gateway/test_async_memory_flush.py tests/gateway/test_clean_shutdown_marker.py tests/gateway/test_command_bypass_active_session.py -q -o addopts=''

Result:

• 74 passed

Notes

• I intentionally did not stage an unrelated local package-lock.json modification.
• The carryover summary is transcript-derived and only used for auto-reset continuity, not for explicit /new resets.