openclaw-workspace

Summary

A streamlined workspace for managing and configuring OpenClaw AI memory, projects, agents, and tools. This setup enables ongoing business automation, operational memory, configuration management, and project execution, leveraging PowerShell and OpenClaw-compatible extensions.

Included Assets

• AGENTS.md — Workspace onboarding, session procedures, and agent guidelines
• SOUL.md — Core philosophies, boundaries, and assistant persona structure
• MEMORY.md — Executive memory file: curated long-term notes, key users, and project priority
• TOOLS.md — Local configuration, skills setup, environment-specific settings, and integrations
• package.json — Dependency management (notably @martian-engineering/lossless-claw)
• memory/* — Daily logs, project files, plugins/skills inventory, and operational JSON state, including:
  • Daily records: 2026-03-21.md to 2026-03-25.md
  • Project folders & plans (e.g., ai-sales-agent-startup.md, EXPLOSIVE-FIND.md, etc.)
  • Plugin/skill lists (PLUGINS-SKILLS-INVENTORY.md)
  • System heartbeat state (heartbeat-state.json)

How to Use

1. Session Startup

   • Review SOUL.md to understand the AI assistant's foundation and style.
   • Follow the workflow in AGENTS.md: check the session context, recent logs, and main memory as required.
   • New days/sessions: Check files in memory/YYYY-MM-DD.md for latest activity and update as needed.

2. Long-Term Memory Management

   • Log notable decisions, missions, and critical user context in MEMORY.md.
   • Use daily memory/YYYY-MM-DD.md files for detailed, high-frequency records.

3. Project and Tooling Organization

   • Store and iterate on active projects within memory/projects/.
   • Customize environment specifics in TOOLS.md—add credentials, devices, preferred voices, and service integrations (e.g., Notion).

4. Dependencies

   • Manage or update workspace dependencies via package.json (e.g., @martian-engineering/lossless-claw).
   • Add, modify, or remove skills and plugins as listed in memory/PLUGINS-SKILLS-INVENTORY.md.

5. Operational Updates

   • Track system heartbeat and automation job status using memory/heartbeat-state.json.
   • Prioritize actionable items and immediate project steps by referencing files like IMMEDIATE-ACTIONS.md.

Notes

• Always write important information into memory files; do not rely on "mental notes."
• Maintain strict user privacy and security boundaries as set in SOUL.md and MEMORY.md.
• All public content and documentation should remain in English.
• Avoid group chat leakage: Only use long-term memory (MEMORY.md) in main user sessions.
• Keep TOOLS.md up to date with integration tokens and device information; do not store sensitive keys in committed files.
• Periodically review and distill daily memory files into curated long-term memory (MEMORY.md).

This workspace is meant for continuous refinement and autonomy. Adapt configuration, notes, and projects as operational needs evolve.