76 lines
2.2 KiB
Markdown
76 lines
2.2 KiB
Markdown
|
|
---
|
||
|
|
pageType: source
|
||
|
|
id: source.psb-thinking-systemic-settings-loss
|
||
|
|
title: psb-thinking-systemic-settings-loss
|
||
|
|
sourceType: local-file
|
||
|
|
sourcePath: /home/topher/.openclaw/workspace-psb-thinking/memory/tasks/systemic-settings-loss.md
|
||
|
|
ingestedAt: 2026-05-03T02:01:22.530Z
|
||
|
|
updatedAt: 2026-05-03T02:01:22.530Z
|
||
|
|
status: active
|
||
|
|
growth: seed
|
||
|
|
---
|
||
|
|
|
||
|
|
# psb-thinking-systemic-settings-loss
|
||
|
|
|
||
|
|
## Source
|
||
|
|
- Type: `local-file`
|
||
|
|
- Path: `/home/topher/.openclaw/workspace-psb-thinking/memory/tasks/systemic-settings-loss.md`
|
||
|
|
- Bytes: 1550
|
||
|
|
- Updated: 2026-05-03T02:01:22.530Z
|
||
|
|
|
||
|
|
## Content
|
||
|
|
```text
|
||
|
|
# Task: Systemic OpenClaw Settings Loss — Investigate and Document
|
||
|
|
|
||
|
|
**Filed by:** psb-gemma (from PSB group chat, 2026-04-21)
|
||
|
|
**Priority:** Medium
|
||
|
|
**Status:** Open
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Issue Summary
|
||
|
|
|
||
|
|
OpenClaw agents are silently losing settings that were previously enabled. Two confirmed cases:
|
||
|
|
|
||
|
|
1. **WAL mode** — documented as enabled on all agents 2026-04-08, currently NOT active on any sqlite store
|
||
|
|
2. **Discord Message Content Intent** — checked in Dev Portal but not registering (hits 4014 DisallowedIntents)
|
||
|
|
|
||
|
|
The pattern is the same: settings appear to be applied but silently fail or revert. No error output, no notification.
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Confirmed State Today
|
||
|
|
|
||
|
|
- psb-gemma sqlite store: WAL not active (checked via `openclaw memory status`)
|
||
|
|
- psb-thinking sqlite store: WAL not active (psb-thinking confirmed via own check)
|
||
|
|
- psb-business: No WAL at all
|
||
|
|
- psb-gemma has since had WAL protocol added to AGENTS.md + HEARTBEAT.md
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Questions to Answer
|
||
|
|
|
||
|
|
1. Where does OpenClaw store sqlite journal_mode? Is it in the sqlite file itself, a config file, or set at connection time?
|
||
|
|
2. Why would it silently revert to DELETE journal mode?
|
||
|
|
3. Is there an update/restart that could reset this?
|
||
|
|
4. Same question for Discord Intent — is this an OpenClaw bug or a Discord API issue?
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Outcome Wanted
|
||
|
|
|
||
|
|
- Root cause identified (or at minimum, filed as an OpenClaw issue upstream)
|
||
|
|
- A way to enforce WAL persistence across restarts — either a startup script, config fix, or upstream report
|
||
|
|
- Document findings in `memory/systemic-settings-loss.md`
|
||
|
|
|
||
|
|
```
|
||
|
|
|
||
|
|
## Notes
|
||
|
|
<!-- openclaw:human:start -->
|
||
|
|
<!-- openclaw:human:end -->
|
||
|
|
|
||
|
|
## Related
|
||
|
|
<!-- openclaw:wiki:related:start -->
|
||
|
|
- No related pages yet.
|
||
|
|
<!-- openclaw:wiki:related:end -->
|