workspace-file-edit

To edit workspace persona files, you modify SOUL.md, USER.md, and BOOTSTRAP.md to update agent identity, user preferences, and bootstrap configurations. The system requires a plan confirmation before applying any write operations to ensure safe updates.

Modifying SOUL.md and USER.md configurations involves reading the current files first, crafting the new content, and applying it through the Workspace File Edit tool. Changes take effect immediately after write for runtime use.

No, you cannot edit any file freely. The system enforces a strict whitelist of editable files limited to SOUL.md, USER.md, and BOOTSTRAP.md. This restriction ensures only authorized persona and configuration files are modified.

Plan confirmation requires you to approve the proposed changes before the system writes to BOOTSTRAP.md. This gating mechanism reads current files first, then waits for your confirmation to apply the bootstrap guidance updates immediately at runtime.

No, the workspace file editor does not manage MEMORY.md. The memory system continues to manage MEMORY.md automatically, while this skill strictly handles editing SOUL.md, USER.md, and BOOTSTRAP.md files.

Limitations of editing workspace persona files include the strict whitelist restricting edits to only SOUL.md, USER.md, and BOOTSTRAP.md, and the mandatory plan confirmation step required before any write operation can be executed.