openclaw-code-agent 4.5.3 → 4.5.4
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 +180 -180
- package/openclaw.plugin.json +1 -1
- package/package.json +7 -6
package/README.md
CHANGED
|
@@ -127,7 +127,7 @@ Because worktree isolation defaults to `delegate`, `defaultWorkdir` should norma
|
|
|
127
127
|
|
|
128
128
|
Chat-launched sessions route updates back to their originating chat thread. For agent-launched tool sessions without an origin route, configure `fallbackChannel` or `agentChannels` in the reference guide.
|
|
129
129
|
|
|
130
|
-
The current package targets and validates against the OpenClaw SDK package `openclaw@2026.6.
|
|
130
|
+
The current package targets and validates against the OpenClaw SDK package `openclaw@2026.6.9`, while keeping the plugin peer floor at `>=2026.4.21`. No host upgrade or host config change is required for this plugin compatibility update. OpenClaw `2026.6.9` changes installed channel plugin discovery, provider package boundaries, plugin write ownership checks, declared tool allowlist recognition, cron delivery defaults, yielded media handling, agent completion recovery, and channel reply reliability. Current main also includes the recent callback and follow-up fixes for native Telegram/Discord callback data, delayed/raw callback routing, retryable plan/question tokens, serialized plan decisions, and PR update completion summary dedupe. `openclaw-code-agent` does not need new SDK imports for the OpenClaw changes: the manifest already declares `contracts.tools`, the plugin still imports only `openclaw/plugin-sdk/plugin-entry`, and its own session store, wake routing, callbacks, worktree flows, and harness model restrictions remain plugin-owned.
|
|
131
131
|
|
|
132
132
|
If you use Codex, make sure the local `codex` command or `OPENCLAW_CODEX_APP_SERVER_COMMAND` override is available and authenticated. Codex-specific defaults live under `harnesses.codex`: `reasoningEffort` is sent as `reasoningEffort`, and `fastMode: true` sends `service_tier: "fast"` on Codex App Server thread, resume, and turn payloads. The Codex harness starts the app server with stdio listener args by default, only sends UUID-shaped backend thread IDs to `thread/resume`, and reports startup timeouts with redacted recent stderr. When Codex auth is inconsistent, this is the recommended `~/.codex/config.toml` setting:
|
|
133
133
|
|