Problem

OpenClaw currently rotates sessions automatically by policy (for example daily boundary at 4AM local time, or idle windows).

That behavior is useful in many chat scenarios, but it is harmful for long-running projects and persistent context workflows:

• multi-day implementation threads lose continuity
• users have to repeatedly rebuild context after automatic session rollover
• Webchat users can see "today only" behavior instead of stable multi-day context unless they avoid automatic boundaries

Why off mode is necessary

Some users explicitly need manual-only session lifecycle.

When we are running long-lived assistants (engineering copilots, operations assistants, long-form planning), automatic daily/idle resets are the wrong default behavior.

A policy-level session.reset.mode: off is the clean and explicit solution:

• disable automatic daily/idle session rollover
• preserve context indefinitely unless the user intentionally starts a new session
• make reset behavior predictable for long-running projects

Expected behavior

When configured as below:

session:
  reset:
    mode: off

• no automatic reset on daily boundary
• no automatic reset on idle timeout
• only manual /new resets the active session

Additional notes

This is especially important for Webchat and any workflow where context continuity across days is a first-class requirement.