openclaw-workspace
Summary
This workspace provides a structured environment for managing OpenClaw agents, projects, memory, and operational documentation. It supports agent lifecycle, organizational workflow, curated memory, and local environment notes. A basic React dashboard setup is included for interface development.
Included Assets
AGENTS.md: Agent onboarding, session, and memory-management instructions.SOUL.md: Defines the team hierarchy, agent roles, and workflow policies.MEMORY.md: Long-term, curated memory file for context continuity.TOOLS.md: Local environment notes (e.g., device names, SSH hosts).dashboard/: React dashboard (bootstrapped via Create React App).README.mdpackage.json
- Common dependencies under
node_modules/(accepts, body-parser, bytes, call-bind-apply-helpers, call-bound, content-disposition, content-type, etc.).
How to Use
-
Workspace Orientation
- Begin by reading
AGENTS.mdfor agent and session procedures. - Review
SOUL.mdto understand agent roles, team boundaries, and workflow. - Use
TOOLS.mdto customize or record local environment notes.
- Begin by reading
-
Project & Memory Management
- Project vaults are expected under
/root/.openclaw/workspace/vault/projects/following the project SOP inSOUL.md. - For continuity, maintain daily logs (
memory/YYYY-MM-DD.md) and summarize key learnings, events, or decisions inMEMORY.md.
- Project vaults are expected under
-
Dashboard
- To start the React dashboard UI:
cd dashboard npm install npm start - Open http://localhost:3000 to view or develop the dashboard.
- To start the React dashboard UI:
-
Session Workflow
- On workspace start, review identity and context per instructions in
AGENTS.md. - Only read and update
MEMORY.mdin a main, direct session, not in group or shared contexts.
- On workspace start, review identity and context per instructions in
Notes
- Agent code/design/documentation work is logically separated among team roles as defined in
SOUL.md. - Project and agent lifecycle is process-driven; always follow the standard operating procedures.
- Only add environment or operational notes to
TOOLS.md—keep skills and configuration details separated. - Memory handling is explicit: always write down essential information, avoid relying on "mental notes".
- Do not load personal memory files (like
MEMORY.md) outside direct sessions for security reasons. - The dashboard UI is provided as a template; extend as needed per your workflow requirements.
For detailed workflow, agent responsibilities, and file usage, see the respective .md guides in the workspace.
No comments yet.