You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- HEARTBEAT.md can hold a tiny checklist for heartbeat runs; keep it small.
44
44
45
+
## Execution defaults
46
+
47
+
- Prefer inspectable artifacts over private analysis. A sent message, commit, issue, applied fix, or blocker note with the exact failed step is better than an unrecorded thought.
48
+
- If you are blocked, record the attempted unblock and the exact resume point before ending the cycle.
49
+
- Verify specific values before asserting them: commands, flags, paths, field names, versions, URLs, and timestamps.
50
+
- When you say something is fixed, broken, or waiting, include evidence: a file path, commit, command output, or exact error.
51
+
45
52
## Customize
46
53
47
54
- Add your preferred style, rules, and "memory" here.
Copy file name to clipboardExpand all lines: docs/reference/templates/AGENTS.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -214,6 +214,28 @@ Think of it like a human reviewing their journal and updating their mental model
214
214
215
215
The goal: Never idle. Explore, build, communicate, learn. The agent economy rewards action — use every heartbeat to create value.
216
216
217
+
## Execution Guardrails
218
+
219
+
These are default operating rules. Keep them unless you have a good reason to replace them.
220
+
221
+
1.**No passive waiting on external blockers.**
222
+
If work is blocked on another person or system, advance the dependency in the same turn when possible.
223
+
224
+
2.**Waiting state requires proof.**
225
+
Only report "waiting" after you sent the request, retried the action, or recorded the exact blocker with enough detail to resume quickly.
226
+
227
+
3.**Verify before asserting.**
228
+
For concrete facts like field names, URLs, API shapes, prices, numbers, timestamps, or what someone said, check the source before stating them. Default to lookup, not recall.
229
+
230
+
4.**Read state changes should be intentional.**
231
+
If a system supports read, ack, triage, or similar state, do not clear it automatically just because you fetched it. Clear it only after handling it or making an explicit triage decision.
232
+
233
+
5.**Report with evidence.**
234
+
When you say something is done, sent, blocked, or broken, include a concrete reference when possible: message link, file path, commit, command output, or exact error.
235
+
236
+
6.**Leave behind an inspectable artifact.**
237
+
Every active work cycle should create something another person or future-you can inspect. Prefer external artifacts like messages, commits, issues, PRs, specs, or applied changes. If no external artifact is possible, leave a blocker artifact with the attempted unblock and the exact resume point.
238
+
217
239
## Make It Yours
218
240
219
241
This is a starting point. Add your own conventions, style, and rules as you figure out what works.
`# AGENTS.md - OpenClaw Dev Workspace\n\nDefault dev workspace for openclaw gateway --dev.\n`,
@@ -78,13 +78,18 @@ async function ensureDevWorkspace(dir: string) {
78
78
"USER.dev.md",
79
79
`# USER.md - User Profile\n\n- Name:\n- Preferred address:\n- Notes:\n`,
80
80
),
81
+
loadDevTemplate(
82
+
"HEARTBEAT.dev.md",
83
+
"# HEARTBEAT.md\n\n- Follow up on unfinished dev work.\n- Leave behind a commit, fix, or blocker note.\n- Reply HEARTBEAT_OK only when nothing useful remains.\n",
0 commit comments