openclaw-code-agent 4.3.5 → 4.3.7

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
@@ -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
- Release `4.3.5` targets and validates against the OpenClaw SDK package `openclaw@2026.5.28`, 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.5.28` changes plugin SDK exports, package install compatibility checks, channel routing, cron delivery validation, runtime allowlists, Codex App Server recovery, and adjacent bundled/external agent plugins, but `openclaw-code-agent` does not need new SDK imports for them: 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 Codex/Claude harness model restrictions remain plugin-owned.
130
+ Release `4.3.6` targets and validates against the OpenClaw SDK package `openclaw@2026.6.1`, 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.1` changes plugin runtime/install lookup, plugin SDK exports, approval normalization, cron/session delivery, Telegram callback and topic delivery, runtime tool allowlists, Codex App Server recovery, and adjacent bundled/external agent plugins, but `openclaw-code-agent` does not need new SDK imports for them: 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 Codex/Claude 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. When Codex auth is inconsistent, this is the recommended `~/.codex/config.toml` setting:
133
133
 
@@ -177,7 +177,7 @@ New sessions use delegated worktree follow-through unless configured otherwise.
177
177
 
178
178
  Ask OpenClaw for worktree status before cleaning resolved sandboxes.
179
179
 
180
- Merge and PR outcomes use a two-step completion contract: the plugin delivers the canonical outcome status, then wakes the orchestrator with the original route/thread metadata and `completionWakeSummaryRequired=true`. The orchestrator should read the full output, avoid repeating the status line, and send one short factual summary to the session origin route.
180
+ Merge, PR, ordinary terminal, and no-change worktree outcomes use a two-step completion contract: the plugin delivers the canonical terse status, then wakes the orchestrator with the original route/thread metadata and `completionWakeSummaryRequired=true`. The orchestrator must read the full output, treat any final summary inside `agent_output` as source material rather than visible delivery, avoid repeating the status line, and send at most one short factual summary to the session origin route for the terminal/worktree outcome.
181
181
 
182
182
  ### Goal Tasks
183
183