openclaw-code-agent 4.7.9 → 4.7.10
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 +154 -161
- package/npm-shrinkwrap.json +2 -2
- package/openclaw.plugin.json +1 -1
- package/package.json +7 -7
package/README.md
CHANGED
|
@@ -128,7 +128,7 @@ Because worktree isolation defaults to `delegate`, `defaultWorkdir` should norma
|
|
|
128
128
|
|
|
129
129
|
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.
|
|
130
130
|
|
|
131
|
-
The current package
|
|
131
|
+
The current package requires, is built against, and is validated against OpenClaw `2026.8.2`, while its plugin API, Gateway, and peer dependency contracts retain the verified `2026.8.1` compatibility floor. The manifest still declares `contracts.tools`, the plugin still imports only `openclaw/plugin-sdk/plugin-entry`, and its session store, wake routing, callbacks, worktree flows, and Codex/Claude model restrictions remain plugin-owned. OpenClaw's host-side migration of `codex/*` and `openai-codex/*` model routes to `openai/*` does not rewrite Code Agent's unprefixed Codex harness models (`gpt-5.6-sol`, `gpt-5.6-terra`, and `gpt-5.6-luna`) or bypass `harnesses.codex.allowedModels`. Existing sessions, permissions, Telegram/topic routes, automation delivery context, callback ownership, and tool allowlists remain under the same plugin contracts. OpenClaw `2026.8.2` broadens the default visibility of unsandboxed same-agent sessions, including retained cron sessions; operators who need narrower isolation can explicitly configure `tools.sessions.visibility` as `tree` or `self`. Installing this package performs no host-side configuration migration.
|
|
132
132
|
|
|
133
133
|
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:
|
|
134
134
|
|