Memory Manipulation
- Category
- Memory Poisoning
- Confidence
- 80% confidence
- Finding
Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
- Content
md OpenClaw core handles transcript routing and raw history. The gateway owns session transcripts in the agent's state store under `~/.openclaw/agents/<agentId>/` (SQLite from 2026.8.1, JSONL before that), isolates them via `session.dmScope`, prunes them via `session.maintenance`, and exposes `sessions_list`, `sessions_history`, and `session_status` as agent tools, with `sessions_search` added on recent releases. This skill does not replace any of that. If you run multiple users or channels, enable `session.dmScope = "per-channel-peer"` regardless of whether this skill is installed; that is what stops Alice's DMs from leaking into Bob's session at the routing level. **Goals.** From 2026.5.31, OpenClaw has a per-session goal: one durable objective set with `/goal`, visible to the model through the goal tools, surviving restarts, with explicit pause, block, complete, and clear states. The goal is the right home for "what this session is trying to achieve". This skill does not duplicate it. If the user states an objective and your version has `/goal`, suggest setting the goal and log the decision to pursue it; the session file then holds the decisions, corrections, and constraints that accumulate while the goal is pursued. **Session state awareness.** Recent releases keep a metadata-only change log per session (`session_status` with `changesSince`) that tells a session when a human or another agent intervened. It never carries message content, so it cannot replace a decision log, but it is the first thing to check during recovery in a multi-actor session.
