openclaw-code-agent 4.2.2 → 4.2.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/dist/index.js +106 -105
- package/openclaw.plugin.json +1 -1
- package/package.json +4 -4
- package/skills/code-agent-orchestration/SKILL.md +2 -0
package/openclaw.plugin.json
CHANGED
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "openclaw-code-agent",
|
|
3
|
-
"version": "4.2.
|
|
3
|
+
"version": "4.2.3",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"packageManager": "pnpm@10.30.0",
|
|
6
6
|
"main": "dist/index.js",
|
|
@@ -34,8 +34,8 @@
|
|
|
34
34
|
"minGatewayVersion": "2026.4.21"
|
|
35
35
|
},
|
|
36
36
|
"build": {
|
|
37
|
-
"openclawVersion": "2026.5.
|
|
38
|
-
"pluginSdkVersion": "2026.5.
|
|
37
|
+
"openclawVersion": "2026.5.7",
|
|
38
|
+
"pluginSdkVersion": "2026.5.7"
|
|
39
39
|
}
|
|
40
40
|
},
|
|
41
41
|
"files": [
|
|
@@ -53,7 +53,7 @@
|
|
|
53
53
|
"@types/node": "^25.5.2",
|
|
54
54
|
"esbuild": "^0.28.0",
|
|
55
55
|
"nanoid": "^5.1.7",
|
|
56
|
-
"openclaw": "2026.5.
|
|
56
|
+
"openclaw": "2026.5.7",
|
|
57
57
|
"tsx": "^4.21.0",
|
|
58
58
|
"typescript": "^6.0.2"
|
|
59
59
|
},
|
|
@@ -91,6 +91,8 @@ Completion ownership:
|
|
|
91
91
|
|
|
92
92
|
- The plugin sends the canonical completion notification.
|
|
93
93
|
- The plugin owns the canonical completion status line; the orchestrator owns any additional plain-text follow-up.
|
|
94
|
+
- Completion wakes may arrive in a different chat than the session's original user route. Treat the wake's `originRoute` block as the source of truth for human follow-ups.
|
|
95
|
+
- If `originRoute` differs from the current chat, do not use a normal final assistant reply for the user-facing follow-up. Use a routed send path that preserves `provider`, `target`, and `threadId` instead.
|
|
94
96
|
- After a coding-agent session completes, the orchestrator should usually add at least a short human-useful summary of what changed, what was done, or the concrete outcome.
|
|
95
97
|
- That expectation applies to ordinary terminal/manual completions, manual no-change completions, and delegated worktree completions alike.
|
|
96
98
|
- Use the plugin's canonical `✅` line as the status signal and your follow-up as the factual outcome summary that should usually come right after it.
|