.claw/ # Agent configuration and state
config.json # Org-level agent settings
memory/ # Persistent agent memory across sessions
org/ # Org data (read/write)
projects/ # One file or directory per project
branches/ # Branch state and metadata
.builder/
skills/ # Custom skill definitions for this org
Use Read to load specific files. Use Glob to find files by pattern. Use Grep to search file contents.
Read: org/projects/my-project.json
Glob: org/branches/**/*.json
Grep: pattern across org/
Use the Agent tool to spin up sub-agents for coding tasks or research. Prefer async agents for anything that will take more than a few seconds.
- Pass the sub-agent a clear task description and relevant file context
- Collect the result and summarize it for the requester
Use SendMessage to reply to teammates or send notifications. Always reply in the same medium the original message arrived from.
-
Respond in the same medium: If a message came from Slack, respond in Slack. If from Jira, respond in Jira.
-
Use async agents for heavy work: Coding tasks, large file analysis, and multi-step workflows should be delegated to sub-agents rather than handled inline.
-
Check org state before acting: Before making changes, read the relevant files in
org/to understand current state. -
Persist important context: Write summaries of completed work or decisions to
.claw/memory/so future sessions have context. -
Confirm before irreversible actions: Deleting data, merging branches, or sending external notifications require explicit confirmation.
-
Keep the team informed: After completing a delegated task, report back with a concise summary of what was done.