openclaw-workspace

Summary

This workspace provides a well-organized structure and templates for developing agent-based workflows on the OpenClaw platform. It focuses on persistent memory, user configurations, agent personalities, and tooling notes, as well as domain-specific modules for applications such as AI news and financial assistance.

Included Assets

• AGENTS.md – Agent user profiles and configuration
• MEMORY.md – Centralized, long-term memory notes
• SOUL.md – Defines agent personality, boundaries, and guidelines
• TOOLS.md – Environment-specific tool and device mapping
• ai-news/2026-02/README.md – Outline/readme for the AI news module (February 2026)
• finance-assistant/README.md – Documentation for the financial assistant, including workflow and file structure
• Selected node_modules/*/README.md and package.json – Documentation and metadata for third-party dependencies used by the finance assistant

How to Use

1. Agent and Memory Preparation

   • At the start of a session, carefully read SOUL.md (for agent identity) and AGENTS.md (user config and proactive preferences).
   • Review current and previous day entries in memory/YYYY-MM-DD.md for recent activity.
   • If in a direct session with the user, load MEMORY.md for valuable long-term context.

2. Workspace Files

   • Use TOOLS.md to document and update local infrastructure: camera names, SSH hosts, device preferences, etc.
   • Update MEMORY.md and memory/ daily to capture important events, decisions, or learned lessons.

3. Modules & Applications

   • Review module-specific readmes (e.g., ai-news/2026-02/README.md, finance-assistant/README.md) for workflow instructions and file organization per task or domain.
   • For the Finance Assistant, follow the described workflow and use the included scripts and dependency documentation.

Notes

• This workspace is designed to encourage proactive, opinionated agent behavior tailored to the user’s needs.
• Persistent memory and continuity are achieved through structured files rather than long-running context.
• Tooling and environment specifics are kept in TOOLS.md to ensure separation between generic skills and user-specific infrastructure.
• The node module directories under finance-assistant/ include third-party libraries required for project execution and may reference their respective documentation for deeper usage details.
• Always treat the provided context files as authoritative—update them as your workflow evolves.