Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug] Gateway restart (SIGTERM) kills active agent sessions, losing context

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

Describe the bug

When executing openclaw gateway restart, the running agent session is killed by SIGTERM. After the gateway restarts, the agent comes back in a fresh session with no context of what was happening before.

This is especially painful when modifying config (e.g. adding cron jobs, editing config) that requires a gateway restart — any active conversation is interrupted and context is completely lost.

To Reproduce

  1. Have an active conversation with the agent
  2. Run openclaw gateway restart (or any operation that triggers gateway restart)
  3. Agent session is killed
  4. Gateway restarts, agent comes back fresh — no memory of what was being discussed

Expected behavior

Gateway restart should either:

  • Gracefully preserve agent session context across restart, OR
  • Provide a "hot reload" mechanism for config changes so restart is not required for common updates (e.g. cron job changes)

Environment

  • OpenClaw version: 2026.3.28 (f9b1079)
  • OS: Linux 5.10.134-19.2.al8.x86_64 (Alibaba Cloud Linux 8)
  • Gateway mode: local
  • Bind: lan

Additional context

Not a crash bug, but a significant UX issue for anyone running OpenClaw interactively. Cron jobs and other config changes should ideally be hot-reloadable without a full gateway restart.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Gateway restart should either:

  • Gracefully preserve agent session context across restart, OR
  • Provide a "hot reload" mechanism for config changes so restart is not required for common updates (e.g. cron job changes)

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug] Gateway restart (SIGTERM) kills active agent sessions, losing context