context-mode 1.0.124 → 1.0.126

package/.claude-plugin/marketplace.json

@@ -6,14 +6,14 @@
   },
   "metadata": {
     "description": "Claude Code plugins by Mert Koseoğlu",
-    "version": "1.0.124"
+    "version": "1.0.126"
   },
   "plugins": [
     {
       "name": "context-mode",
       "source": "./",
       "description": "Claude Code MCP plugin that saves 98% of your context window. Sandboxed code execution in 11 languages, FTS5 knowledge base with BM25 ranking, and intent-driven search.",
-      "version": "1.0.124",
+      "version": "1.0.126",
       "author": {
         "name": "Mert Koseoğlu"
       },

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "context-mode",
-  "version": "1.0.124",
+  "version": "1.0.126",
   "description": "MCP server that saves 98% of your context window with session continuity. Sandboxed code execution in 11 languages, FTS5 knowledge base with BM25 ranking, and automatic state restore across compactions.",
   "author": {
     "name": "Mert Koseoğlu",

package/.openclaw-plugin/openclaw.plugin.json

@@ -3,7 +3,7 @@
   "name": "Context Mode",
   "kind": "tool",
   "description": "OpenClaw plugin that saves 98% of your context window. Sandboxed code execution in 11 languages, FTS5 knowledge base with BM25 ranking, and intent-driven search.",
-  "version": "1.0.124",
+  "version": "1.0.126",
   "sandbox": {
     "mode": "permissive",
     "filesystem_access": "full",

package/.openclaw-plugin/package.json

@@ -1,6 +1,6 @@
 {
   "name": "context-mode",
-  "version": "1.0.124",
+  "version": "1.0.126",
   "description": "OpenClaw plugin that saves 98% of your context window. Sandboxed code execution in 11 languages, FTS5 knowledge base with BM25 ranking, and intent-driven search.",
   "author": {
     "name": "Mert Koseoğlu",

package/README.md

@@ -570,7 +570,7 @@ Full documentation: [`docs/adapters/openclaw.md`](docs/adapters/openclaw.md)
    ```json
    {
      "hooks": {
-      "PreToolUse": [{ "matcher": "local_shell|shell|shell_command|exec_command|container.exec|functions\\.exec_command|Bash|Shell|apply_patch|functions\\.apply_patch|Edit|Write|grep_files|ctx_execute|ctx_execute_file|ctx_batch_execute|ctx_fetch_and_index|ctx_search|ctx_index|mcp__.*__ctx_execute|mcp__.*__ctx_execute_file|mcp__.*__ctx_batch_execute|mcp__.*__ctx_fetch_and_index|mcp__.*__ctx_search|mcp__.*__ctx_index|mcp__(?!.*context-mode)", "hooks": [{ "type": "command", "command": "context-mode hook codex pretooluse" }] }],
+      "PreToolUse": [{ "matcher": "local_shell|shell|shell_command|exec_command|Bash|Shell|apply_patch|Edit|Write|grep_files|ctx_execute|ctx_execute_file|ctx_batch_execute|ctx_fetch_and_index|ctx_search|ctx_index|mcp__", "hooks": [{ "type": "command", "command": "context-mode hook codex pretooluse" }] }],
        "PostToolUse": [{ "hooks": [{ "type": "command", "command": "context-mode hook codex posttooluse" }] }],
        "SessionStart": [{ "hooks": [{ "type": "command", "command": "context-mode hook codex sessionstart" }] }],
        "PreCompact": [{ "hooks": [{ "type": "command", "command": "context-mode hook codex precompact" }] }],
@@ -964,7 +964,7 @@ npm install -g context-mode
 | Tool | What it does | Context saved |
 |---|---|---|
 | `ctx_batch_execute` | Run multiple commands + search multiple queries in ONE call. Opt-in `concurrency: 1-8` for I/O-bound batches. | 986 KB → 62 KB |
-| `ctx_execute` | Run code in 11 languages. Only stdout enters context. | 56 KB → 299 B |
+| `ctx_execute` | Run code in 12 languages. Only stdout enters context. | 56 KB → 299 B |
 | `ctx_execute_file` | Process files in sandbox. Raw content never leaves. | 45 KB → 155 B |
 | `ctx_index` | Chunk markdown into FTS5 with BM25 ranking. | 60 KB → 40 B |
 | `ctx_search` | Query indexed content with multiple queries in one call. | On-demand retrieval |
@@ -978,7 +978,7 @@ npm install -g context-mode
 
 Each `ctx_execute` call spawns an isolated subprocess with its own process boundary. Scripts can't access each other's memory or state. The subprocess runs your code, captures stdout, and only that stdout enters the conversation context. The raw data — log files, API responses, snapshots — never leaves the sandbox.
 
-Eleven language runtimes are available: JavaScript, TypeScript, Python, Shell, Ruby, Go, Rust, PHP, Perl, R, and Elixir. Bun is auto-detected for 3-5x faster JS/TS execution.
+Twelve language runtimes are available: JavaScript, TypeScript, Python, Shell, Ruby, Go, Rust, PHP, Perl, R, Elixir, and C#. Bun is auto-detected for 3-5x faster JS/TS execution.
 
 Authenticated CLIs work through credential passthrough — `gh`, `aws`, `gcloud`, `kubectl`, `docker` inherit environment variables and config paths without exposing them to the conversation.
 

package/build/adapters/claude-code/hooks.d.ts

@@ -25,22 +25,21 @@ export declare const HOOK_TYPES: {
 };
 export type HookType = (typeof HOOK_TYPES)[keyof typeof HOOK_TYPES];
 /**
- * Negative-lookahead matcher for external MCP tool namespaces (#529).
+ * External MCP catch-all matcher for Claude Code (#529, #547 hotfix).
  *
- * Claude Code's hook matcher engine evaluates each entry as a regex against
- * the tool name. This pattern fires on any `mcp__<server>__<tool>` whose
- * server segment is NOT context-mode's own (`plugin_context-mode_...`).
- * Without it, large payloads from external MCPs (slack channel history,
- * telegram messages, gdrive content, notion pages, …) bypass PreToolUse
- * routing and flood the model's context window — PostToolUse runs too late
- * to keep the raw data out.
- *
- * The negative lookahead prevents this entry from double-firing on
- * context-mode's own ctx_* tools, which already have dedicated entries above.
+ * Claude Code's hook matcher engine treats this entry as a substring match
+ * (it also accepts regex, but `mcp__` alone is enough — every MCP tool
+ * surfaces as `mcp__<server>__<tool>`). v1.0.124 used a negative lookahead
+ * `mcp__(?!plugin_context-mode_)` to skip context-mode's own MCP tools,
+ * but this same hooks.json is bundled to Codex CLI which uses Rust's
+ * `regex` crate (no look-around support) — Codex rejected the matcher at
+ * boot, breaking every Codex user (#547). Drop the lookaround on both
+ * sides; the hook BODY (`isExternalMcpTool()` in hooks/core/routing.mjs)
+ * already filters context-mode's own tools, so semantics are preserved.
  */
-export declare const EXTERNAL_MCP_MATCHER_PATTERN = "mcp__(?!plugin_context-mode_)";
+export declare const EXTERNAL_MCP_MATCHER_PATTERN = "mcp__";
 /** Tools that context-mode's PreToolUse hook intercepts. */
-export declare const PRE_TOOL_USE_MATCHERS: readonly ["Bash", "WebFetch", "Read", "Grep", "Agent", "mcp__plugin_context-mode_context-mode__ctx_execute", "mcp__plugin_context-mode_context-mode__ctx_execute_file", "mcp__plugin_context-mode_context-mode__ctx_batch_execute", "mcp__(?!plugin_context-mode_)"];
+export declare const PRE_TOOL_USE_MATCHERS: readonly ["Bash", "WebFetch", "Read", "Grep", "Agent", "mcp__plugin_context-mode_context-mode__ctx_execute", "mcp__plugin_context-mode_context-mode__ctx_execute_file", "mcp__plugin_context-mode_context-mode__ctx_batch_execute", "mcp__"];
 /**
  * Combined matcher pattern for settings.json (pipe-separated).
  * Used by the upgrade command when writing a single consolidated entry.
@@ -81,11 +80,17 @@ export declare function isContextModeHook(entry: {
 export declare function buildHookCommand(hookType: HookType, pluginRoot?: string): string;
 /**
  * Extract the hook script file path from a command string.
- * Returns the path if the command uses the `node "/path/to/hook.mjs"` format
- * or the new `"/path/to/node" "/path/to/hook.mjs"` format (#369, #372),
- * or null if it uses the CLI dispatcher format (which is path-independent).
  *
- * Handles both quoted and unquoted paths, and both forward/back slashes.
+ * Algo-D2 twin — same shape as `src/util/hook-config.ts::extractHookScriptPath`.
+ * Delegates to `parseNodeCommand` for canonical buildNodeCommand-shape;
+ * keeps narrow legacy fallbacks for pre-D3 settings.json entries
+ * (`node "X.mjs"` and `node X.mjs` with no internal whitespace).
+ *
+ * Pre-D2 this matched `node\s+"?([^"]+\.mjs)"?` — the unquoted fallback
+ * silently grabbed the tail after the last whitespace, producing the
+ * #548 doubled-path FAIL on Windows paths with spaces. The new shape
+ * refuses ambiguous input; doctor (Algo-D1) falls through to direct
+ * `existsSync` instead of trusting the regex.
  */
 export declare function extractHookScriptPath(command: string): string | null;
 /**

package/build/adapters/claude-code/hooks.js

@@ -1,4 +1,4 @@
-import { buildNodeCommand } from "../types.js";
+import { buildNodeCommand, parseNodeCommand } from "../types.js";
 /**
  * adapters/claude-code/hooks — Claude Code hook definitions and matchers.
  *
@@ -31,20 +31,19 @@ export const HOOK_TYPES = {
 // PreToolUse matchers
 // ─────────────────────────────────────────────────────────
 /**
- * Negative-lookahead matcher for external MCP tool namespaces (#529).
+ * External MCP catch-all matcher for Claude Code (#529, #547 hotfix).
  *
- * Claude Code's hook matcher engine evaluates each entry as a regex against
- * the tool name. This pattern fires on any `mcp__<server>__<tool>` whose
- * server segment is NOT context-mode's own (`plugin_context-mode_...`).
- * Without it, large payloads from external MCPs (slack channel history,
- * telegram messages, gdrive content, notion pages, …) bypass PreToolUse
- * routing and flood the model's context window — PostToolUse runs too late
- * to keep the raw data out.
- *
- * The negative lookahead prevents this entry from double-firing on
- * context-mode's own ctx_* tools, which already have dedicated entries above.
+ * Claude Code's hook matcher engine treats this entry as a substring match
+ * (it also accepts regex, but `mcp__` alone is enough — every MCP tool
+ * surfaces as `mcp__<server>__<tool>`). v1.0.124 used a negative lookahead
+ * `mcp__(?!plugin_context-mode_)` to skip context-mode's own MCP tools,
+ * but this same hooks.json is bundled to Codex CLI which uses Rust's
+ * `regex` crate (no look-around support) — Codex rejected the matcher at
+ * boot, breaking every Codex user (#547). Drop the lookaround on both
+ * sides; the hook BODY (`isExternalMcpTool()` in hooks/core/routing.mjs)
+ * already filters context-mode's own tools, so semantics are preserved.
  */
-export const EXTERNAL_MCP_MATCHER_PATTERN = "mcp__(?!plugin_context-mode_)";
+export const EXTERNAL_MCP_MATCHER_PATTERN = "mcp__";
 /** Tools that context-mode's PreToolUse hook intercepts. */
 export const PRE_TOOL_USE_MATCHERS = [
     "Bash",
@@ -143,20 +142,30 @@ export function buildHookCommand(hookType, pluginRoot) {
 }
 /**
  * Extract the hook script file path from a command string.
- * Returns the path if the command uses the `node "/path/to/hook.mjs"` format
- * or the new `"/path/to/node" "/path/to/hook.mjs"` format (#369, #372),
- * or null if it uses the CLI dispatcher format (which is path-independent).
  *
- * Handles both quoted and unquoted paths, and both forward/back slashes.
+ * Algo-D2 twin — same shape as `src/util/hook-config.ts::extractHookScriptPath`.
+ * Delegates to `parseNodeCommand` for canonical buildNodeCommand-shape;
+ * keeps narrow legacy fallbacks for pre-D3 settings.json entries
+ * (`node "X.mjs"` and `node X.mjs` with no internal whitespace).
+ *
+ * Pre-D2 this matched `node\s+"?([^"]+\.mjs)"?` — the unquoted fallback
+ * silently grabbed the tail after the last whitespace, producing the
+ * #548 doubled-path FAIL on Windows paths with spaces. The new shape
+ * refuses ambiguous input; doctor (Algo-D1) falls through to direct
+ * `existsSync` instead of trusting the regex.
  */
 export function extractHookScriptPath(command) {
-    // New format: "nodePath" "scriptPath.mjs" (from buildNodeCommand)
-    const newFmt = command.match(/"[^"]+"\s+"([^"]+\.mjs)"/);
-    if (newFmt)
-        return newFmt[1];
-    // Legacy format: node "/path/to/hooks/scriptname.mjs" or node /path/to/hooks/scriptname.mjs
-    const match = command.match(/node\s+"?([^"]+\.mjs)"?/);
-    return match?.[1] ?? null;
+    const parsed = parseNodeCommand(command);
+    if (parsed) {
+        return parsed.scriptPath.endsWith(".mjs") ? parsed.scriptPath : null;
+    }
+    const legacyQuoted = command.match(/^\s*node\s+"([^"]+\.mjs)"\s*$/);
+    if (legacyQuoted)
+        return legacyQuoted[1];
+    const legacyBare = command.match(/^\s*node\s+(\S+\.mjs)\s*$/);
+    if (legacyBare)
+        return legacyBare[1];
+    return null;
 }
 /**
  * Check if a hook entry is a context-mode hook (any hook type).

package/build/adapters/claude-code/index.d.ts

@@ -12,7 +12,7 @@
  *   - Plugin registry: <configDir>/plugins/installed_plugins.json
  */
 import { ClaudeCodeBaseAdapter, type ClaudeCodeWireInput } from "../claude-code-base.js";
-import type { HookAdapter, HookParadigm, PlatformCapabilities, DiagnosticResult, HookRegistration } from "../types.js";
+import { type HookAdapter, type HookParadigm, type PlatformCapabilities, type DiagnosticResult, type HookRegistration, type HealthCheck } from "../types.js";
 export declare class ClaudeCodeAdapter extends ClaudeCodeBaseAdapter implements HookAdapter {
     constructor();
     readonly name = "Claude Code";
@@ -44,6 +44,29 @@ export declare class ClaudeCodeAdapter extends ClaudeCodeBaseAdapter implements
     readSettings(): Record<string, unknown> | null;
     writeSettings(settings: Record<string, unknown>): void;
     validateHooks(pluginRoot: string): DiagnosticResult[];
+    /**
+     * Adapter-defined health checks (Algo-D1 + Algo-D5).
+     *
+     * For each entry in HOOK_SCRIPTS (the canonical hookType → scriptName
+     * map), emit a HealthCheck that joins `pluginRoot + "hooks" +
+     * scriptName` and probes via `existsSync`. Crucially, this NEVER
+     * parses a hook command — pluginRoot and scriptName are both in our
+     * hand, so the regex round-trip that produced the #548 doubled-path
+     * FAIL is bypassed entirely.
+     *
+     * The hook check derives from HOOK_SCRIPTS (single source of truth in
+     * src/adapters/claude-code/hooks.ts), so adding a new hook event in
+     * that map auto-extends doctor coverage — no parallel hardcoded list
+     * to maintain.
+     *
+     * Algo-D5: appends a single "Plugin cache integrity" check that
+     * delegates to the same helper start.mjs uses at boot
+     * (scripts/plugin-cache-integrity.mjs::assertPluginCacheIntegrity).
+     * Same code, two callsites — boot fail-fast and doctor diagnostic
+     * agree byte-for-byte. Users hitting #550 get the actionable signal
+     * without restarting the MCP server.
+     */
+    getHealthChecks(pluginRoot: string): readonly HealthCheck[];
     /** Read plugin hooks from hooks/hooks.json or .claude-plugin/hooks/hooks.json */
     private readPluginHooks;
     /** Check if a hook type is configured in either settings.json or plugin hooks */

package/build/adapters/claude-code/index.js

@@ -16,6 +16,8 @@ import { resolve, join } from "node:path";
 import { homedir } from "node:os";
 import { ClaudeCodeBaseAdapter } from "../claude-code-base.js";
 import { resolveClaudeConfigDir } from "../../util/claude-config.js";
+import { checkPluginCacheIntegritySync } from "../../util/plugin-cache-integrity.js";
+import { buildNodeCommand, } from "../types.js";
 import { HOOK_TYPES, HOOK_SCRIPTS, REQUIRED_HOOKS, PRE_TOOL_USE_MATCHERS, PRE_TOOL_USE_MATCHER_PATTERN, isContextModeHook, isAnyContextModeHook, extractHookScriptPath, buildHookCommand, } from "./hooks.js";
 // ─────────────────────────────────────────────────────────
 // Adapter implementation
@@ -67,7 +69,20 @@ export class ClaudeCodeAdapter extends ClaudeCodeBaseAdapter {
         return join(this.getConfigDir(), "settings.json");
     }
     generateHookConfig(pluginRoot) {
-        const preToolUseCommand = `node ${pluginRoot}/hooks/pretooluse.mjs`;
+        // Algo-D3: every command flows through `buildNodeCommand` (defined in
+        // src/adapters/types.ts), which:
+        //   - quotes both nodePath and scriptPath (#548 — Windows pluginRoots
+        //     with spaces no longer fall through extractHookScriptPath's
+        //     ambiguous-tail fallback),
+        //   - swaps backslashes for forward slashes (#372 MSYS path mangling),
+        //   - uses `process.execPath` instead of bare `node` (#369 PATH
+        //     resolution on Git Bash).
+        // Pre-D3 we hand-rolled `node "${pluginRoot}/hooks/X.mjs"` for all
+        // five events; bare `node` made claude-code the lone outlier and
+        // dropping the execPath swap re-opened the Windows class. Algo-D3.5
+        // (CI invariant in tests/adapters/claude-code.test.ts) locks this in
+        // for adapter #16.
+        const preToolUseCommand = buildNodeCommand(`${pluginRoot}/hooks/pretooluse.mjs`);
         const preToolUseMatchers = [...PRE_TOOL_USE_MATCHERS];
         return {
             PreToolUse: preToolUseMatchers.map((matcher) => ({
@@ -80,7 +95,7 @@ export class ClaudeCodeAdapter extends ClaudeCodeBaseAdapter {
                     hooks: [
                         {
                             type: "command",
-                            command: `node ${pluginRoot}/hooks/posttooluse.mjs`,
+                            command: buildNodeCommand(`${pluginRoot}/hooks/posttooluse.mjs`),
                         },
                     ],
                 },
@@ -91,7 +106,7 @@ export class ClaudeCodeAdapter extends ClaudeCodeBaseAdapter {
                     hooks: [
                         {
                             type: "command",
-                            command: `node ${pluginRoot}/hooks/precompact.mjs`,
+                            command: buildNodeCommand(`${pluginRoot}/hooks/precompact.mjs`),
                         },
                     ],
                 },
@@ -102,7 +117,7 @@ export class ClaudeCodeAdapter extends ClaudeCodeBaseAdapter {
                     hooks: [
                         {
                             type: "command",
-                            command: `node ${pluginRoot}/hooks/userpromptsubmit.mjs`,
+                            command: buildNodeCommand(`${pluginRoot}/hooks/userpromptsubmit.mjs`),
                         },
                     ],
                 },
@@ -113,7 +128,7 @@ export class ClaudeCodeAdapter extends ClaudeCodeBaseAdapter {
                     hooks: [
                         {
                             type: "command",
-                            command: `node ${pluginRoot}/hooks/sessionstart.mjs`,
+                            command: buildNodeCommand(`${pluginRoot}/hooks/sessionstart.mjs`),
                         },
                     ],
                 },
@@ -171,6 +186,53 @@ export class ClaudeCodeAdapter extends ClaudeCodeBaseAdapter {
         });
         return results;
     }
+    /**
+     * Adapter-defined health checks (Algo-D1 + Algo-D5).
+     *
+     * For each entry in HOOK_SCRIPTS (the canonical hookType → scriptName
+     * map), emit a HealthCheck that joins `pluginRoot + "hooks" +
+     * scriptName` and probes via `existsSync`. Crucially, this NEVER
+     * parses a hook command — pluginRoot and scriptName are both in our
+     * hand, so the regex round-trip that produced the #548 doubled-path
+     * FAIL is bypassed entirely.
+     *
+     * The hook check derives from HOOK_SCRIPTS (single source of truth in
+     * src/adapters/claude-code/hooks.ts), so adding a new hook event in
+     * that map auto-extends doctor coverage — no parallel hardcoded list
+     * to maintain.
+     *
+     * Algo-D5: appends a single "Plugin cache integrity" check that
+     * delegates to the same helper start.mjs uses at boot
+     * (scripts/plugin-cache-integrity.mjs::assertPluginCacheIntegrity).
+     * Same code, two callsites — boot fail-fast and doctor diagnostic
+     * agree byte-for-byte. Users hitting #550 get the actionable signal
+     * without restarting the MCP server.
+     */
+    getHealthChecks(pluginRoot) {
+        const hookChecks = Object.entries(HOOK_SCRIPTS).map(([hookType, scriptName]) => {
+            const absolutePath = join(pluginRoot, "hooks", scriptName);
+            return {
+                name: `Hook script: ${hookType} (${scriptName})`,
+                check: () => {
+                    // Direct existsSync — no hook-command parsing, no regex.
+                    // pluginRoot is the value the doctor was invoked with;
+                    // scriptName comes from the canonical HOOK_SCRIPTS map.
+                    if (existsSync(absolutePath)) {
+                        return { status: "OK", detail: absolutePath };
+                    }
+                    return {
+                        status: "FAIL",
+                        detail: `not found at ${absolutePath}`,
+                    };
+                },
+            };
+        });
+        const integrityCheck = {
+            name: "Plugin cache integrity",
+            check: () => checkPluginCacheIntegritySync(pluginRoot),
+        };
+        return [...hookChecks, integrityCheck];
+    }
     /** Read plugin hooks from hooks/hooks.json or .claude-plugin/hooks/hooks.json */
     readPluginHooks(pluginRoot) {
         const candidates = [

package/build/adapters/codex/hooks.d.ts

@@ -27,24 +27,23 @@ export declare const HOOK_TYPES: {
     readonly STOP: "Stop";
 };
 /**
- * Negative-lookahead matcher for external MCP tool namespaces on Codex CLI (#529).
+ * External MCP catch-all matcher for Codex CLI (#529, #547 hotfix).
  *
  * Codex CLI's hook `tool_name` payload uses `mcp__<server>__<tool>` for any
- * MCP-namespaced tool — verified by configs/codex/hooks.json which already
- * matches `mcp__.*__ctx_execute` style for context-mode's OWN MCP tools. This
- * pattern fires PreToolUse for any external `mcp__<server>__<tool>` whose
- * server segment does NOT contain `context-mode`. Without it, large payloads
- * from slack / telegram / gdrive / notion-style MCPs bypass the routing nudge
- * and flood the model's context — PostToolUse runs too late to keep raw data
- * out.
+ * MCP-namespaced tool. Originally this constant used a negative lookahead
+ * `mcp__(?!.*context-mode)` to exclude context-mode's own MCP tools at the
+ * matcher layer. v1.0.124 shipped that pattern and Codex (Rust `regex` crate)
+ * rejected the matcher at boot with "look-around not supported", breaking
+ * every Codex user (#547).
  *
- * The negative lookahead `(?!.*context-mode)` covers both naming variants
- * Codex sees in practice: the canonical `mcp__context-mode__ctx_*` AND the
- * Claude Code plugin shim `mcp__plugin_context-mode_context-mode__ctx_*`.
- * Codex own bare names (ctx_execute, local_shell, …) are not `mcp__`-prefixed
- * and are unaffected.
+ * Fix: drop the lookaround. The matcher is now a charset-clean literal
+ * (`[A-Za-z0-9_|]` only), satisfying Codex's `is_exact_matcher`
+ * (refs/platforms/codex/codex-rs/hooks/src/events/common.rs:152) which
+ * short-circuits the regex engine entirely. context-mode's own MCP tools are
+ * already filtered in the hook BODY by `isExternalMcpTool()` in
+ * hooks/core/routing.mjs — semantics preserved.
  */
-export declare const EXTERNAL_MCP_MATCHER_PATTERN = "mcp__(?!.*context-mode)";
+export declare const EXTERNAL_MCP_MATCHER_PATTERN = "mcp__";
 /**
  * Path to the routing instructions file for Codex CLI.
  * Used as fallback routing awareness alongside hook-based enforcement.

package/build/adapters/codex/hooks.js

@@ -33,24 +33,23 @@ export const HOOK_TYPES = {
 // External MCP routing matcher (#529)
 // ─────────────────────────────────────────────────────────
 /**
- * Negative-lookahead matcher for external MCP tool namespaces on Codex CLI (#529).
+ * External MCP catch-all matcher for Codex CLI (#529, #547 hotfix).
  *
  * Codex CLI's hook `tool_name` payload uses `mcp__<server>__<tool>` for any
- * MCP-namespaced tool — verified by configs/codex/hooks.json which already
- * matches `mcp__.*__ctx_execute` style for context-mode's OWN MCP tools. This
- * pattern fires PreToolUse for any external `mcp__<server>__<tool>` whose
- * server segment does NOT contain `context-mode`. Without it, large payloads
- * from slack / telegram / gdrive / notion-style MCPs bypass the routing nudge
- * and flood the model's context — PostToolUse runs too late to keep raw data
- * out.
+ * MCP-namespaced tool. Originally this constant used a negative lookahead
+ * `mcp__(?!.*context-mode)` to exclude context-mode's own MCP tools at the
+ * matcher layer. v1.0.124 shipped that pattern and Codex (Rust `regex` crate)
+ * rejected the matcher at boot with "look-around not supported", breaking
+ * every Codex user (#547).
  *
- * The negative lookahead `(?!.*context-mode)` covers both naming variants
- * Codex sees in practice: the canonical `mcp__context-mode__ctx_*` AND the
- * Claude Code plugin shim `mcp__plugin_context-mode_context-mode__ctx_*`.
- * Codex own bare names (ctx_execute, local_shell, …) are not `mcp__`-prefixed
- * and are unaffected.
+ * Fix: drop the lookaround. The matcher is now a charset-clean literal
+ * (`[A-Za-z0-9_|]` only), satisfying Codex's `is_exact_matcher`
+ * (refs/platforms/codex/codex-rs/hooks/src/events/common.rs:152) which
+ * short-circuits the regex engine entirely. context-mode's own MCP tools are
+ * already filtered in the hook BODY by `isExternalMcpTool()` in
+ * hooks/core/routing.mjs — semantics preserved.
  */
-export const EXTERNAL_MCP_MATCHER_PATTERN = "mcp__(?!.*context-mode)";
+export const EXTERNAL_MCP_MATCHER_PATTERN = "mcp__";
 // ─────────────────────────────────────────────────────────
 // Routing instructions
 // ─────────────────────────────────────────────────────────

package/build/adapters/codex/index.js

@@ -18,14 +18,25 @@ import { resolve, dirname, join } from "node:path";
 import { fileURLToPath } from "node:url";
 import { BaseAdapter } from "../base.js";
 import { resolveCodexConfigDir } from "./paths.js";
-// PreToolUse matcher: canonical Codex tool names + context-mode own MCP tools
-// (both bare and `mcp__<server>__<tool>` forms) + external MCP catch-all (#529).
-// The final `mcp__(?!.*context-mode)` segment uses a negative lookahead that
-// excludes any `mcp__` tool whose server segment contains `context-mode` so
-// context-mode's own MCP tools (already wired by the explicit entries above)
-// are not double-routed. Keep this as a single string literal — `codex.test.ts`
-// drift-guard parses the source with a `"([^"]+)"` regex.
-const PRE_TOOL_USE_MATCHER_PATTERN = "local_shell|shell|shell_command|exec_command|container.exec|functions\\.exec_command|Bash|Shell|apply_patch|functions\\.apply_patch|Edit|Write|grep_files|ctx_execute|ctx_execute_file|ctx_batch_execute|ctx_fetch_and_index|ctx_search|ctx_index|mcp__.*__ctx_execute|mcp__.*__ctx_execute_file|mcp__.*__ctx_batch_execute|mcp__.*__ctx_fetch_and_index|mcp__.*__ctx_search|mcp__.*__ctx_index|mcp__(?!.*context-mode)";
+// PreToolUse matcher: canonical Codex tool names + context-mode bare MCP tool
+// names + external MCP catch-all literal (#529, #547 hotfix).
+//
+// Codex CLI's Rust `regex` crate does NOT support look-around, and
+// `is_exact_matcher` (refs/platforms/codex/codex-rs/hooks/src/events/common.rs:152)
+// short-circuits the regex engine entirely when the matcher contains only
+// [A-Za-z0-9_|]. v1.0.124 shipped a matcher with `(?!.*context-mode)` AND
+// `mcp__.*__ctx_*` regex syntax — Codex rejected the file at boot with
+// "look-around not supported" → all v1.0.124 Codex users broken (#547).
+//
+// Fix: keep only literal tool names (charset-clean). The hook BODY already
+// filters context-mode's own MCP tools via `isExternalMcpTool()` in
+// hooks/core/routing.mjs, so dropping `mcp__.*__ctx_*` and the lookaround
+// preserves end-to-end semantics. The literal `mcp__` final segment is a
+// no-op under exact-matcher mode but kept for parity with hooks/hooks.json.
+//
+// Keep this as a single string literal — `codex.test.ts` drift-guard parses
+// the source with a `"([^"]+)"` regex.
+const PRE_TOOL_USE_MATCHER_PATTERN = "local_shell|shell|shell_command|exec_command|Bash|Shell|apply_patch|Edit|Write|grep_files|ctx_execute|ctx_execute_file|ctx_batch_execute|ctx_fetch_and_index|ctx_search|ctx_index|mcp__";
 const CODEX_HOOK_COMMANDS = {
     PreToolUse: "context-mode hook codex pretooluse",
     PostToolUse: "context-mode hook codex posttooluse",

package/build/adapters/types.d.ts

@@ -206,6 +206,21 @@ export interface HookAdapter {
     writeSettings(settings: Record<string, unknown>): void;
     /** Validate that hooks are properly configured for this platform. */
     validateHooks(pluginRoot: string): DiagnosticResult[];
+    /**
+     * Adapter-defined per-platform health checks (Algo-D1).
+     *
+     * OPTIONAL. Adapters that don't override return nothing — they don't
+     * have this class of check today. claude-code overrides with hook-script
+     * existence checks that join `pluginRoot + scriptName` directly via
+     * `existsSync`, so doctor never round-trips through a regex on a hook
+     * command (the #548 root cause).
+     *
+     * Adapter #16 with hook scripts inherits the contract by overriding;
+     * adapter #17 without hook scripts simply doesn't override. The doctor
+     * iterates `adapter.getHealthChecks?.(pluginRoot) ?? []` and renders
+     * each — no per-adapter wiring in the doctor body.
+     */
+    getHealthChecks?(pluginRoot: string): readonly HealthCheck[];
     /** Check if the plugin is registered/enabled on this platform. */
     checkPluginRegistration(): DiagnosticResult;
     /** Get the installed version from this platform's registry/marketplace. */
@@ -230,6 +245,26 @@ export interface DiagnosticResult {
     /** Suggested fix command (if applicable). */
     fix?: string;
 }
+/**
+ * Adapter-defined health check (Algo-D1).
+ *
+ * Lighter-weight than `DiagnosticResult`: adapters declare a name and a
+ * synchronous `check()` thunk. The doctor renders the result. The
+ * thunk-style intentionally avoids forcing adapters into async — the
+ * existsSync probe used by claude-code is sync and the doctor invokes it
+ * directly without an `await`. Adapters needing async work return a
+ * pre-resolved status (the check ran at thunk-creation time) or extend
+ * `validateHooks()` instead.
+ */
+export interface HealthCheck {
+    /** Human-readable check title (e.g. "Hook script exists: pretooluse.mjs"). */
+    readonly name: string;
+    /** Synchronous check thunk. Returns OK or FAIL with optional detail. */
+    check(): {
+        status: "OK" | "FAIL";
+        detail?: string;
+    };
+}
 /**
  * Build a cross-platform `node <script>` command string.
  *
@@ -243,6 +278,28 @@ export interface DiagnosticResult {
  * Safe on macOS/Linux — quoting and forward slashes are no-ops there.
  */
 export declare function buildNodeCommand(scriptPath: string): string;
+/**
+ * Strict inverse of `buildNodeCommand`.
+ *
+ * Returns `{ nodePath, scriptPath }` ONLY when `cmd` could have been
+ * produced by `buildNodeCommand` — i.e. exactly two double-quoted args
+ * separated by whitespace. Anything else (bare `node …`, single quotes,
+ * unquoted ambiguous input, CLI dispatcher entries) returns `null`.
+ *
+ * Why strict: the legacy `\S+\.mjs` fallback in
+ * `src/util/hook-config.ts:24` and the two-step regex in
+ * `src/adapters/claude-code/hooks.ts:178` silently grabbed the path tail
+ * after the last whitespace whenever the host wire-format dropped quotes,
+ * producing the #548 doubled-path FAIL when `pluginRoot` contained
+ * spaces (e.g. `C:\Users\High Ground Services\…`). A canonical inverse
+ * lets every emit (`buildNodeCommand`) round-trip through every parse
+ * (`parseNodeCommand`) without inventing fallbacks. Adapter #16 inherits
+ * the contract by importing one module.
+ */
+export declare function parseNodeCommand(cmd: string): {
+    nodePath: string;
+    scriptPath: string;
+} | null;
 /** Supported platform identifiers. */
 export type PlatformId = "claude-code" | "gemini-cli" | "opencode" | "kilo" | "openclaw" | "codex" | "vscode-copilot" | "jetbrains-copilot" | "cursor" | "antigravity" | "kiro" | "pi" | "omp" | "zed" | "qwen-code" | "unknown";
 /** Detection signal used to identify which platform is running. */

package/build/adapters/types.js

@@ -33,3 +33,32 @@ export function buildNodeCommand(scriptPath) {
     const safePath = scriptPath.replace(/\\/g, "/");
     return `"${nodePath}" "${safePath}"`;
 }
+/**
+ * Strict inverse of `buildNodeCommand`.
+ *
+ * Returns `{ nodePath, scriptPath }` ONLY when `cmd` could have been
+ * produced by `buildNodeCommand` — i.e. exactly two double-quoted args
+ * separated by whitespace. Anything else (bare `node …`, single quotes,
+ * unquoted ambiguous input, CLI dispatcher entries) returns `null`.
+ *
+ * Why strict: the legacy `\S+\.mjs` fallback in
+ * `src/util/hook-config.ts:24` and the two-step regex in
+ * `src/adapters/claude-code/hooks.ts:178` silently grabbed the path tail
+ * after the last whitespace whenever the host wire-format dropped quotes,
+ * producing the #548 doubled-path FAIL when `pluginRoot` contained
+ * spaces (e.g. `C:\Users\High Ground Services\…`). A canonical inverse
+ * lets every emit (`buildNodeCommand`) round-trip through every parse
+ * (`parseNodeCommand`) without inventing fallbacks. Adapter #16 inherits
+ * the contract by importing one module.
+ */
+export function parseNodeCommand(cmd) {
+    if (typeof cmd !== "string" || cmd.length === 0)
+        return null;
+    // Match `"<nodePath>" "<scriptPath>"` with arbitrary whitespace
+    // separator. Both segments must be non-empty and contain no embedded
+    // double quotes — buildNodeCommand never emits embedded quotes.
+    const m = cmd.match(/^"([^"]+)"\s+"([^"]+)"\s*$/);
+    if (!m)
+        return null;
+    return { nodePath: m[1], scriptPath: m[2] };
+}