Problem
There are three ways to reset a session in OpenClaw:
- Manual:
/new or /reset command — triggers session-memory hook ✅
- Idle timeout:
session.reset.idleMinutes — does NOT trigger session-memory ❌
- Daily reset: default 4:00 AM — does NOT trigger
session-memory ❌
The hooks system only listens for command:new and command:reset events, but idle timeout and daily reset are gateway-internal mechanisms that don't fire these events.
Expected Behavior
When a session is automatically reset (idle or daily), the session-memory hook should save the session context to memory, just as it does for manual /new//reset.
Suggested Fix
- Add
session:idle_reset and session:daily_reset events to the hooks system
- Have
session-memory hook respond to these events as well, OR
- Document clearly that automatic resets do not preserve context
Workaround
Currently no workaround — users lose session context when idle timeout or daily reset fires.
Additional Context
- OpenClaw version: 2026.3.13
- Hooks documentation: docs/automation/hooks.md
Problem
There are three ways to reset a session in OpenClaw:
/newor/resetcommand — triggerssession-memoryhook ✅session.reset.idleMinutes— does NOT triggersession-memory❌session-memory❌The hooks system only listens for
command:newandcommand:resetevents, but idle timeout and daily reset are gateway-internal mechanisms that don't fire these events.Expected Behavior
When a session is automatically reset (idle or daily), the
session-memoryhook should save the session context to memory, just as it does for manual/new//reset.Suggested Fix
session:idle_resetandsession:daily_resetevents to the hooks systemsession-memoryhook respond to these events as well, ORWorkaround
Currently no workaround — users lose session context when idle timeout or daily reset fires.
Additional Context