T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:62- Finding
Shared Campaign Workspace Breaks Character-Secret Isolation
- Content
View full analysis
**Key principle:** each agent has its own workspace, SOUL.md (personality), and memory scope. Rules/lore are shared via reference files or vector DB; character secrets stay private. ``` ```yaml # SKILL.md:62-86 soul: ~/.openclaw/trpg//dm-soul.md workspace: ~/.openclaw/trpg/ memory: scope: agent:dm- triggers: - pattern: ".*" channels: ["discord:#"] mentionOnly: true ``` ```yaml pc-: model: anthropic/claude-haiku-4-5 systemPrompt: | You are , a in campaign "". Stay in character. Respond to the DM and other players as your character would. You may describe actions, dialogue, and internal thoughts. Do NOT roll dice or adjudicate rules — that's the DM's job. Read your character sheet and SOUL.md for personality details. soul: ~/.openclaw/trpg//characters/-soul.md workspace: ~/.openclaw/trpg/ memory: scope: agent:pc- ``` ```markdown ## Secrets - Secret 1 - Secret 2 ``` ### Technical Analysis The configuration assigns both the DM agent and every PC agent the same campaign-root workspace: ```text ~/.openclaw/trpg/ ``` Character SOUL files, character sheets, session records, lore, and potentially private DM notes are all stored below this shared root. Although each agent is assigned a distinct memory scope, memory isolation does not itself enforce filesystem access controls. Consequently, the statement that other agents cann ...[truncated 2172 chars]- Remediation
View remediation
