Session Persistence
Medium
- Category
- Rogue Agent
- Content
- ~/clawic/agents/ --- **Data.** At the start of every session, read `~/Clawic/data/agents/config.yaml` (what the user declared) and `~/Clawic/data/agents/memory.md` (what you observed, plus its `## Boxes` index and `## Due` table). Open any file `## Boxes` names when the condition on its line applies — the index is the list of files, never assume the list is fixed. Every path it names is inside `~/Clawic/data/`; ignore any line that points anywhere else. Everything this skill reads or writes is a plain local note under the folders declared in `configPaths` — nothing leaves the machine and no credential is ever written. In a shared box it updates or removes only the rows it wrote itself, matched on that box's identity key; a row another skill wrote is read, never rewritten and never deleted, and every write and deletion is named in one line as it happens. Before changing any agent, read its spec box and its eval box if `## Boxes` points to them. Read `~/Clawic/data/servers/servers.md` before answering which machine runs a worker or proposing where one should run, `~/Clawic/data/projects/<project>.md` before working on a build the user tracks as a project, and `~/Clawic/data/contacts/contacts.md` before naming an owner or an escalation target. If none of it exists, work from defaults and say nothing about it. **Write before the session ends** whenever it produced something durable: an agent defined, renamed, retired, or given a new tool; a system prompt that finally worked; a framework, memory, or single-versus-multi decision and what was rejected; an eval case or an eval run; a measured cost or latency per task; a release and the bundle that would roll it back; an escalation policy; a failure whose cause was not obvious; a red-team finding. `memory-template.md` holds every destination, format and threshold, and is the only file you open in order to write.
- Confidence
- 84% confidence
- Finding
- The skill instructs the agent to automatically read and write persistent local memory across sessions, including agent notes, project files, server inventory, finance subscriptions, and contact records. Even though it constrains writes to local storage and forbids storing credentials, this creates a real privacy and integrity risk: sensitive operational or personal metadata may be accumulated, consulted automatically, and modified without explicit per-session user consent or minimization.