openclaw-code-agent 4.7.0 → 4.7.2
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 +9 -8
- package/dist/index.js +191 -187
- package/openclaw.plugin.json +1 -1
- package/package.json +7 -6
package/README.md
CHANGED
|
@@ -81,17 +81,18 @@ openclaw gateway restart
|
|
|
81
81
|
openclaw plugins inspect openclaw-code-agent --runtime --json
|
|
82
82
|
```
|
|
83
83
|
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
|
|
84
|
+
OpenClaw 2026.7.1 no longer performs built-in dangerous-code blocking during
|
|
85
|
+
plugin installation. Review the subprocess rationale in
|
|
86
|
+
[docs/SECURITY.md](docs/SECURITY.md) before installing this plugin because it
|
|
87
|
+
launches local coding harnesses and git tooling. Operators who require a local
|
|
88
|
+
allow/block decision should configure OpenClaw's `security.installPolicy`.
|
|
89
|
+
To replace an existing reviewed installation and pin the resolved version, use:
|
|
89
90
|
|
|
90
91
|
```bash
|
|
91
|
-
openclaw plugins install openclaw-code-agent --force --pin
|
|
92
|
+
openclaw plugins install openclaw-code-agent --force --pin
|
|
92
93
|
```
|
|
93
94
|
|
|
94
|
-
Use
|
|
95
|
+
Use `--force` only for a package/source you already trust. When validating a
|
|
95
96
|
specific reviewed release, add its version after the package name.
|
|
96
97
|
|
|
97
98
|
Add the smallest useful config under `plugins.entries["openclaw-code-agent"]` in `~/.openclaw/openclaw.json`:
|
|
@@ -127,7 +128,7 @@ Because worktree isolation defaults to `delegate`, `defaultWorkdir` should norma
|
|
|
127
128
|
|
|
128
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.
|
|
129
130
|
|
|
130
|
-
The current package targets and validates against
|
|
131
|
+
The current package targets and validates against OpenClaw `2026.7.1`, which is also the minimum host version advertised for new installs. The plugin API peer range remains `>=2026.4.21` for dependency resolution, while the install requirement stays aligned with the host version used for release verification. OpenClaw `2026.7.1` changes Codex app-server, Telegram delivery, cron/session delivery, tool visibility, approval, and plugin update behavior, but `openclaw-code-agent` does not need new SDK imports for those 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. Current callback behavior around native callback data, routed follow-ups, retryable stale plan approval buttons, and serialized plan decisions remains plugin-owned.
|
|
131
132
|
|
|
132
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:
|
|
133
134
|
|