multicorn-shield 1.11.0 → 1.12.0

package/CHANGELOG.md

@@ -9,6 +9,36 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - Bump `version` in `package.json` before publishing to npm.
 
+## [Unreleased]
+
+## [1.12.0] - 2026-07-06
+
+### Fixed
+
+- Local proxy no longer crashes on startup with "pathRegexp is not a function": pinned express 4's nested path-to-regexp to the patched 0.1.x line so the supergateway filesystem gateway starts cleanly.
+- `files` now threads the resolved base URL (--base-url > MULTICORN_BASE_URL > config baseUrl > default) into the spawned proxy's SHIELD_API_BASE_URL, so a local-minted API key is validated against the correct service instead of defaulting to production.
+- `files restart` now respawns the shared proxy instead of reusing a stale one, so a changed base URL takes effect.
+- `files` now reaps a stale pid file when its process is no longer running, instead of refusing to start with "already running" when the port is free.
+- `init` base-URL precedence now matches `files` (--base-url > MULTICORN_BASE_URL > config baseUrl > default), so MULTICORN_BASE_URL overrides a stale stored base URL.
+- `init` "Use this key? (Y/n)" prompt now accepts a pasted `mcs_` key as a replacement key rather than silently keeping the existing one.
+- OpenClaw plugin config is now written in the shape OpenClaw's schema accepts (apiKey/baseUrl/agentName/failMode as direct properties, no env wrapper), fixing "Unrecognized keys: env, agentName" on load.
+- Corrected the OpenClaw auth-error message to point at the valid config path.
+
+### Changed
+
+- The interactive platform picker is now native-only; MCP/hosted agents are directed to the dashboard. Selecting a native platform proceeds straight to native setup with no redundant native-vs-hosted prompt. Explicit `--client` still configures any supported platform.
+
+### Security
+
+- Native governance hooks and the OpenClaw plugin now fail closed: when the Shield API cannot be reached or authentication fails, tool calls are blocked (with an actionable message) instead of being silently allowed. `failMode` is honoured from configuration and defaults to closed.
+- The OpenClaw plugin config now prefers a `${MULTICORN_API_KEY}` reference over embedding the raw API key in `openclaw.json`.
+
+## [1.11.1] - 2026-06-22
+
+### Fixed
+
+- The local proxy server entry is now resolved by locating the multicorn-shield package root rather than a fixed relative climb, so `files` works from source, bundled dist, and npm installs.
+
 ## [1.11.0] - 2026-06-18
 
 ### Added
@@ -25,6 +55,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Fixed
 
+- `files` now starts the local proxy by spawning the bundled `dist/server.js` entry directly (with `PORT`, `SHIELD_API_BASE_URL`, and `ALLOW_PRIVATE_TARGETS`), instead of invoking the deprecated `multicorn-proxy` CLI alias. First-run setup works when no proxy is already listening on the port.
 - Pinned transitive dependencies (`path-to-regexp`, `ws`, `hono`) via `pnpm.overrides` to clear high-severity audit advisories pulled in by `supergateway` and the MCP SDK.
 
 ## [1.10.0] - 2026-06-09

package/README.md

@@ -22,7 +22,15 @@ Most AI coding agents inherit direct access to MCP tools, terminals, mail, and s
 
 ## Supported agents
 
-`npx multicorn-shield init` recognises every platform listed here (same registry as [`INIT_WIZARD_PLATFORM_REGISTRY`](https://github.com/Multicorn-AI/multicorn-shield/blob/main/src/proxy/config.ts) in source). Integration mode follows the [**Shield threat model**](https://multicorn.ai/shield/threat-model): **native plugins** inspect the whole tool surface exposed by the host; **hosted MCP proxy** governs MCP-shaped traffic routed through Shield.
+`npx multicorn-shield init` walks you through **native plugins** only: OpenClaw, Claude Code, Windsurf, Cline, Gemini CLI, OpenCode, and Codex CLI. Native plugins govern files, terminal, and browser tools exposed by the host.
+
+**MCP-only clients** (Cursor, Claude Desktop, GitHub Copilot, Kilo Code, Continue, Goose, and other hosted MCP setups) are configured in the [Multicorn dashboard](https://app.multicorn.ai/agents/new). The init menu includes a link there if you do not see your agent.
+
+The full platform registry in [`INIT_WIZARD_PLATFORM_REGISTRY`](https://github.com/Multicorn-AI/multicorn-shield/blob/main/src/proxy/config.ts) still lists every supported slug. Integration mode follows the [**Shield threat model**](https://multicorn.ai/shield/threat-model): **native plugins** inspect the whole tool surface exposed by the host; **hosted MCP proxy** governs MCP-shaped traffic routed through Shield.
+
+Use `npx multicorn-shield files --client <name>` to write MCP config for any supported coding client (including Cursor and Copilot). Valid `--client` names: cursor, cline, windsurf, claude, copilot, goose, gemini, codex, continue, kilo, opencode.
+
+For hybrid platforms (Windsurf, Cline, Gemini CLI, OpenCode, Codex CLI), the init wizard defaults to the native plugin. Use `npx multicorn-shield init --integration hosted` when you want the hosted MCP proxy path instead.
 
 | Agent                           | Mode                                             | Setup on multicorn.ai                                                 |
 | ------------------------------- | ------------------------------------------------ | --------------------------------------------------------------------- |
@@ -40,7 +48,7 @@ Most AI coding agents inherit direct access to MCP tools, terminals, mail, and s
 | Continue                        | Hosted MCP proxy                                 | [Setup guide](https://multicorn.ai/docs/mcp-proxy#generic-mcp-client) |
 | Goose                           | Hosted MCP proxy                                 | [Setup guide](https://multicorn.ai/docs/mcp-proxy#generic-mcp-client) |
 
-For any other MCP client on stdio, pick **Local MCP / Other** in the wizard or open the [Setup guide](https://multicorn.ai/docs/mcp-proxy#generic-mcp-client).
+For any other MCP client on stdio, use `npx multicorn-shield --wrap` or set up a hosted agent in the [dashboard](https://app.multicorn.ai/agents/new).
 
 ## Quick start
 

package/dist/index.cjs

@@ -2118,7 +2118,7 @@ function handleHttpError(status, logger, retryDelaySeconds) {
   if (status === 401 || status === 403) {
     if (!authErrorLogged) {
       authErrorLogged = true;
-      const errorMsg = "[multicorn-shield] ERROR: Authentication failed. Your MULTICORN_API_KEY is invalid or expired. Check the key in your OpenClaw config (~/.openclaw/openclaw.json \u2192 plugins.entries.multicorn-shield.env.MULTICORN_API_KEY). Get a valid key from your Multicorn dashboard (Settings \u2192 API Keys).";
+      const errorMsg = "[multicorn-shield] ERROR: Authentication failed. Your MULTICORN_API_KEY is invalid or expired. Check the key in ~/.multicorn/config.json (from npx multicorn-shield init) or ~/.openclaw/openclaw.json \u2192 plugins.entries.multicorn-shield.config.apiKey. Get a valid key from your Multicorn dashboard (Settings \u2192 API Keys).";
       logger?.error(errorMsg);
       process.stderr.write(`${errorMsg}
 `);

package/dist/index.js

@@ -2116,7 +2116,7 @@ function handleHttpError(status, logger, retryDelaySeconds) {
   if (status === 401 || status === 403) {
     if (!authErrorLogged) {
       authErrorLogged = true;
-      const errorMsg = "[multicorn-shield] ERROR: Authentication failed. Your MULTICORN_API_KEY is invalid or expired. Check the key in your OpenClaw config (~/.openclaw/openclaw.json \u2192 plugins.entries.multicorn-shield.env.MULTICORN_API_KEY). Get a valid key from your Multicorn dashboard (Settings \u2192 API Keys).";
+      const errorMsg = "[multicorn-shield] ERROR: Authentication failed. Your MULTICORN_API_KEY is invalid or expired. Check the key in ~/.multicorn/config.json (from npx multicorn-shield init) or ~/.openclaw/openclaw.json \u2192 plugins.entries.multicorn-shield.config.apiKey. Get a valid key from your Multicorn dashboard (Settings \u2192 API Keys).";
       logger?.error(errorMsg);
       process.stderr.write(`${errorMsg}
 `);