openclaw-code-agent 4.4.2 → 4.5.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
@@ -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.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 harness model restrictions remain plugin-owned.
130
+ The current package targets and validates against the OpenClaw SDK package `openclaw@2026.6.6`, 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.6` changes wake routing metadata, Telegram topic and callback delivery, cron/session delivery, runtime tool allowlists, trusted plugin policy contracts, and adjacent bundled Codex/ACPX package targets, 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 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
 
@@ -139,7 +139,15 @@ If you use experimental OpenCode, make sure local `opencode >= 1.16.2` is availa
139
139
 
140
140
  ## First Session
141
141
 
142
- In chat, ask OpenClaw to start work:
142
+ In chat, ask OpenClaw to start work. The plugin ships with `oca` as a built-in short name, so no local alias config is needed for these launch phrases:
143
+
144
+ ```text
145
+ Let oca do the auth middleware bug fix.
146
+ Ask oca to add tests for the billing flow.
147
+ Have oca handle the failing dashboard smoke test.
148
+ ```
149
+
150
+ You can also ask without the short name:
143
151
 
144
152
  ```text
145
153
  Start a coding session named fix-auth to fix the auth middleware bug.