Fresh start - excluded large ROM JSON files
This commit is contained in:
OpenClaw Agent
194
memory/2026-02-23.md
Normal file
194
memory/2026-02-23.md
Normal file
@@ -0,0 +1,194 @@
|
||||
# 2026-02-23
|
||||
|
||||
## Monday Morning System Status
|
||||
|
||||
**Overnight Jobs (All Successful):**
|
||||
- Supermemory Backup: 2 AM ✅
|
||||
- Cron Cleanup: 3 AM ✅
|
||||
- Memory Worker: 3:04 AM ✅ (11 items extracted from 2026-02-22)
|
||||
- Daily News Brief: 8:02 AM ✅
|
||||
- Job Verifier: 9:02 AM ✅
|
||||
|
||||
---
|
||||
|
||||
## Fixes Applied Yesterday (Now Verified Working)
|
||||
|
||||
### 1. Compaction Config Fix
|
||||
- **Changed:** `mode: "safeguard"` → `mode: "default"`
|
||||
- **Added:** `reserveTokensFloor: 40000`
|
||||
- **Result:** Auto-compaction now triggers at 40k tokens instead of failing silently at ~180k
|
||||
- **Status:** Active on all new sessions
|
||||
|
||||
### 2. Job Verifier Cron ID Fix
|
||||
- **Problem:** Verifier checked wrong News Brief ID (`623e` instead of `423e`)
|
||||
- **Effect:** False "FAILED" warnings every morning
|
||||
- **Fix:** Updated cron job payload with correct ID
|
||||
- **Verification:** 9:02 AM report showed all 4 jobs ✅ SUCCESS (no false warnings)
|
||||
|
||||
---
|
||||
|
||||
## Discord Session Compaction Issue
|
||||
|
||||
**Problem:** Session `e97798a4-4139-4f32-b3d3-fae43947361e` (#home-assistant) hit 256k/256k (100%) with 0 compactions
|
||||
|
||||
**Investigation:**
|
||||
- Config fix applies to NEW sessions
|
||||
- Existing sessions that were already full don't auto-compact
|
||||
- Manual `/compact` timed out due to full context
|
||||
|
||||
**Resolution:** Session was manually compacted via restart/flush
|
||||
|
||||
**Lesson:** Config changes only affect future sessions; existing full sessions need manual intervention
|
||||
|
||||
---
|
||||
|
||||
## Memory Worker Extraction (2026-02-22)
|
||||
|
||||
**11 items extracted and stored in SQLite:**
|
||||
- 2 bugs (compaction safeguard mode, job verifier ID)
|
||||
- 4 action items
|
||||
- 5 system status entries
|
||||
|
||||
**Database:** `~/.openclaw/memory.db` updated successfully
|
||||
|
||||
---
|
||||
|
||||
## F1 News Brief Policy
|
||||
|
||||
Reminder: Strict NO SPOILERS policy enforced
|
||||
- ✅ OK: Pre-race previews, testing updates, technical news, driver announcements
|
||||
- ❌ NEVER: Race results, winners, podium, standings, qualifying results
|
||||
|
||||
---
|
||||
|
||||
## Next Actions
|
||||
|
||||
- Monitor compaction on new sessions (should trigger at 40k tokens)
|
||||
- Verify Job Verifier continues reporting correctly
|
||||
- Create daily memory file each morning for memory worker extraction
|
||||
|
||||
---
|
||||
|
||||
## Chat Platform Decision (2026-02-23 10:00 AM)
|
||||
|
||||
**Decision:** Stick with Discord ✅
|
||||
|
||||
**Background:** Discord rolled back ID verification requirements
|
||||
|
||||
**Result:**
|
||||
- ❌ **CANCEL:** Zulip self-hosted (Docker experiment abandoned)
|
||||
- ❌ **CANCEL:** Rocket.Chat (working but unnecessary)
|
||||
- ❌ **CANCEL:** All self-hosted chat server experiments
|
||||
- ✅ **KEEP:** Discord primary platform
|
||||
- ✅ **KEEP:** GLaDOS voice bot (separate project, still operational)
|
||||
|
||||
**Next Steps:**
|
||||
- Fix bot permissions to enable slash commands
|
||||
- Update MEMORY.md index
|
||||
- Update Obsidian vault
|
||||
|
||||
**Reasoning:** Discord works, user base is there, no migration friction. Self-hosted options were exploratory; not worth operational overhead given Discord policy reversal.
|
||||
|
||||
---
|
||||
|
||||
## Discord Bot Permissions Fixed (2026-02-23 12:36 PM)
|
||||
|
||||
**Problem:** Slash commands (`/compact`, `/status`) not working; agent not responding when `users` whitelist enabled
|
||||
|
||||
**Root Cause:** OpenClaw dual-whitelist design issue
|
||||
- `users` at guild level → enables slash commands
|
||||
- But ALSO blocks agent message processing → agent stops responding
|
||||
- `channels.allow: true` at channel level → required workaround to re-enable responses
|
||||
|
||||
**Working Config:**
|
||||
```json
|
||||
"guilds": {
|
||||
"1465924568119251006": {
|
||||
"users": ["458667380332036117", "1465926559134257294"],
|
||||
"channels": {
|
||||
"1466074219829006599": { "allow": true }
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**Result:**
|
||||
- ✅ Slash commands working (`/compact`, `/status`)
|
||||
- ✅ Agent responds to messages
|
||||
- Config documented in TOOLS.md and Obsidian
|
||||
|
||||
**Bug:** This is a design issue — `users` whitelist shouldn't break agent responses. Both layers required until fixed.
|
||||
|
||||
---
|
||||
|
||||
## Obsidian Sync Automation (2026-02-23 1:10 PM)
|
||||
|
||||
**Setup:**
|
||||
1. Created note: `OpenClaw/Discord Config.md` (full config docs)
|
||||
2. Created sync script: `scripts/sync-obsidian.ps1`
|
||||
3. Cron job: `daily-obsidian-sync` runs daily at 6:00 AM CT
|
||||
|
||||
**Script syncs:**
|
||||
- TOOLS.md → Obsidian
|
||||
- MEMORY.md → Obsidian
|
||||
- Creates daily sync log
|
||||
|
||||
**Job ID:** `7b974006-490b-4a9c-846e-fd2fb39a7d67`
|
||||
|
||||
**Result:** Obsidian stays in sync with OpenClaw config automatically
|
||||
|
||||
---
|
||||
|
||||
## Notes Updated
|
||||
|
||||
- ✅ MEMORY.md — Added Platform Decisions section (Discord/GLaDOS)
|
||||
- ✅ TOOLS.md — Added Discord config + Obsidian setup
|
||||
- ✅ Obsidian — Discord Config note created
|
||||
- ✅ Cron job — Daily sync scheduled
|
||||
|
||||
---
|
||||
|
||||
## OpenClaw Update Crash (2026-02-23 ~2:15 PM)
|
||||
|
||||
**Problem:** `npm update -g openclaw` crashed during update
|
||||
- Removed old version successfully
|
||||
- Crashed before installing new version
|
||||
- No clear error message
|
||||
|
||||
**Fix:** `openclaw install` command
|
||||
- Installs without onboarding
|
||||
- Preserves all existing config, sessions, and files
|
||||
- Clean install that doesn't overwrite current setup
|
||||
|
||||
**Lesson:** Prefer `openclaw install` over `npm update -g openclaw` for updates
|
||||
|
||||
**Note:** Recovery option available if update fails — no need to rebuild from scratch
|
||||
|
||||
---
|
||||
|
||||
## Auto-Summarize Workflow (2026-02-23 ~2:30 PM)
|
||||
|
||||
**Trigger:** `/summarize https://example.com`
|
||||
|
||||
**Works in:** ANY Discord channel (home-assistant, coding, summaries, projects, etc.)
|
||||
|
||||
**Process:**
|
||||
1. Detect `/summarize` + URL pattern
|
||||
2. Fetch content via web_fetch
|
||||
3. Summarize with structured format (tl;dr, features, etc.)
|
||||
4. **SAVE to Obsidian:** `Summaries/[Title].md`
|
||||
5. Respond with summary + "Saved to Obsidian: [path]"
|
||||
|
||||
**Important:**
|
||||
- This is a CROSS-CHANNEL workflow
|
||||
- Works in #summaries, #home-assistant, #coding, etc.
|
||||
- Always saves to Obsidian even if requested from different channel
|
||||
- MEMORY.md updated with "Active Workflows" section for persistence
|
||||
|
||||
**Added to MEMORY.md:**
|
||||
```markdown
|
||||
## Active Workflows (Auto-Execute)
|
||||
| Trigger | Action | Output | Notes |
|
||||
|---------|--------|--------|-------|
|
||||
| `/summarize [URL]` | Fetch → Summarize → Save | `Summaries/[Title].md` | Works in ANY channel. Auto-saves to Obsidian. Confirm with file path. |
|
||||
```
|
||||
Reference in New Issue
Block a user