fix: preserve conversation history on gateway restart by openperf · Pull Request #10060 · openclaw/openclaw

openperf · 2026-02-06T02:40:00Z

This PR fixes issue #10018, where a boot message injected after a gateway restart would create a new session branch, orphaning the previous conversation history.

Problem

When the gateway restarts, it sends a notification message (e.g., "Gateway restarted"). This message was being delivered to external channels (like Slack/Telegram) via deliverOutboundPayloads but was not being written to the session transcript. This caused a gap in the conversation history.

An earlier attempt to fix this involved replacing deliverOutboundPayloads with a full agentCommand run. However, this was an incorrect approach as it introduced significant overhead and unintended side effects (like triggering a full AI agent run for a simple notification).

Solution

This PR implements a lightweight and safe solution by separating the concerns:

Keep deliverOutboundPayloads: The original function for sending external notifications remains unchanged, preserving its low-overhead behavior.
Inject into Transcript: A new, dedicated function writeAssistantMessageToTranscript is introduced. This function is called right before deliverOutboundPayloads and is responsible for writing the restart message directly to the session transcript.

This new function leverages the existing SessionManager to ensure the message is appended correctly to the conversation tree, automatically handling the parentId and preserving the history chain.

This approach cleanly fixes the bug without altering the original notification behavior, ensuring both safety and correctness.

Greptile Overview

Greptile Summary

This PR threads an optional parentId through the restart-sentinel → agentCommand → embedded agent execution path, and adds readSessionLeafId() to read the last transcript entry ID so the gateway’s injected boot message is appended to the existing conversation branch rather than starting a new root after restart.

The new helper mirrors existing transcript tail-reading utilities (readLastMessagePreviewFromTranscript) by scanning a bounded window at the end of the JSONL transcript and returning the last parseable entry with an id.

Confidence Score: 4/5

This PR is close to safe to merge but has a failing/newly-invalid unit test that should be fixed first.
The runtime change is localized and follows existing transcript-reading patterns, but the added test uses the helper with an incorrect storePath argument type, which will make the test unreliable or fail in CI.
src/gateway/session-transcript-leaf.test.ts

greptile-apps

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

src/gateway/session-transcript-leaf.test.ts

openperf · 2026-02-07T10:37:24Z

Hi! This PR is ready for review.
@steipete @Takhoffman Could you help review this when you have time? Thanks!

…TP tools

@steipete

Merged via /review-pr -> /prepare-pr -> /merge-pr. Prepared head SHA: 8ed13fb Co-authored-by: nicholascyh <[email protected]> Co-authored-by: steipete <[email protected]> Reviewed-by: @steipete

- Add 'minimax-api-key-cn' auth choice for Chinese users - Reuse existing --minimax-api-key CLI option - Use MINIMAX_CN_API_BASE_URL (https://api.minimaxi.com/anthropic) - Similar to how moonshot supports moonshot-api-key-cn Tested: build ✅, check ✅, test ✅

openclaw-barnacle · 2026-02-14T16:36:24Z