codiedev 0.9.88 → 0.9.90

package/dist/utils.d.ts

@@ -111,6 +111,10 @@ export declare function openCodeInstalled(): boolean;
  * keeps `codiedev connect` as the only setup step even when Codie/OpenCode is
  * installed later. OpenCode loads this file from its documented plugin dir. */
 export declare function installOpenCodeCapturePlugin(): void;
+/** Rewrite an OpenCode plugin installed by an older CLI: one that still wires
+ * the retired Agent Security tool hooks, or predates the prompt guard (it
+ * would let a stopped prompt through). Only touches an existing Codiedev plugin. */
+export declare function ensureOpenCodePluginCurrent(): void;
 export declare function piInstalled(): boolean;
 /** Subcommands the pi extension calls, in the order inspectPiExtension checks. */
 export declare const PI_EXTENSION_SUBCOMMANDS: readonly ["session-start-pi", "backup-pi", "capture-pi-final", "discover-pi", "security-pre-pi", "security-post-pi", "security-failure-pi"];
@@ -143,7 +147,7 @@ export declare function ensureAllCodiedevHooksInstalled(): void;
 export declare function hasDirectHookPath(configText: string): boolean;
 export declare function migrateHooksToLauncher(): string[];
 export declare function ensureSessionStartHookInstalled(): void;
-export declare const CODIEDEV_INSTRUCTIONS_BODY = "## Codiedev \u2014 team artifact layer\n\nThis machine is connected to Codiedev. Teammates share specs, reviews,\ndecisions, and messages via a CLI on every dev's machine.\n\n**When the user asks to share, push, ping, check messages, or capture a\nthought, use the `codiedev` CLI via Bash:**\n\n| Intent | Command |\n|---|---|\n| \"push this spec\" / \"save this as a skill\" | `codiedev push <file.md>` |\n| \"pull X\" / \"grab the latest spec-X\" / \"what did a teammate push?\" | `codiedev pull <key>` |\n| \"delete X\" / \"remove that test push\" / \"rm spec-old\" | `codiedev delete <key>` (always confirm with the user first) |\n| \"ping a teammate about this\" / \"ask someone for their take\" / \"send them this file\" | `codiedev ping <name> \"<msg>\" [--with <key>] [--file <path>]` |\n| \"any messages?\" / \"check my inbox\" / \"what did a teammate say?\" | `codiedev inbox` |\n| \"read that reply\" / \"mark that ping read\" | `codiedev read <ping-id>` |\n| \"reply to that\" / \"tell them X\" (answering a message from `codiedev inbox`) | `codiedev reply <ping-id> \"<msg>\" [--file <path>]` (not a new ping: this threads it and marks theirs answered) |\n| \"note that X is a follow-up\" / \"remember X\" | `codiedev note \"<text>\"` |\n| \"share with a teammate\" / \"give someone access\" (no notification) | `codiedev share <key> <name> [--role read\\|edit]` |\n| \"send this to a teammate\" / \"ask someone to look at this\" | `codiedev send <key> <name> [\"<msg>\"]` |\n| \"find something about X\" / \"has anyone solved Y?\" | `codiedev search \"<query>\" [--limit N]` |\n| \"show my library\" / \"what artifacts exist?\" | `codiedev library [--scope mine\\|shared\\|all] [--kind doc\\|skill]` |\n| \"run my agent's test cases\" / \"check the dataset on model Y\" / \"run v2 of the dataset\" | `codiedev traces cases <agent> [--dataset <name> [--version <n>]] [--model <id>]` (writes cases + RUN_CASES.md + results.json; follow it, then `codiedev traces report <results.json>`) |\n| \"how are my agents doing?\" / \"what's failing this week?\" / \"show the booking agent's failed runs\" / \"why did run X fail?\" | `codiedev traces overview`; `codiedev traces runs <agent> [--failed] [--flag <issue>] [--days n]`; `codiedev traces run <run> --agent <name>` (add `--json` to read the data yourself) |\n| \"add a helpfulness 1\u20135 score\" / \"make a review queue for tone\" | `codiedev traces score-kinds add <name> --type number --min 1 --max 5`; `codiedev traces queue create <name> --scores <a,b>` |\n| \"score that run 4 for helpfulness\" / \"how is my agent scoring?\" | `codiedev traces score <run> <score> <value> [--agent <name>] [--comment <why>]`; `codiedev traces scores <agent>` |\n| \"put this week's failed runs in the review queue\" | `codiedev traces queue list`; `codiedev traces queue add <queue> --agent <name> [--failed] [--days n]` |\n| \"have a judge score 10% of my agent's runs\" / \"turn off automatic scoring\" | `codiedev traces judge <agent> --on --scores <a,b> --sample 10 [--budget 25]`; `--off`; no flags shows it |\n| \"import these test cases from a CSV\" / \"add an example to the dataset\" / \"save the dataset as a version\" | `codiedev traces import <agent> <file> --dataset <name>`; `codiedev traces add-example <agent> --dataset <name> --input \"\u2026\" [--expected \"\u2026\"]`; `codiedev traces save-version <dataset>`; `codiedev traces versions <dataset>` |\n| \"make a starter pack\" / \"add this to our pack\" / \"package these skills for my team\" | write a `<slug>.pack.md` (start from `codiedev pack export <slug> --manifest --out .` for an existing pack), then `codiedev pack apply <file> [--publish]` \u2014 see **Starter packs** below |\n| \"publish the pack\" / \"ship the pack to my team\" | `codiedev pack publish <slug> [--channel stable\\|beta\\|alpha]` |\n| \"what was the last eval on X?\" / \"file these eval results\" | `codiedev evals last <subject>` before starting a related eval; `codiedev evals report <run.json>` after each variant runs (scores only \u2014 `codiedev evals help` for the shape) |\n\n**Starter packs** (team managers and admins): a pack.md is frontmatter\n(`name:`, `slug:`, optional `description:`) then sections. Ask the user\nwhat to include, write the file, run `codiedev pack apply <file> --dry-run`\nto show them, then apply for real:\n\n```\n---\nname: \"Healthcare scan\"\nslug: \"healthcare-scan\"\n---\n\n# Healthcare scan\n\n## Skills\n\n- ./skills/healthcare-scan\n- lint.md @teammate@example.com\n\n## Files\n\n- runner <- ~/.claude/runner\n```\n\nUnder **Skills**, a local path (`./\u2026`, `~/\u2026` or `/\u2026`) to a skill folder\nor SKILL.md is pushed to the library and added, with the rest of its folder\nshipped as the skill's files; `<key> @<author email>` adds a teammate's\nlibrary skill. **Files** maps local folders to paths in the pack\n(`.` is the pack root). In skills, point at shipped files relative to the\nskill's folder or with `${CLAUDE_PLUGIN_ROOT}/\u2026`. Applying changes the\ndraft; `--publish` (or `codiedev pack publish`) sends it to the team.\n\n**Just push the file \u2014 we'll figure out where it goes.** Every artifact\nis classified into one of two kinds at upload time:\n\n- **skill** \u2014 the file has SKILL.md frontmatter (`name:` + `description:`\n  inside a `---` block). Shows on the Skills page in the portal and is\n  invokable as a slash command (`/<name>`).\n- **doc** \u2014 everything else. Lives in the library: list it with\n  `codiedev library`, fetch it with `codiedev pull <key>`.\n\nDetection is content-based, not filename-based. The filename prefix\n(`spec-` / `decision-` / `proposal-` / `bugfix-` / `review-` /\n`note-`) is preserved as a *tag* you can filter by, but it never gates\nvisibility. A SKILL-frontmatter file named `note-foo.md` still becomes\na skill.\n\nThe `codiedev push` response always says where the artifact landed \u2014\nread it back to the user so they can confirm.\n\n**Resolving \"the spec we just worked on\":**\n- If a file was recently edited in this session matching the conventions\n  above, push that file.\n- If content was drafted inline in the conversation, write it to a file\n  first (e.g., `/tmp/spec-xxx.md`) then push.\n\n**Teammate names:** first name usually works (`codiedev ping <name> ...`).\nIf ambiguous, the CLI returns candidates \u2014 retry with the full email.\n\n**Search before pushing.** For any \"save this as \u2026\" request, run\n`codiedev search \"<query>\"` first. If prior art exists, pull it and\niterate rather than duplicating.\n\n**Sharing vs sending:** `codiedev share` is silent (access only, no\nnotification). `codiedev send` both grants access AND pings the\nrecipient. Use send when the user is actively looping someone in.\n\n**Errors:**\n- \"not connected\" \u2192 user needs to run `npx codiedev connect` with their\n  API token from https://codiedev.com/portal/integrations/claude-code\n- \"ambiguous recipient\" \u2192 surface candidates to the user\n";
+export declare const CODIEDEV_INSTRUCTIONS_BODY = "## Codiedev \u2014 team artifact layer\n\nThis machine is connected to Codiedev. Teammates share specs, reviews,\ndecisions, and messages via a CLI on every dev's machine.\n\n**When the user asks to share, push, ping, check messages, or capture a\nthought, use the `codiedev` CLI via Bash:**\n\n| Intent | Command |\n|---|---|\n| \"push this spec\" / \"save this as a skill\" | `codiedev push <file.md>` |\n| \"pull X\" / \"grab the latest spec-X\" / \"what did a teammate push?\" | `codiedev pull <key>` |\n| \"delete X\" / \"remove that test push\" / \"rm spec-old\" | `codiedev delete <key>` (always confirm with the user first) |\n| \"ping a teammate about this\" / \"send them this spec\" / \"send them this file\" | `codiedev ping <name> \"<msg>\" [--with <key>] [--file <path>]` (`--with` also gives them access) |\n| \"any messages?\" / \"check my inbox\" / \"what did a teammate say?\" | `codiedev inbox` |\n| \"read that reply\" / \"mark that ping read\" | `codiedev read <ping-id>` |\n| \"reply to that\" / \"tell them X\" (answering a message from `codiedev inbox`) | `codiedev reply <ping-id> \"<msg>\" [--file <path>]` (not a new ping: this threads it and marks theirs answered) |\n| \"note that X is a follow-up\" / \"remember X\" | `codiedev note \"<text>\"` |\n| \"share with a teammate\" / \"give someone access\" (no notification) | `codiedev ping <name> --with <key> [--edit]` (no message = silent share) |\n| \"find something about X\" / \"has anyone solved Y?\" | `codiedev search \"<query>\" [--limit N]` |\n| \"show my library\" / \"what artifacts exist?\" | `codiedev library [--scope mine\\|shared\\|all] [--kind doc\\|skill]` |\n| \"run my agent's test cases\" / \"check the dataset on model Y\" / \"run v2 of the dataset\" | `codiedev traces cases <agent> [--dataset <name> [--version <n>]] [--model <id>]` (writes cases + RUN_CASES.md + results.json; follow it, then `codiedev traces report <results.json>`) |\n| \"how are my agents doing?\" / \"what's failing this week?\" / \"show the booking agent's failed runs\" / \"why did run X fail?\" | `codiedev traces overview`; `codiedev traces runs <agent> [--failed] [--flag <issue>] [--days n]`; `codiedev traces run <run> --agent <name>` (add `--json` to read the data yourself) |\n| \"add a helpfulness 1\u20135 score\" / \"make a review queue for tone\" | `codiedev traces score-kinds add <name> --type number --min 1 --max 5`; `codiedev traces queue create <name> --scores <a,b>` |\n| \"score that run 4 for helpfulness\" / \"how is my agent scoring?\" | `codiedev traces score <run> <score> <value> [--agent <name>] [--comment <why>]`; `codiedev traces scores <agent>` |\n| \"put this week's failed runs in the review queue\" | `codiedev traces queue list`; `codiedev traces queue add <queue> --agent <name> [--failed] [--days n]` |\n| \"have a judge score 10% of my agent's runs\" / \"turn off automatic scoring\" | `codiedev traces judge <agent> --on --scores <a,b> --sample 10 [--budget 25]`; `--off`; no flags shows it |\n| \"import these test cases from a CSV\" / \"add an example to the dataset\" / \"save the dataset as a version\" | `codiedev traces import <agent> <file> --dataset <name>`; `codiedev traces add-example <agent> --dataset <name> --input \"\u2026\" [--expected \"\u2026\"]`; `codiedev traces save-version <dataset>`; `codiedev traces versions <dataset>` |\n| \"make a starter pack\" / \"add this to our pack\" / \"package these skills for my team\" | write a `<slug>.pack.md` (start from `codiedev pack export <slug> --manifest --out .` for an existing pack), then `codiedev pack apply <file> [--publish]` \u2014 see **Starter packs** below |\n| \"publish the pack\" / \"ship the pack to my team\" | `codiedev pack publish <slug> [--channel stable\\|beta\\|alpha]` |\n| \"what was the last eval on X?\" / \"file these eval results\" | `codiedev evals last <subject>` before starting a related eval; `codiedev evals report <run.json>` after each variant runs (scores only \u2014 `codiedev evals help` for the shape) |\n\n**Starter packs** (team managers and admins): a pack.md is frontmatter\n(`name:`, `slug:`, optional `description:`) then sections. Ask the user\nwhat to include, write the file, run `codiedev pack apply <file> --dry-run`\nto show them, then apply for real:\n\n```\n---\nname: \"Healthcare scan\"\nslug: \"healthcare-scan\"\n---\n\n# Healthcare scan\n\n## Skills\n\n- ./skills/healthcare-scan\n- lint.md @teammate@example.com\n\n## Files\n\n- runner <- ~/.claude/runner\n```\n\nUnder **Skills**, a local path (`./\u2026`, `~/\u2026` or `/\u2026`) to a skill folder\nor SKILL.md is pushed to the library and added, with the rest of its folder\nshipped as the skill's files; `<key> @<author email>` adds a teammate's\nlibrary skill. **Files** maps local folders to paths in the pack\n(`.` is the pack root). In skills, point at shipped files relative to the\nskill's folder or with `${CLAUDE_PLUGIN_ROOT}/\u2026`. Applying changes the\ndraft; `--publish` (or `codiedev pack publish`) sends it to the team.\n\n**Just push the file \u2014 we'll figure out where it goes.** Every artifact\nis classified into one of two kinds at upload time:\n\n- **skill** \u2014 the file has SKILL.md frontmatter (`name:` + `description:`\n  inside a `---` block). Shows on the Skills page in the portal and is\n  invokable as a slash command (`/<name>`).\n- **doc** \u2014 everything else. Lives in the library: list it with\n  `codiedev library`, fetch it with `codiedev pull <key>`.\n\nDetection is content-based, not filename-based. The filename prefix\n(`spec-` / `decision-` / `proposal-` / `bugfix-` / `review-` /\n`note-`) is preserved as a *tag* you can filter by, but it never gates\nvisibility. A SKILL-frontmatter file named `note-foo.md` still becomes\na skill.\n\nThe `codiedev push` response always says where the artifact landed \u2014\nread it back to the user so they can confirm.\n\n**Resolving \"the spec we just worked on\":**\n- If a file was recently edited in this session matching the conventions\n  above, push that file.\n- If content was drafted inline in the conversation, write it to a file\n  first (e.g., `/tmp/spec-xxx.md`) then push.\n\n**Teammate names:** first name usually works (`codiedev ping <name> ...`).\nIf ambiguous, the CLI returns candidates \u2014 retry with the full email.\n\n**Search before pushing.** For any \"save this as \u2026\" request, run\n`codiedev search \"<query>\"` first. If prior art exists, pull it and\niterate rather than duplicating.\n\n**One command for messaging and sharing:** `codiedev ping`. A message\nlands in their inbox and emails them; `--with <key>` also gives them read\naccess (`--edit` for edit). With `--with` and no message it's a silent\nshare. (`codiedev send` / `share` still work as aliases.)\n\n**Errors:**\n- \"not connected\" \u2192 user needs to run `npx codiedev connect` with their\n  API token from https://codiedev.com/portal/integrations/claude-code\n- \"ambiguous recipient\" \u2192 surface candidates to the user\n";
 /** The full Codiedev instructions (team-skill context + command table), for
  * harnesses Codiedev launches itself (Codie, Codie's pi) rather than a
  * user-owned instructions file. */

package/dist/utils.js

@@ -64,6 +64,7 @@ exports.cursorInstalled = cursorInstalled;
 exports.copilotInstalled = copilotInstalled;
 exports.openCodeInstalled = openCodeInstalled;
 exports.installOpenCodeCapturePlugin = installOpenCodeCapturePlugin;
+exports.ensureOpenCodePluginCurrent = ensureOpenCodePluginCurrent;
 exports.piInstalled = piInstalled;
 exports.piExtensionSource = piExtensionSource;
 exports.installPiExtension = installPiExtension;
@@ -1165,6 +1166,22 @@ function installOpenCodeCapturePlugin() {
         `    const cwd = worktree || directory || process.cwd();\n` +
         `    const prompt = Array.isArray(output?.parts) ? output.parts.filter((part) => part?.type === "text").map((part) => part.text || "").join("\\n") : "";\n` +
         `    const decision = invokeSync(PROMPT, { session_id: id, cwd, prompt });\n` +
+        `    if (decision?.decision === "block") {\n` +
+        `      // A key in the prompt (Team Security setting): stop it before the model.\n` +
+        `      const reason = String(decision.reason || "Codiedev stopped this prompt.");\n` +
+        `      const toast = { title: "Prompt not sent", message: reason, variant: "error", duration: 12000 };\n` +
+        `      // Older SDKs take { body }, newer ones the fields themselves. The TUI\n` +
+        `      // follows a stopped prompt with its own generic \"Failed to send\n` +
+        `      // prompt\" toast; show ours now and again just after, so ours stays up.\n` +
+        `      const show = () => { try { Promise.resolve(client.tui.showToast({ body: toast, ...toast })).catch(() => {}); } catch {} };\n` +
+        `      show();\n` +
+        `      setTimeout(show, 600);\n` +
+        `      if (process.env.CODIEDEV_PROMPT_BLOCK_OUTPUT === "marker") {\n` +
+        `        process.stderr.write("__CODIEDEV_PROMPT_BLOCKED__" + JSON.stringify({ reason }) + "\\n");\n` +
+        `        process.exit(3);\n` +
+        `      }\n` +
+        `      throw new Error(reason);\n` +
+        `    }\n` +
         `    const context = decision?.hookSpecificOutput?.additionalContext;\n` +
         `    if (context && Array.isArray(output?.parts)) {\n` +
         `      // Preserve the native part IDs required by current engine schemas.\n` +
@@ -1215,6 +1232,20 @@ function installOpenCodeCapturePlugin() {
     fs.writeFileSync(OPENCODE_PLUGIN_PATH, source, { encoding: "utf8", mode: 0o600 });
     fs.chmodSync(OPENCODE_PLUGIN_PATH, 0o600);
 }
+/** Rewrite an OpenCode plugin installed by an older CLI: one that still wires
+ * the retired Agent Security tool hooks, or predates the prompt guard (it
+ * would let a stopped prompt through). Only touches an existing Codiedev plugin. */
+function ensureOpenCodePluginCurrent() {
+    try {
+        if (!fs.existsSync(OPENCODE_PLUGIN_PATH))
+            return;
+        const current = fs.readFileSync(OPENCODE_PLUGIN_PATH, "utf8");
+        if (!current.includes("SECURITY_PRE") && current.includes("CODIEDEV_PROMPT_BLOCK_OUTPUT"))
+            return;
+        installOpenCodeCapturePlugin();
+    }
+    catch { /* best-effort */ }
+}
 function piInstalled() {
     if (fs.existsSync((0, harnessDirs_1.piAgentDir)()))
         return true;
@@ -1318,8 +1349,14 @@ function piExtensionSource(agentSecurityEnabled) {
         `    if (event?.source === "extension") return { action: "continue" };\n` +
         `    const s = current(ctx);\n` +
         `    const decision = invokeSync(PROMPT, { session_id: s.id, cwd: s.cwd, prompt: event?.text ?? "" });\n` +
-        `    const reason = blockReason(decision);\n` +
-        `    if (reason) { warn(ctx, reason); return { action: "handled" }; }\n` +
+        `    if (decision?.decision === "block") {\n` +
+        `      // A key in the prompt (Team Security setting): pi never sends it.\n` +
+        `      const reason = String(decision.reason || "Codiedev stopped this prompt.");\n` +
+        `      if (ctx?.hasUI) { try { ctx.ui.notify(reason, "error"); } catch { process.stderr.write("\\n" + reason + "\\n"); } }\n` +
+        `      else process.stderr.write("\\n" + reason + "\\n");\n` +
+        `      pendingContext = null;\n` +
+        `      return { action: "handled" };\n` +
+        `    }\n` +
         `    pendingContext = decision?.hookSpecificOutput?.additionalContext || null;\n` +
         `    return { action: "continue" };\n` +
         `  });\n\n` +
@@ -1674,13 +1711,12 @@ thought, use the \`codiedev\` CLI via Bash:**
 | "push this spec" / "save this as a skill" | \`codiedev push <file.md>\` |
 | "pull X" / "grab the latest spec-X" / "what did a teammate push?" | \`codiedev pull <key>\` |
 | "delete X" / "remove that test push" / "rm spec-old" | \`codiedev delete <key>\` (always confirm with the user first) |
-| "ping a teammate about this" / "ask someone for their take" / "send them this file" | \`codiedev ping <name> "<msg>" [--with <key>] [--file <path>]\` |
+| "ping a teammate about this" / "send them this spec" / "send them this file" | \`codiedev ping <name> "<msg>" [--with <key>] [--file <path>]\` (\`--with\` also gives them access) |
 | "any messages?" / "check my inbox" / "what did a teammate say?" | \`codiedev inbox\` |
 | "read that reply" / "mark that ping read" | \`codiedev read <ping-id>\` |
 | "reply to that" / "tell them X" (answering a message from \`codiedev inbox\`) | \`codiedev reply <ping-id> "<msg>" [--file <path>]\` (not a new ping: this threads it and marks theirs answered) |
 | "note that X is a follow-up" / "remember X" | \`codiedev note "<text>"\` |
-| "share with a teammate" / "give someone access" (no notification) | \`codiedev share <key> <name> [--role read\\|edit]\` |
-| "send this to a teammate" / "ask someone to look at this" | \`codiedev send <key> <name> ["<msg>"]\` |
+| "share with a teammate" / "give someone access" (no notification) | \`codiedev ping <name> --with <key> [--edit]\` (no message = silent share) |
 | "find something about X" / "has anyone solved Y?" | \`codiedev search "<query>" [--limit N]\` |
 | "show my library" / "what artifacts exist?" | \`codiedev library [--scope mine\\|shared\\|all] [--kind doc\\|skill]\` |
 | "run my agent's test cases" / "check the dataset on model Y" / "run v2 of the dataset" | \`codiedev traces cases <agent> [--dataset <name> [--version <n>]] [--model <id>]\` (writes cases + RUN_CASES.md + results.json; follow it, then \`codiedev traces report <results.json>\`) |
@@ -1756,9 +1792,10 @@ If ambiguous, the CLI returns candidates — retry with the full email.
 \`codiedev search "<query>"\` first. If prior art exists, pull it and
 iterate rather than duplicating.
 
-**Sharing vs sending:** \`codiedev share\` is silent (access only, no
-notification). \`codiedev send\` both grants access AND pings the
-recipient. Use send when the user is actively looping someone in.
+**One command for messaging and sharing:** \`codiedev ping\`. A message
+lands in their inbox and emails them; \`--with <key>\` also gives them read
+access (\`--edit\` for edit). With \`--with\` and no message it's a silent
+share. (\`codiedev send\` / \`share\` still work as aliases.)
 
 **Errors:**
 - "not connected" → user needs to run \`npx codiedev connect\` with their
@@ -2259,10 +2296,10 @@ function installCursorHook() {
     replaceManaged("stop", ["backup-cursor"]);
     for (const event of ["postToolUse", "postToolUseFailure", "subagentStart", "subagentStop"])
         replaceManaged(event, ["observe-cursor"]);
-    // Cursor cannot inject dynamic context from beforeSubmitPrompt today.
-    // Remove older Codiedev discovery entries so prompts are not uploaded for
-    // a response the host will discard; preserve any third-party hooks.
-    replaceManaged("beforeSubmitPrompt", []);
+    // Stops a prompt with a key in it when the company turned that on (a quick
+    // local no-op otherwise). It also replaces older Codiedev discovery entries,
+    // so prompts are not uploaded for a response the host will discard.
+    replaceManaged("beforeSubmitPrompt", ["prompt-guard-cursor"]);
     fs.writeFileSync(CURSOR_HOOKS_PATH, JSON.stringify(hooksFile, null, 2), "utf8");
 }
 // GitHub Copilot reads every `$COPILOT_HOME/hooks/*.json`, so Codiedev owns
@@ -2358,6 +2395,7 @@ function ensureCursorCodiedevHooksInstalled() {
             ["postToolUseFailure", "observe-cursor"],
             ["subagentStart", "observe-cursor"],
             ["subagentStop", "observe-cursor"],
+            ["beforeSubmitPrompt", "prompt-guard-cursor"],
         ];
         const has = (eventName, subcommand) => {
             const entries = hooks[eventName];
@@ -2369,7 +2407,8 @@ function ensureCursorCodiedevHooksInstalled() {
             });
         };
         const promptEntries = hooks.beforeSubmitPrompt;
-        const hasStalePromptHook = Array.isArray(promptEntries) && promptEntries.some((entry) => (0, detection_1.isCodiedevHookCommand)(entry.command));
+        const hasStalePromptHook = Array.isArray(promptEntries) && promptEntries.some((entry) => (0, detection_1.isCodiedevHookCommand)(entry.command)
+            && !String(entry.command ?? "").trim().endsWith("prompt-guard-cursor"));
         if (!required.every(([eventName, subcommand]) => has(eventName, subcommand)) ||
             hasStalePromptHook) {
             installCursorHook();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codiedev",
-  "version": "0.9.88",
+  "version": "0.9.90",
   "description": "Connect Claude Code, Codex, Cursor, OpenCode, or VS Code Copilot to Codiedev for team session capture and artifact collaboration — and run the governed Codie harness",
   "bin": {
     "codiedev": "dist/cli.js",