codiedev 0.7.10 → 0.8.0

package/dist/commands/share.js

@@ -0,0 +1,87 @@
+"use strict";
+// `codiedev share <filename> <recipient> [--role read|edit]` — silently
+// grant a teammate access to an artifact (no notification). Use
+// `codiedev send` instead when the user wants to actively loop someone in.
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.runShare = runShare;
+const shared_1 = require("./shared");
+const VALID_ROLES = new Set(["read", "edit"]);
+function parseArgs(args) {
+    let filename;
+    let to;
+    let role;
+    for (let i = 0; i < args.length; i++) {
+        const a = args[i];
+        if (a === "--role" && i + 1 < args.length) {
+            role = args[++i];
+        }
+        else if (a.startsWith("--role=")) {
+            role = a.slice("--role=".length);
+        }
+        else if (!a.startsWith("--")) {
+            if (filename === undefined)
+                filename = a;
+            else if (to === undefined)
+                to = a;
+        }
+    }
+    if (!filename || !to) {
+        console.error("Usage: codiedev share <filename> <recipient> [--role read|edit]");
+        process.exit(1);
+    }
+    if (role && !VALID_ROLES.has(role)) {
+        console.error(`Invalid --role. Valid: ${[...VALID_ROLES].join(", ")}`);
+        process.exit(1);
+    }
+    return { filename, to, role: (role ?? "read") };
+}
+async function runShare(args, configOverride) {
+    const parsed = parseArgs(args);
+    const config = configOverride ?? (0, shared_1.requireConfig)();
+    const start = Date.now();
+    try {
+        const res = await (0, shared_1.apiRequest)("POST", "/api/cli/share-with", {
+            config,
+            body: {
+                filename: parsed.filename,
+                to: parsed.to,
+                role: parsed.role,
+            },
+        });
+        (0, shared_1.recordAgentEvent)(config, {
+            tool: "codiedev_share_with",
+            ok: true,
+            latencyMs: Date.now() - start,
+        });
+        const who = res.recipient ? `${res.recipient.name} (${res.recipient.email})` : parsed.to;
+        if (res.noop) {
+            console.log(`Already shared with ${who}.`);
+        }
+        else if (res.updated) {
+            console.log(`Updated access for ${who} to ${parsed.role}.`);
+        }
+        else {
+            console.log(`Shared ${parsed.filename} with ${who} (${parsed.role}).`);
+        }
+    }
+    catch (err) {
+        (0, shared_1.recordAgentEvent)(config, {
+            tool: "codiedev_share_with",
+            ok: false,
+            latencyMs: Date.now() - start,
+            error: err.message,
+        });
+        // Ambiguous recipients return 409 with candidates in the body.
+        const body = err.body;
+        if (body && Array.isArray(body.candidates) && body.candidates.length > 0) {
+            console.error(`Recipient "${parsed.to}" is ambiguous. Candidates:`);
+            for (const c of body.candidates) {
+                console.error(`  - ${c.name} (${c.email})`);
+            }
+        }
+        else {
+            console.error(`Share failed: ${err.message}`);
+        }
+        process.exit(1);
+    }
+}

package/dist/commands/shared.d.ts

@@ -1,4 +1,12 @@
 import { CodiedevConfig } from "../utils";
+/**
+ * Layer per-command env overrides on top of the on-disk config. Useful for
+ * ad-hoc testing — point a prod-connected CLI at a dev Convex deployment
+ * without re-running `codiedev connect`. Both CODIEDEV_URL and CODIEDEV_TOKEN
+ * must be set together (half-overrides would mismatch URL and auth realm).
+ * Other fields (companyId, repos[]) come from the file unchanged.
+ */
+export declare function applyConfigEnvOverrides(config: CodiedevConfig): CodiedevConfig;
 /**
  * Require a connected CodieDev config. Exits the process with a helpful
  * message if the user hasn't run `codiedev connect` yet.
@@ -13,12 +21,30 @@ export declare function apiRequest<T = unknown>(method: "GET" | "POST", path: st
     body?: Record<string, unknown>;
     query?: Record<string, string | number | undefined>;
 }): Promise<T>;
+/**
+ * Fire-and-forget per-invocation telemetry from CLI subcommands. Mirrors
+ * the MCP server's emitTelemetry but stamps `source: "cli"` so adoption
+ * dashboards can distinguish between the two surfaces. Never blocks the
+ * user's command, never throws — telemetry must not change behavior.
+ */
+export declare function recordAgentEvent(config: CodiedevConfig, event: {
+    tool: string;
+    ok: boolean;
+    latencyMs: number;
+    error?: string;
+}): void;
+/**
+ * Wraps a CLI subcommand body so success and failure both record telemetry
+ * and the original error propagates after the event is queued. Use this in
+ * each `runXxx` command instead of inline timing + try/catch boilerplate.
+ */
+export declare function withTelemetry<T>(config: CodiedevConfig, tool: string, fn: () => Promise<T>): Promise<T>;
 /**
  * Relative-time formatter for inbox / listing output.
  */
 export declare function timeAgo(ts: number): string;
 /**
  * Strip surrounding quotes from a CLI argument if the user wrapped it.
- * `codiedev ping maya "hey"` on some shells passes the quotes through.
+ * `codiedev ping <name> "hey"` on some shells passes the quotes through.
  */
 export declare function stripQuotes(s: string): string;

package/dist/commands/shared.js

@@ -33,14 +33,32 @@ var __importStar = (this && this.__importStar) || (function () {
     };
 })();
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.applyConfigEnvOverrides = applyConfigEnvOverrides;
 exports.requireConfig = requireConfig;
 exports.apiRequest = apiRequest;
+exports.recordAgentEvent = recordAgentEvent;
+exports.withTelemetry = withTelemetry;
 exports.timeAgo = timeAgo;
 exports.stripQuotes = stripQuotes;
 const https = __importStar(require("https"));
 const http = __importStar(require("http"));
 const utils_1 = require("../utils");
 const version_1 = require("../version");
+/**
+ * Layer per-command env overrides on top of the on-disk config. Useful for
+ * ad-hoc testing — point a prod-connected CLI at a dev Convex deployment
+ * without re-running `codiedev connect`. Both CODIEDEV_URL and CODIEDEV_TOKEN
+ * must be set together (half-overrides would mismatch URL and auth realm).
+ * Other fields (companyId, repos[]) come from the file unchanged.
+ */
+function applyConfigEnvOverrides(config) {
+    const url = process.env.CODIEDEV_URL;
+    const token = process.env.CODIEDEV_TOKEN;
+    if (url && token) {
+        return { ...config, backendUrl: url, token };
+    }
+    return config;
+}
 /**
  * Require a connected CodieDev config. Exits the process with a helpful
  * message if the user hasn't run `codiedev connect` yet.
@@ -51,7 +69,7 @@ function requireConfig() {
         console.error("Not connected. Run `npx codiedev connect` first and enter your API token.");
         process.exit(1);
     }
-    return config;
+    return applyConfigEnvOverrides(config);
 }
 /**
  * Perform an authenticated HTTP request against the CodieDev backend.
@@ -116,6 +134,49 @@ function apiRequest(method, path, options) {
         req.end();
     });
 }
+/**
+ * Fire-and-forget per-invocation telemetry from CLI subcommands. Mirrors
+ * the MCP server's emitTelemetry but stamps `source: "cli"` so adoption
+ * dashboards can distinguish between the two surfaces. Never blocks the
+ * user's command, never throws — telemetry must not change behavior.
+ */
+function recordAgentEvent(config, event) {
+    apiRequest("POST", "/api/telemetry/mcp-event", {
+        config,
+        body: {
+            tool: event.tool,
+            ok: event.ok,
+            latencyMs: event.latencyMs,
+            error: event.error,
+            mcpVersion: version_1.CLI_VERSION,
+            source: "cli",
+        },
+    }).catch(() => {
+        // Swallow — telemetry must never affect user-facing flow.
+    });
+}
+/**
+ * Wraps a CLI subcommand body so success and failure both record telemetry
+ * and the original error propagates after the event is queued. Use this in
+ * each `runXxx` command instead of inline timing + try/catch boilerplate.
+ */
+async function withTelemetry(config, tool, fn) {
+    const start = Date.now();
+    try {
+        const result = await fn();
+        recordAgentEvent(config, { tool, ok: true, latencyMs: Date.now() - start });
+        return result;
+    }
+    catch (err) {
+        recordAgentEvent(config, {
+            tool,
+            ok: false,
+            latencyMs: Date.now() - start,
+            error: err.message?.slice(0, 240),
+        });
+        throw err;
+    }
+}
 /**
  * Relative-time formatter for inbox / listing output.
  */
@@ -134,7 +195,7 @@ function timeAgo(ts) {
 }
 /**
  * Strip surrounding quotes from a CLI argument if the user wrapped it.
- * `codiedev ping maya "hey"` on some shells passes the quotes through.
+ * `codiedev ping <name> "hey"` on some shells passes the quotes through.
  */
 function stripQuotes(s) {
     if ((s.startsWith('"') && s.endsWith('"')) ||

package/dist/connect.js

@@ -111,7 +111,7 @@ function promptHidden(question) {
         stdin.on("data", onData);
     });
 }
-function postJson(url, body) {
+function postJson(url, body, extraHeaders = {}) {
     return new Promise((resolve, reject) => {
         const parsed = new URL(url);
         const data = JSON.stringify(body);
@@ -124,6 +124,7 @@ function postJson(url, body) {
                 "Content-Type": "application/json",
                 "Content-Length": Buffer.byteLength(data),
                 "X-Codiedev-Cli-Version": version_1.CLI_VERSION,
+                ...extraHeaders,
             },
         };
         const lib = parsed.protocol === "https:" ? https : http;
@@ -213,16 +214,44 @@ async function runConnect(args = []) {
         console.error(`\nError: Failed to save config — ${err.message}`);
         process.exit(1);
     }
+    // Migration: strip MCP server entries written by pre-CLI-only versions
+    // of `codiedev connect`. These pointed at `npx codiedev-mcp`, a binary
+    // that was removed in 0.3.4 and that 0.7.11+ no longer ships. Without
+    // cleanup, customers upgrading from any prior version see persistent
+    // "MCP server failed to start" errors in their agent UIs even though
+    // the CLI works fine. Each helper is idempotent and a no-op when the
+    // relevant config file doesn't exist.
+    //
+    // Each call is wrapped because the user's upgrade path matters more
+    // than the cleanup. A locked / wrong-owner config file (rare but real)
+    // shouldn't block the install loop or strand them on an old version.
+    for (const [label, fn] of [
+        ["Claude Code", utils_1.cleanupClaudeCodeMcp],
+        ["Codex", utils_1.cleanupCodexMcp],
+        ["Cursor", utils_1.cleanupCursorMcp],
+        ["VS Code", utils_1.cleanupVSCodeMcp],
+    ]) {
+        try {
+            fn();
+        }
+        catch (err) {
+            console.warn(`\nWarning: Couldn't clean up legacy ${label} MCP entry — ${err.message}`);
+            console.warn("Continuing with install. The stale entry won't break the CLI but the agent may show a broken-MCP indicator until you remove it manually.");
+        }
+    }
     const hasClaude = (0, utils_1.claudeCodeInstalled)();
     const hasCodex = (0, utils_1.codexInstalled)();
     const hasCursor = (0, utils_1.cursorInstalled)();
-    const hasVSCodeCopilot = (0, utils_1.vscodeCopilotInstalled)();
     const installed = [];
-    let vscodeMcpInstalled = false;
+    // Machine-readable target keys reported back to the backend via
+    // /api/cli/markInstalled so the portal's "Connected" state reflects
+    // what's actually wired up on this machine, not just "token validated."
+    const installedTargets = [];
     if (hasClaude) {
         try {
             (0, utils_1.installHook)();
             installed.push("Claude Code SessionEnd hook (~/.claude/settings.json)");
+            installedTargets.push("claudeCode-hook");
         }
         catch (err) {
             console.error(`\nWarning: Failed to install Claude Code hook — ${err.message}`);
@@ -230,22 +259,17 @@ async function runConnect(args = []) {
         try {
             (0, utils_1.installClaudeCodeInstructions)();
             installed.push("Claude Code agent instructions (~/.claude/CLAUDE.md)");
+            installedTargets.push("claudeCode-instructions");
         }
         catch (err) {
             console.error(`\nWarning: Failed to install Claude Code instructions — ${err.message}`);
         }
-        try {
-            (0, utils_1.installClaudeCodeMcp)();
-            installed.push("Claude Code MCP server (~/.claude.json)");
-        }
-        catch (err) {
-            console.error(`\nWarning: Failed to install Claude Code MCP server — ${err.message}`);
-        }
     }
     if (hasCodex) {
         try {
             (0, utils_1.installCodexHook)();
             installed.push("Codex Stop hook (~/.codex/hooks.json)");
+            installedTargets.push("codex-hook");
         }
         catch (err) {
             console.error(`\nWarning: Failed to install Codex hook — ${err.message}`);
@@ -253,22 +277,17 @@ async function runConnect(args = []) {
         try {
             (0, utils_1.installCodexInstructions)();
             installed.push("Codex agent instructions (~/.codex/AGENTS.md)");
+            installedTargets.push("codex-instructions");
         }
         catch (err) {
             console.error(`\nWarning: Failed to install Codex instructions — ${err.message}`);
         }
-        try {
-            (0, utils_1.installCodexMcp)();
-            installed.push("Codex MCP server (~/.codex/config.toml)");
-        }
-        catch (err) {
-            console.error(`\nWarning: Failed to install Codex MCP server — ${err.message}`);
-        }
     }
     if (hasCursor) {
         try {
             (0, utils_1.installCursorHook)();
             installed.push("Cursor sessionEnd hook (~/.cursor/hooks.json)");
+            installedTargets.push("cursor-hook");
         }
         catch (err) {
             console.error(`\nWarning: Failed to install Cursor hook — ${err.message}`);
@@ -276,30 +295,29 @@ async function runConnect(args = []) {
         try {
             (0, utils_1.installCursorInstructions)();
             installed.push("Cursor agent instructions (~/.cursor/rules/codiedev.mdc)");
+            installedTargets.push("cursor-instructions");
         }
         catch (err) {
             console.error(`\nWarning: Failed to install Cursor instructions — ${err.message}`);
         }
-        try {
-            (0, utils_1.installCursorMcp)();
-            installed.push("Cursor MCP server (~/.cursor/mcp.json)");
-        }
-        catch (err) {
-            console.error(`\nWarning: Failed to install Cursor MCP server — ${err.message}`);
-        }
     }
-    if (hasVSCodeCopilot) {
+    // Tell the backend which targets we wired up so the portal's onboarding
+    // card flips to "Connected" only when something actually installed —
+    // not on bare token validation. Best-effort: a network failure here
+    // doesn't undo the local install, and `codiedev doctor` still works.
+    if (installedTargets.length > 0) {
         try {
-            (0, utils_1.installVSCodeMcp)();
-            installed.push("VS Code Copilot MCP server (~/Library/Application Support/Code/User/mcp.json)");
-            vscodeMcpInstalled = true;
+            await postJson(`${BACKEND_URL}/api/cli/markInstalled`, {
+                installedTargets,
+            }, { Authorization: `Bearer ${token}` });
         }
         catch (err) {
-            console.error(`\nWarning: Failed to install VS Code Copilot MCP server — ${err.message}`);
+            console.error(`\nWarning: Failed to report install to backend — ${err.message}`);
+            console.error("Local install succeeded; portal may not reflect it until you re-run.");
         }
     }
-    if (!hasClaude && !hasCodex && !hasCursor && !hasVSCodeCopilot) {
-        console.warn("\nNo Claude Code, Codex, Cursor, or VS Code Copilot install detected.");
+    if (!hasClaude && !hasCodex && !hasCursor) {
+        console.warn("\nNo Claude Code, Codex, or Cursor install detected.");
         console.warn("If you just installed Claude Code, launch it once (so ~/.claude is created),");
         console.warn("then re-run `npx codiedev connect` to wire up the capture hook.");
     }
@@ -312,13 +330,6 @@ async function runConnect(args = []) {
         }
         console.log("Sessions will be captured automatically.");
     }
-    if (vscodeMcpInstalled) {
-        console.log();
-        console.log("VS Code: open Copilot Chat — it will prompt you to trust the codiedev MCP server.");
-        console.log("Click Allow once, then ask Copilot: \"create a reverse ticket from my current changes\".");
-        console.log("Note: Copilot doesn't expose chat transcripts to MCP, so on-demand tools (reverse_ticket,");
-        console.log("push, pull, ask, ping) work fully — auto-captured decisions need Claude Code or Codex.");
-    }
     console.log();
     console.log("Run `codiedev doctor` to verify everything's wired up.");
     console.log();

package/dist/createTicketSkill.d.ts

@@ -0,0 +1,12 @@
+/**
+ * Skill instructions printed to stdout when `codiedev create-ticket` is
+ * invoked without `--submit`. Claude (running the CLI via Bash) reads
+ * this content and follows the protocol: ask the dev about repos,
+ * investigate locally, emit a plan, call back into the CLI to submit.
+ *
+ * The scoping rules (#### TICKET QUALITY BAR onwards) are lifted verbatim
+ * from `modal/runner.py:_format_ticket_from_analysis` so the CLI path
+ * produces structurally-identical plans to the Modal path.
+ */
+export declare const CREATE_TICKET_SKILL_INSTRUCTIONS = "\nYou are conducting a forward ticket-writing session for the user via codiedev.\nFollow this protocol exactly. Do not improvise the ticket structure.\n\n## Step 1 \u2014 Ask about repos\nAsk the user once:\n  \"Is this work in a single repo or across multiple? If multiple, please tell me where each one is located on disk.\"\nWait for their reply. They will give you absolute paths like /Users/x/code/foo.\n\n## Step 2 \u2014 Investigate (read-only)\nFor each repo path the user gave you:\n  - cd into the repo\n  - Read the user's intent (their prompt, given below)\n  - Find the primary files related to that intent. Use grep for class names,\n    function names, enum values, constants, file names extracted from the prompt.\n  - For each file found, report what it contains: function signatures, enum\n    values, switch/case statements, existing patterns.\n  - Grep for who imports each file (consumers, dependencies).\n  - Check for existing tests related to those files.\n  - Note migration patterns, naming conventions, barrel exports.\nDO NOT modify any files. This is read-only.\n\n## Step 2.5 \u2014 Ask if the prompt doesn't match the codebase\n\nBefore writing the plan, check: do the user's literal words appear in the codebase as named?\n\n- If they said \"delete X\" but only \"archive X\" / \"setArchived\" exists, ask one question quoting\n  both sides: \"You said `delete`, but I see only `setArchived` \u2014 confirm the modal is for the\n  archive button?\"\n- If they said \"the analytics dashboard\" but the named component (e.g. AnalyticsTab) is already\n  reactive and the only useEffect-fetch lives elsewhere, ask: \"AnalyticsTab is already on\n  useQuery; the only useEffect-fetch I found is in admin/page.tsx LangfuseCostsSection \u2014 is\n  that the target?\"\n- If they named a feature/flag/component that doesn't exist at all, ask which of the closest\n  matches they meant, listing each with a one-line reason it's plausible.\n\nDo NOT silently route to the closest match in these cases. Silently routing buries the mismatch\nin scope OUT and produces a ticket the user didn't ask for. One targeted question that quotes\nthe user's word AND the codebase's actual word is the right move.\n\nIf you also have a separate genuine ambiguity (two plausible places the change could go that\nboth match the user's words), bundle it into the same question \u2014 but don't fabricate ambiguity\nto hit a quota. If the words map to the codebase clearly, do not ask further questions \u2014\nproceed to Step 3.\n\n## Step 3 \u2014 Format the plan\n\nThe user's request defines WHAT to build. The investigation defines HOW to build it.\nYour job is to translate the user's exact request into actionable tickets using\nthe investigation as supporting evidence. The user chose their words carefully \u2014\nuse them.\n\nOutput a plan as one or more tickets. Each ticket becomes a single PR handled\nby a coding agent. The agent works alone and makes one PR per ticket.\n\nEACH TICKET = ONE MERGEABLE PR\nA ticket is ready when its PR can merge to main and the app compiles, renders,\nand passes tests with zero other tickets merged. This is the only rule that matters.\n\nHow to group work:\n- The investigation identified every file that needs to change. Your job is to\n  package that into tickets, not to re-scope. Every file from the investigation\n  appears in at least one ticket.\n- Each ticket becomes one PR. A PR should be focused enough that a reviewer\n  understands it in one sitting and CI validates it fully.\n- Include every file needed for the change to be complete \u2014 don't leave wiring,\n  migrations, or consumer updates for a follow-up.\n- If the work naturally spans independent modules, output multiple tickets ordered\n  by dependency. Use the `dependsOn` field (array of zero-indexed ticket numbers\n  this ticket depends on).\n- \"After this PR merges, the app:\" must describe a working state. If you can't,\n  the ticket is incomplete \u2014 add what's missing.\n- Default to ONE ticket. Only split when ticket 2 could merge to main without\n  ticket 1 and the app still compiles.\n\nQUALITY BAR \u2014 every ticket must:\n- Quantify the problem: count the calls, files, violations. \"6 manager.getRepository()\n  calls\", not \"several calls\".\n- Name the codebase's own patterns: use the exact class names, method names, and\n  conventions found in the investigation. \"injectable wrapper pattern with\n  @InjectRepository\", not \"create a new class\".\n- Include specific file paths with line numbers from the investigation findings.\n- Say what stays the same: \"Keep standard CRUD in AceService\", \"do not export it\",\n  \"no logic changes\".\n- Scope IN/OUT must reference concrete things in the codebase, not abstract categories.\n\nFor each ticket, fill these fields:\n  - title: <80 chars, imperative mood\n  - description: GIVEN/WHEN/THEN format, quantify the problem\n  - technicalDetails: specific files with line numbers, the approach,\n    patterns from the codebase to follow, what to keep unchanged\n  - scope: IN: ... / OUT: ...\n  - targetRepoId: leave empty for now \u2014 the CLI will fill this from the repo paths\n  - targetRepoFullName: \"owner/name\" matching the git remote of the repo this\n    ticket touches (e.g. \"ericlam1114/vm-demo\")\n  - dependsOn: [zero-indexed ticket numbers] or [] if independent\n\n## Step 4 \u2014 Submit\nWhen the plan is ready, write it to a temp file as JSON matching this schema:\n\n{\n  \"plan\": {\n    \"summary\": \"<one sentence: what this plan delivers and how many tickets>\",\n    \"tickets\": [\n      {\n        \"title\": \"...\",\n        \"description\": \"...\",\n        \"technicalDetails\": \"...\",\n        \"scope\": \"...\",\n        \"targetRepoFullName\": \"owner/name\",\n        \"dependsOn\": []\n      }\n    ]\n  },\n  \"prompt\": \"<the user's original intent verbatim>\",\n  \"repoFullNames\": [\"owner/name\", ...]\n}\n\nThen run:\n  codiedev create-ticket --submit <path-to-temp-file.json>\n\nThe CLI will translate `targetRepoFullName` and `repoFullNames` into repo IDs,\nPOST the plan, and print the portal URL. Tell the user the URL when it returns.\n\n## The user's intent\n{{USER_PROMPT}}\n";
+export declare function renderSkillInstructions(prompt: string | undefined): string;

package/dist/createTicketSkill.js

@@ -0,0 +1,146 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.CREATE_TICKET_SKILL_INSTRUCTIONS = void 0;
+exports.renderSkillInstructions = renderSkillInstructions;
+/**
+ * Skill instructions printed to stdout when `codiedev create-ticket` is
+ * invoked without `--submit`. Claude (running the CLI via Bash) reads
+ * this content and follows the protocol: ask the dev about repos,
+ * investigate locally, emit a plan, call back into the CLI to submit.
+ *
+ * The scoping rules (#### TICKET QUALITY BAR onwards) are lifted verbatim
+ * from `modal/runner.py:_format_ticket_from_analysis` so the CLI path
+ * produces structurally-identical plans to the Modal path.
+ */
+exports.CREATE_TICKET_SKILL_INSTRUCTIONS = `
+You are conducting a forward ticket-writing session for the user via codiedev.
+Follow this protocol exactly. Do not improvise the ticket structure.
+
+## Step 1 — Ask about repos
+Ask the user once:
+  "Is this work in a single repo or across multiple? If multiple, please tell me where each one is located on disk."
+Wait for their reply. They will give you absolute paths like /Users/x/code/foo.
+
+## Step 2 — Investigate (read-only)
+For each repo path the user gave you:
+  - cd into the repo
+  - Read the user's intent (their prompt, given below)
+  - Find the primary files related to that intent. Use grep for class names,
+    function names, enum values, constants, file names extracted from the prompt.
+  - For each file found, report what it contains: function signatures, enum
+    values, switch/case statements, existing patterns.
+  - Grep for who imports each file (consumers, dependencies).
+  - Check for existing tests related to those files.
+  - Note migration patterns, naming conventions, barrel exports.
+DO NOT modify any files. This is read-only.
+
+## Step 2.5 — Ask if the prompt doesn't match the codebase
+
+Before writing the plan, check: do the user's literal words appear in the codebase as named?
+
+- If they said "delete X" but only "archive X" / "setArchived" exists, ask one question quoting
+  both sides: "You said \`delete\`, but I see only \`setArchived\` — confirm the modal is for the
+  archive button?"
+- If they said "the analytics dashboard" but the named component (e.g. AnalyticsTab) is already
+  reactive and the only useEffect-fetch lives elsewhere, ask: "AnalyticsTab is already on
+  useQuery; the only useEffect-fetch I found is in admin/page.tsx LangfuseCostsSection — is
+  that the target?"
+- If they named a feature/flag/component that doesn't exist at all, ask which of the closest
+  matches they meant, listing each with a one-line reason it's plausible.
+
+Do NOT silently route to the closest match in these cases. Silently routing buries the mismatch
+in scope OUT and produces a ticket the user didn't ask for. One targeted question that quotes
+the user's word AND the codebase's actual word is the right move.
+
+If you also have a separate genuine ambiguity (two plausible places the change could go that
+both match the user's words), bundle it into the same question — but don't fabricate ambiguity
+to hit a quota. If the words map to the codebase clearly, do not ask further questions —
+proceed to Step 3.
+
+## Step 3 — Format the plan
+
+The user's request defines WHAT to build. The investigation defines HOW to build it.
+Your job is to translate the user's exact request into actionable tickets using
+the investigation as supporting evidence. The user chose their words carefully —
+use them.
+
+Output a plan as one or more tickets. Each ticket becomes a single PR handled
+by a coding agent. The agent works alone and makes one PR per ticket.
+
+EACH TICKET = ONE MERGEABLE PR
+A ticket is ready when its PR can merge to main and the app compiles, renders,
+and passes tests with zero other tickets merged. This is the only rule that matters.
+
+How to group work:
+- The investigation identified every file that needs to change. Your job is to
+  package that into tickets, not to re-scope. Every file from the investigation
+  appears in at least one ticket.
+- Each ticket becomes one PR. A PR should be focused enough that a reviewer
+  understands it in one sitting and CI validates it fully.
+- Include every file needed for the change to be complete — don't leave wiring,
+  migrations, or consumer updates for a follow-up.
+- If the work naturally spans independent modules, output multiple tickets ordered
+  by dependency. Use the \`dependsOn\` field (array of zero-indexed ticket numbers
+  this ticket depends on).
+- "After this PR merges, the app:" must describe a working state. If you can't,
+  the ticket is incomplete — add what's missing.
+- Default to ONE ticket. Only split when ticket 2 could merge to main without
+  ticket 1 and the app still compiles.
+
+QUALITY BAR — every ticket must:
+- Quantify the problem: count the calls, files, violations. "6 manager.getRepository()
+  calls", not "several calls".
+- Name the codebase's own patterns: use the exact class names, method names, and
+  conventions found in the investigation. "injectable wrapper pattern with
+  @InjectRepository", not "create a new class".
+- Include specific file paths with line numbers from the investigation findings.
+- Say what stays the same: "Keep standard CRUD in AceService", "do not export it",
+  "no logic changes".
+- Scope IN/OUT must reference concrete things in the codebase, not abstract categories.
+
+For each ticket, fill these fields:
+  - title: <80 chars, imperative mood
+  - description: GIVEN/WHEN/THEN format, quantify the problem
+  - technicalDetails: specific files with line numbers, the approach,
+    patterns from the codebase to follow, what to keep unchanged
+  - scope: IN: ... / OUT: ...
+  - targetRepoId: leave empty for now — the CLI will fill this from the repo paths
+  - targetRepoFullName: "owner/name" matching the git remote of the repo this
+    ticket touches (e.g. "ericlam1114/vm-demo")
+  - dependsOn: [zero-indexed ticket numbers] or [] if independent
+
+## Step 4 — Submit
+When the plan is ready, write it to a temp file as JSON matching this schema:
+
+{
+  "plan": {
+    "summary": "<one sentence: what this plan delivers and how many tickets>",
+    "tickets": [
+      {
+        "title": "...",
+        "description": "...",
+        "technicalDetails": "...",
+        "scope": "...",
+        "targetRepoFullName": "owner/name",
+        "dependsOn": []
+      }
+    ]
+  },
+  "prompt": "<the user's original intent verbatim>",
+  "repoFullNames": ["owner/name", ...]
+}
+
+Then run:
+  codiedev create-ticket --submit <path-to-temp-file.json>
+
+The CLI will translate \`targetRepoFullName\` and \`repoFullNames\` into repo IDs,
+POST the plan, and print the portal URL. Tell the user the URL when it returns.
+
+## The user's intent
+{{USER_PROMPT}}
+`;
+function renderSkillInstructions(prompt) {
+    return exports.CREATE_TICKET_SKILL_INSTRUCTIONS.replace("{{USER_PROMPT}}", prompt && prompt.length > 0
+        ? prompt
+        : "(not yet provided — ask the user a single combined question that covers both the intent AND repo locations: \"What are you working on, and is this in a single repo or multiple? If multiple, give me the paths.\" Skip Step 1 since you've folded it into this question. Then proceed to Step 2.)");
+}

package/dist/detection.d.ts

@@ -10,3 +10,21 @@ export interface ClaudeCodeProbe {
  * obviously committed to the tool.
  */
 export declare function detectClaudeCode(probe: ClaudeCodeProbe): boolean;
+/**
+ * True iff `cmd` looks like a hook command codiedev itself wrote. Used
+ * both by the install filter (so `connect` replaces the existing entry
+ * instead of stacking another one) and by `codiedev doctor` (so it can
+ * grade whether the hook is wired up).
+ *
+ * Must match every form codiedev can write:
+ *   - Legacy `npx codiedev-hook <subcommand>`
+ *   - Absolute path from npm-registry install:
+ *     `<node> /.../node_modules/codiedev/dist/hook.js <subcommand>`
+ *   - Absolute path from `npm link` dev install (the monorepo folder
+ *     is named `codiedev-cli`, not `codiedev`):
+ *     `<node> /.../codiedev-cli/dist/hook.js <subcommand>`
+ *
+ * The `codiedev[^/\\]*` allows the trailing `-cli` (or any future suffix)
+ * without matching unrelated paths like `notcodiedev/dist/hook.js`.
+ */
+export declare function isCodiedevHookCommand(cmd: string | undefined): boolean;

package/dist/detection.js

@@ -4,6 +4,7 @@
 // mocking fs or process.
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.detectClaudeCode = detectClaudeCode;
+exports.isCodiedevHookCommand = isCodiedevHookCommand;
 /**
  * Claude Code is "installed" if either ~/.claude exists (the user has
  * launched the app at least once) OR the `claude` binary is on PATH (the
@@ -14,3 +15,30 @@ exports.detectClaudeCode = detectClaudeCode;
 function detectClaudeCode(probe) {
     return probe.dirExists || probe.binOnPath;
 }
+/**
+ * True iff `cmd` looks like a hook command codiedev itself wrote. Used
+ * both by the install filter (so `connect` replaces the existing entry
+ * instead of stacking another one) and by `codiedev doctor` (so it can
+ * grade whether the hook is wired up).
+ *
+ * Must match every form codiedev can write:
+ *   - Legacy `npx codiedev-hook <subcommand>`
+ *   - Absolute path from npm-registry install:
+ *     `<node> /.../node_modules/codiedev/dist/hook.js <subcommand>`
+ *   - Absolute path from `npm link` dev install (the monorepo folder
+ *     is named `codiedev-cli`, not `codiedev`):
+ *     `<node> /.../codiedev-cli/dist/hook.js <subcommand>`
+ *
+ * The `codiedev[^/\\]*` allows the trailing `-cli` (or any future suffix)
+ * without matching unrelated paths like `notcodiedev/dist/hook.js`.
+ */
+function isCodiedevHookCommand(cmd) {
+    if (!cmd)
+        return false;
+    if (cmd.includes("codiedev-hook"))
+        return true;
+    // Anchor at a path separator (or string start) so we don't match
+    // unrelated paths like `notcodiedev/dist/hook.js` that happen to contain
+    // the substring `codiedev`.
+    return /(?:^|[\\/])codiedev[^/\\]*[\\/]dist[\\/]hook/.test(cmd);
+}