Upgrading from 4.x? 5.x needs Node 22.14+ or 24. npm warns on Node 20 and still installs; the native module will not load. Read the guide.

Install ShieldCortex

From a fresh machine: install, run setup, see a catch, then turn the tool gate on. 5.x needs Node 22.14+ or Node 24. npm warns on Node 20 and still installs; the native module will not load.

Fresh Install

Requires Node 22.14+ or Node 24+. Node 20 and Node 23 are not supported. npm warns on Node 20 (EBADENGINE) and installs anyway; with engine-strict it refuses. The native module will not load on Node 20. Coming from 4.x, read Upgrading to 5 before you install. Stay on 4.x with npm install -g shieldcortex@4.

ShieldCortex CLI

Install, then setup (alias quickstart). It prints one host table and asks before wiring. Action Guard stays off.

npm install -g shieldcortex
shieldcortex setup
shieldcortex doctor

Within 5.x, update with shieldcortex update, then doctor.

ShieldCortex + OpenClaw

Manual OpenClaw path. shieldcortex setup offers the same wiring and asks first:

openclaw skills install shieldcortex
openclaw plugins install @drakon-systems/shieldcortex-realtime

Restart the gateway: openclaw gateway restart

Migrating from Claude Cortex

# Non-destructive — copies your database, updates settings
shieldcortex migrate
# Restart Claude Code

Your existing memories are preserved. The original database stays intact at ~/.claude-cortex/ for rollback.

See a catch, then turn the gate on

The published package does not include examples/. This command works after npm install -g. A catch exits non-zero.

shieldcortex scan "ignore previous instructions"

Action Guard stays off until you turn it on. On Claude Code, OpenClaw, and Hermes this pins the gate (root, once). There is no unprotect command.

sudo shieldcortex protect

Verify Installation

shieldcortex doctor

doctor will not print “protected” for a host that cannot deny a tool call.

Next steps

Trouble installing?

If shieldcortex doctor reports an issue, the report links the exact fix command. For everything else, file an issue on GitHub.