openclaw_mirror
Summary
This workspace is a structured mirror of OpenClaw's key setup and operational documentation, providing clear, actionable instructions for managing agents, tools, memory systems, and specialized operational routines. It consolidates essential guides for onboarding, agent behavior, tooling, and daily operations.
Included Assets
-
Core Agent, Memory, and Personality Files
AGENTS.md– Agent operating rules and onboarding.MEMORY.md– Long-term, curated memory and key configuration notes.SOUL.md– Persona, communication rules, and voice guidelines.TOOLS.md– Custom tooling and environment notes.
-
Operational and Specialized Subsystems
ops/multi-agent-v1/README.md– Multi-agent team setup instructions.ops/telegram-send-monitor/README.md– Telegram send monitor setup and usage.ops/workspace-mirror/README.md– Workspace mirroring to private GitHub instructions.shared/README.md– Shared asset guidelines.telegram-account-export/README.md– Telegram message export via Telethon.
-
Memory Logs
memory/YYYY-MM-DD.md– Dated, session-based memory and daily logs.
How to Use
-
Agent Startup
- Follow
AGENTS.mdfor manual file reading order and session startup rules. - Core files (
SOUL.md,USER.md,IDENTITY.md,MEMORY.md) are injected by the runtime; do not reload manually.
- Follow
-
Memory System
- Review
MEMORY.mdfor curated key facts, configuration references, and system-wide records. - Check dated
memory/files for daily notes and decisions.
- Review
-
Persona & Communication
- Consult
SOUL.mdfor agent voice, brevity rules, and direct response guidelines. - Ensure all communication and actions follow outlined persona and boundaries.
- Consult
-
Tooling
- Reference
TOOLS.mdfor environment-specific setups, secret paths, devices, and local notes.
- Reference
-
Operational Components
- For multi-agent setups, Telegram monitor, or workspace mirroring, see the respective
ops/subdirectory readmes for clear, step-by-step setup and usage.
- For multi-agent setups, Telegram monitor, or workspace mirroring, see the respective
-
Memory Export
- Use
telegram-account-export/for exporting Telegram messages; see its README for architecture and setup specifics.
- Use
Notes
- All sensitive credentials/secrets are path-referenced only; keys themselves are not stored in this workspace.
- Readme files in ops/ and shared/ subfolders provide operational details unique to each subsystem.
- Some operational steps (e.g., multi-agent Discord token creation, workspace mirror pushes) require manual action and are deliberately not automated.
- For effective usage, adhere strictly to reading and writing protocols in
AGENTS.mdand communication standards inSOUL.md. - Memory logs are routinely updated; consult the latest entries for recent changes or incidents.
- Always follow the exclusion and safety guidelines provided for mirroring or exporting operations to avoid exposing secrets or unnecessary data.
No comments yet.