openclaw-code-agent 3.2.1 → 4.0.0

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,15 @@ 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.0
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.0` is the messaging-contract cleanup release. Interactive direct notifications for Telegram and Discord now go through the same shared OpenClaw presentation contract, and the plugin drops the old Telegram legacy fallback plus the Discord-native component sender split.
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
+ - **Shared outbound interactive delivery**. Telegram and Discord direct notifications now use one `message.send --presentation` path.
36
+ - **Breaking compatibility floor update**. The plugin now requires OpenClaw `v2026.4.21` or newer.
37
+ - **Removed legacy sender paths**. The Telegram `--buttons` fallback and the custom Discord component sender path are gone; both providers now depend on the shared presentation contract.
38
+ - **State migration cleanup**. Persisted approval-prompt delivery state is now recorded as `direct-message`, while older `direct-telegram` entries still restore cleanly.
39
+ - **Model refresh**. Built-in defaults now recommend `anthropic/claude-sonnet-4-7` for Claude Code and `gpt-5.5` for Codex, with `gpt-5.5-pro` also included in the built-in Codex allowlist.
40
40
 
41
41
  ## From Prompt To Merged Branch
42
42
 
@@ -122,7 +122,7 @@ openclaw plugins enable openclaw-code-agent
122
122
  openclaw gateway restart
123
123
  ```
124
124
 
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.
125
+ This release targets the OpenClaw `v2026.4.21` external plugin contract and is verified against the stable `v2026.4.23` 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
126
 
127
127
  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
128
 
@@ -150,12 +150,12 @@ Add a minimal config block under `plugins.entries["openclaw-code-agent"]` in `~/
150
150
  "fallbackChannel": "telegram|my-bot|123456789",
151
151
  "harnesses": {
152
152
  "claude-code": {
153
- "defaultModel": "sonnet",
153
+ "defaultModel": "anthropic/claude-sonnet-4-7",
154
154
  "allowedModels": ["sonnet", "opus"]
155
155
  },
156
156
  "codex": {
157
- "defaultModel": "gpt-5.4",
158
- "allowedModels": ["gpt-5.4", "gpt-5.4-pro"],
157
+ "defaultModel": "gpt-5.5",
158
+ "allowedModels": ["gpt-5.5", "gpt-5.5-pro"],
159
159
  "reasoningEffort": "medium"
160
160
  }
161
161
  }