Upgrading from 4.x? 5.x needs Node 22.14+ or 24+; Node 20 and 23 are unsupported. On Node 20, npm warns and still installs unless engine-strict is set; the database engine will not load. Read the guide.

launch release action-guard

ShieldCortex 5.11.0: Config Tamper Evidence, Clearer Watch Only, Session-End Timeout Digest

DS
Drakon Systems · 21 October 2026

ShieldCortex 5.11.0 was released on 21 October 2026. It is a minor release on 5.10.7. It adds no new configuration, and Action Guard stays off by default in the shared ShieldCortex config.

What shipped

Config tamper evidence (#647). A write on a tampered config.json no longer re-signs it as valid. Explicit setters refuse with a message and exit 1, and automatic writers skip with one stderr line per process. The file and its stale signature stay as they were, and reads still get the strict fail-closed posture. shieldcortex doctor names the config verdict without side effects. The signature is still a corruption detector, not tamper protection.

Watch only on headless sessions (#874). On a session with no prompt surface, Watch only (advisory) no longer denies read-only inspection of ShieldCortex’s own config when the command is only a closed set of plain read verbs on plain arguments. Writes, copies over the file, in-place edits and network sends on that path stay held. The exception is in the shared classifier, so it also applies under Enforce, which still holds writes on that file and, with no prompt surface, still denies the remaining dangerous tier. Watch only denials now name their signal instead of redacted-signal, and doctor reports Watch only as advisory rather than off.

Session-end digest for OpenClaw (#673, partial). The OpenClaw plugin can send one report-only digest of recorded approval timeouts at session end to the actionGuard.notify webhook you already configured. It reports only and changes no approval, timeout or decision. #673 stays open.

Release hygiene. hono moves to 4.13.13 and the MCP SDK to 1.32.1 to clear advisories published on 20 October (PR #876), with no ShieldCortex source change. The npm release workflow verifies the published versions with fresh registry reads (#871).

Upgrade to 5.11.0

npm install -g shieldcortex@5.11.0

If config.json fails its signature check, a config write now refuses instead of clearing the warning. Restore a backup whose signature verifies, or move it aside and rebuild it through the setters.

Read the changelog →

Built by Drakon Systems.