openclaw-workspace

Summary

A structured workspace template for organizing agent, tool, identity, and memory configurations in OpenClaw projects. This setup provides clear separation and persistence of context, daily logs, user and assistant profiles, and environment notes to streamline onboarding and daily operations.

Included Assets

• AGENTS.md — Workspace introduction and session instructions.
• SOUL.md — Defines assistant philosophy, boundaries, and behavior.
• TOOLS.md — Environment-specific configuration, device notes, cheat sheets.
• IDENTITY.md — Profile for the assistant; to be filled during onboarding.
• USER.md — User profile; continually updated based on context.
• HEARTBEAT.md — Task file for heartbeat or periodic checks.
• .openclaw/workspace-state.json — Tracks workspace onboarding state.
• Memory files:
  • memory/2026-03-09.md to memory/2026-03-12.md — Daily logs, actions, context.
  • memory/IDENTITY.md — Assistant persona and settings.

How to Use

1. Start with AGENTS.md

   • Read instructions for session startup, context gathering, and memory handling.

2. Set Up Your Identity

   • Edit IDENTITY.md to define your assistant persona.
   • Fill in SOUL.md to clarify assistant ethos.
   • Update USER.md with user details and relevant context.

3. Configure Tools

   • List devices, scripts, aliases, and any environment-specific info in TOOLS.md.

4. Memory Management

   • Use memory/YYYY-MM-DD.md for daily logs and events.
   • Curate significant context and lessons in MEMORY.md (main session only).
   • Review daily files periodically to update your long-term memory.

5. Periodic Tasks

   • Add or update recurring check tasks in HEARTBEAT.md.

Notes

• Files should be read and updated as part of each main session for continuity.
• Sensitive context in MEMORY.md must be accessed only in direct chats; avoid loading it in group/shared conversations.
• Daily memory files are for raw logs; long-term memory is for distilled, important facts.
• Customize IDENTITY.md and USER.md as you learn more; respect privacy and boundaries.
• Use TOOLS.md to keep local setup and environment details separate from skill definitions.
• Onboarding completion is tracked in .openclaw/workspace-state.json.
• If editing core files (especially SOUL.md), notify the user.

This workspace facilitates efficient agent onboarding, maintains necessary context, and keeps operational notes organized for productive OpenClaw project management.