docs/reference/AGENTS.default.md
OpenClaw uses a dedicated workspace directory for the agent. Default: ~/.openclaw/workspace (configurable via agents.defaults.workspace).
mkdir -p ~/.openclaw/workspace
cp docs/reference/templates/AGENTS.md ~/.openclaw/workspace/AGENTS.md
cp docs/reference/templates/SOUL.md ~/.openclaw/workspace/SOUL.md
cp docs/reference/templates/TOOLS.md ~/.openclaw/workspace/TOOLS.md
cp docs/reference/AGENTS.default.md ~/.openclaw/workspace/AGENTS.md
agents.defaults.workspace (supports ~):{
agents: { defaults: { workspace: "~/.openclaw/workspace" } },
}
Before proposing or building a custom system, feature, workflow, tool, integration, or automation, do a brief check for open-source projects, maintained libraries, existing OpenClaw plugins, or free platforms that already solve it well enough. Prefer those when adequate. Build custom only when existing options are unsuitable, too expensive, unmaintained, unsafe, non-compliant, or the user explicitly asks for custom. Avoid paid-service recommendations unless the user explicitly approves spend. Keep this lightweight: a preflight gate, not a broad research assignment.
SOUL.md, USER.md, and today+yesterday in memory/.MEMORY.md when present.SOUL.md defines identity, tone, and boundaries. Keep it current.SOUL.md, tell the user.memory/YYYY-MM-DD.md (create memory/ if needed).MEMORY.md for durable facts, preferences, and decisions.memory.md is legacy repair input only; do not keep both root files on purpose.MEMORY.md when present.SKILL.md when you need it.TOOLS.md (Notes for Skills).If you treat this workspace as Clawd's "memory", make it a git repo (ideally private) so AGENTS.md and your memory files are backed up.
cd ~/.openclaw/workspace
git init
git add AGENTS.md
git commit -m "Add Clawd workspace"
# Optional: add a private remote + push
openclaw CLI via its bundled binary.main session by default; groups stay isolated as agent:<agentId>:<channel>:group:<id> (rooms/channels: agent:<agentId>:<channel>:channel:<id>); heartbeats keep background tasks alive.user:<id> or channel:<id> targets (bare numeric ids are ambiguous).openclaw CLI for scripting; mac app handles permissions.openclaw browser (tabs/status/screenshot) with the OpenClaw-managed Chrome profile.openclaw browser eval|query|dom|snapshot (and --json/--out when you need machine output).openclaw browser click|type|hover|drag|select|upload|press|wait|navigate|back|evaluate|run (click/type require snapshot refs; use evaluate for CSS selectors).