Feature Request: session-end lifecycle hook for thread sessions
We discovered a gap in session lifecycle management: thread-topic sessions (e.g., We discovered a gap in session lifecycle management: thread-topic sessions (e.g., Slack "New Assistant Thread") end silently when they go inactive. The session-memory hook only fires on /new and /reset — thread sessions that timeout never trigger it.
The problem: An overnight build session (19 commits, ~8,800 LOC across 5 phases) completed in a Slack thread, but the orchestrator main session had zero awareness until the next morning. No memory was flushed from the thread session.
Proposed solution: A session-end (or session-close) lifecycle hook that fires when any session ends, including thread-topic sessions going inactive/timing out. Should receive context about the ending session (session key, channel, thread ID, message count, duration) so downstream processing (memory flush, orchestrator notification) can act on it.
Current workaround: Extended heartbeat lookback windows (activeMinutes: 1440) and git commit scanning to detect work from sessions that ended without hooks firing. Works but is polling-based.
GitHub issue with full details: https://github.com/openclaw/openclaw/issues/36816
Setup: OpenClaw 2026.3.2, Slack (socket mode), multi-agent architecture with orchestrator + worker agents.
Would love to hear if others have hit this or if there's an existing pattern we're missing!
The problem: An overnight build session (19 commits, ~8,800 LOC across 5 phases) completed in a Slack thread, but the orchestrator main session had zero awareness until the next morning. No memory was flushed from the thread session.
Proposed solution: A session-end (or session-close) lifecycle hook that fires when any session ends, including thread-topic sessions going inactive/timing out. Should receive context about the ending session (session key, channel, thread ID, message count, duration) so downstream processing (memory flush, orchestrator notification) can act on it.
Current workaround: Extended heartbeat lookback windows (activeMinutes: 1440) and git commit scanning to detect work from sessions that ended without hooks firing. Works but is polling-based.
GitHub issue with full details: https://github.com/openclaw/openclaw/issues/36816
Setup: OpenClaw 2026.3.2, Slack (socket mode), multi-agent architecture with orchestrator + worker agents.
Would love to hear if others have hit this or if there's an existing pattern we're missing!
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
130,529Members
Resources
Similar Threads
Was this page helpful?
