openclaw-code-agent 3.2.1 → 4.0.1

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 CHANGED
@@ -28,15 +28,13 @@ Need the ACPX vs Codex vs code-agent breakdown? See [docs/ACP-COMPARISON.md](doc
28
28
 
29
29
  The shared substrate is often the local `codex` command and Codex App Server, but the responsibilities are different. This plugin is not an ACP server and it does not depend on OpenClaw's bundled Codex provider to expose its own `codex` harness.
30
30
 
31
- ## New In 3.2.1
31
+ ## New In 4.0.1
32
32
 
33
- `3.2.1` is a maintenance release focused on routing correctness, compatibility metadata, and release/security hygiene around the newer plan-review and worktree model.
33
+ `4.0.1` is the OpenClaw `v2026.4.25` compatibility patch release. It keeps the `4.0.0` messaging-contract cleanup intact while refreshing the verified local build/test target and adding guard coverage for newer OpenClaw plugin-install and embedded-extension behavior.
34
34
 
35
- - **Trusted route resolution for newer OpenClaw contexts**. The plugin now prefers `deliveryContext` and `requesterSenderId` when available, while keeping legacy routing fallbacks for persisted sessions and older fixtures.
36
- - **Safer verifier execution**. Goal-task verifier commands now drop shell bootstrap hooks like `BASH_ENV` and `ENV` so operator-provided verifier commands run with fewer implicit side effects.
37
- - **Compatibility and onboarding metadata refresh**. The release raises the external OpenClaw baseline to `v2026.4.14`, verifies against the stable `v2026.4.21` build target, and ships the manifest activation/setup descriptors plus narrower onboarding guidance for first-run setup.
38
- - **Codex harness policy refresh**. The built-in Codex allowlist now includes `gpt-5.4-pro`.
39
- - **Stronger security and release hygiene**. Dependency overrides, CI checks, plugin security validation, and release metadata parity checks are all updated to match the shipped package.
35
+ - **Verified OpenClaw target**. Local build/test metadata now targets stable OpenClaw `2026.4.25` while keeping the minimum compatibility floor at `>=2026.4.21`.
36
+ - **Install-registry compatibility**. Guard coverage now confirms plugin code does not read or write OpenClaw's legacy authored install metadata.
37
+ - **Embedded-extension compatibility**. Guard coverage now documents the removed embedded-extension factory path and keeps future tool-result rewriting aligned with OpenClaw's runtime-neutral middleware contract.
40
38
 
41
39
  ## From Prompt To Merged Branch
42
40
 
@@ -122,7 +120,7 @@ openclaw plugins enable openclaw-code-agent
122
120
  openclaw gateway restart
123
121
  ```
124
122
 
125
- This release targets the OpenClaw `v2026.4.14` external plugin contract and is verified against the stable `v2026.4.21` build/test target. `package.json` now carries the plugin API compatibility and build metadata used by modern OpenClaw / ClawHub installs, and `openclaw.plugin.json` now advertises the plugin-owned command activation surface plus the onboarding metadata OpenClaw uses during plugin-config setup. Keep those metadata surfaces in sync when bumping the plugin release baseline.
123
+ This release targets the OpenClaw `v2026.4.21` external plugin contract and is verified against the stable `v2026.4.25` build/test target. `package.json` now carries the plugin API compatibility and build metadata used by modern OpenClaw / ClawHub installs, and `openclaw.plugin.json` now advertises the plugin-owned command activation surface plus the onboarding metadata OpenClaw uses during plugin-config setup. Keep those metadata surfaces in sync when bumping the plugin release baseline.
126
124
 
127
125
  The current manifest descriptors stay intentionally narrow: activation advertises only the chat commands this plugin owns, and setup stays minimal with `requiresRuntime: false`. First-run onboarding is driven by the manifest config schema and `uiHints`, not by provider/backend setup descriptors.
128
126
 
@@ -150,12 +148,12 @@ Add a minimal config block under `plugins.entries["openclaw-code-agent"]` in `~/
150
148
  "fallbackChannel": "telegram|my-bot|123456789",
151
149
  "harnesses": {
152
150
  "claude-code": {
153
- "defaultModel": "sonnet",
151
+ "defaultModel": "anthropic/claude-sonnet-4-7",
154
152
  "allowedModels": ["sonnet", "opus"]
155
153
  },
156
154
  "codex": {
157
- "defaultModel": "gpt-5.4",
158
- "allowedModels": ["gpt-5.4", "gpt-5.4-pro"],
155
+ "defaultModel": "gpt-5.5",
156
+ "allowedModels": ["gpt-5.5", "gpt-5.5-pro"],
159
157
  "reasoningEffort": "medium"
160
158
  }
161
159
  }