Audit: David #david session reset
Date: 2026-04-08 12:02 PDT
Findings summary
- Verified David's session store path exists at
/Users/vinny/.openclaw/agents/david/sessions/sessions.json. - Verified target key existed before change:
agent:david:discord:channel:1482462276660367492. - Backed up the store to
/Users/vinny/.openclaw/agents/david/sessions/sessions.json.bak-20260408-120146. - Deleted only that one key from
sessions.json. - Verified post-change that the key is absent.
- Left the transcript file untouched:
/Users/vinny/.openclaw/agents/david/sessions/d7f511ab-4077-4592-9626-c8432c2b080d.jsonl.
Verified state
- Store entry count before: 65
- Store entry count after: 64
- Removed keys: only
agent:david:discord:channel:1482462276660367492 - Added keys: none
- Changed keys besides removal: none
- Target entry pointed at session id
d7f511ab-4077-4592-9626-c8432c2b080d - Target entry
updatedAt: 2026-04-01T16:12:11.756-07:00
Why this is the smallest safe fix
- The fault scope was one persisted session key for one Discord channel.
- Deleting only the single store entry avoids touching Discord config, bindings, other David sessions, and Vinny.
- Leaving the old transcript file in place avoids extra cleanup risk. It is now inert unless re-linked manually.
Pending step
- Gateway restart is still pending. Manual file deletion changes disk state, but the running gateway may still hold the session store in memory.
- Exact command, only if Vinny/Pete approves:
bash
openclaw gateway restartRestart impact
- Short interruption to active OpenClaw traffic while the gateway restarts.
- Required if the goal is immediate effect for new messages in
#david, because the running process may still use the old in-memory session map until restart. - After restart, the next message in
#davidshould create a fresh session entry for that channel.
Rollback
bash
cp /Users/vinny/.openclaw/agents/david/sessions/sessions.json.bak-20260408-120146 /Users/vinny/.openclaw/agents/david/sessions/sessions.json
openclaw gateway restart