codiedev 0.7.10 → 0.7.11

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);
+}

package/dist/mcp.js

@@ -173,8 +173,8 @@ const TOOLS = [
         name: "codiedev_ping",
         description: "Send a message to a teammate on CodieDev, optionally attached to a " +
             "specific artifact. Use when the user asks to ping, ask, share with, " +
-            "or get feedback from a teammate by name (e.g. 'ping Maya about this " +
-            "spec'). Recipients are resolved by first name, full name, or email " +
+            "or get feedback from a teammate by name (e.g. 'ping a teammate about " +
+            "this spec'). Recipients are resolved by first name, full name, or email " +
             "within the current org. They're notified by email and can reply " +
             "from their own agent.",
         inputSchema: {
@@ -325,8 +325,8 @@ const TOOLS = [
         name: "codiedev_share_with",
         description: "Grant a teammate persistent read (or edit) access to an artifact " +
             "without sending a notification. Use when the user says 'share this " +
-            "with Greg' or 'give Jason access', and doesn't want to surface it " +
-            "as a message. If they want the teammate actively notified, use " +
+            "with a teammate' or 'give someone access', and doesn't want to surface " +
+            "it as a message. If they want the teammate actively notified, use " +
             "codiedev_send_to instead.",
         inputSchema: {
             type: "object",
@@ -349,8 +349,8 @@ const TOOLS = [
     {
         name: "codiedev_send_to",
         description: "Grant access to an artifact AND send a short message to a " +
-            "teammate. Use when the user asks to 'send this to Greg', 'ask " +
-            "Greg to look at this', or 'share this with Jason and tell him X'. " +
+            "teammate. Use when the user asks to 'send this to a teammate', 'ask " +
+            "someone to look at this', or 'share this with a teammate and tell them X'. " +
             "This is the active handoff version of codiedev_share_with — the " +
             "recipient gets a ping in their inbox.",
         inputSchema: {
@@ -439,7 +439,7 @@ const TOOLS = [
             "files surfaced as slash commands). Each row reports its `kind` " +
             "(doc | skill) and `tags`. Use when the user asks 'show me my " +
             "artifacts', 'what skills do we have?', 'what did I push?', 'what " +
-            "has Greg shared with me?', or 'browse the library'. Filter by " +
+            "has a teammate shared with me?', or 'browse the library'. Filter by " +
             "`kind` to narrow to docs-only or skills-only.",
         inputSchema: {
             type: "object",

package/dist/utils.d.ts

@@ -61,6 +61,28 @@ export declare function installCursorMcp(): void;
  * 100% diff-driven (no transcript dependency).
  */
 export declare function installVSCodeMcp(): void;
+/**
+ * Removes `mcpServers.codiedev` from `~/.claude.json` if present. Leaves
+ * other MCP servers and unrelated top-level settings untouched.
+ */
+export declare function cleanupClaudeCodeMcp(): void;
+/**
+ * Removes `mcpServers.codiedev` from `~/.cursor/mcp.json` if present.
+ */
+export declare function cleanupCursorMcp(): void;
+/**
+ * Removes `servers.codiedev` from VS Code's user-scope mcp.json. VS Code
+ * uses a different schema (`servers` not `mcpServers`), so this is a
+ * separate helper.
+ */
+export declare function cleanupVSCodeMcp(): void;
+/**
+ * Removes the `# codiedev-mcp` block from `~/.codex/config.toml`. The
+ * install side appends a well-marked block; we strip it the same way —
+ * the marker line through the end of its TOML section. Whitespace-only
+ * gaps between sections are preserved.
+ */
+export declare function cleanupCodexMcp(): void;
 /**
  * Best-effort append of the CodieDev MCP server block to ~/.codex/config.toml.
  *

package/dist/utils.js

@@ -50,6 +50,10 @@ exports.installCursorInstructions = installCursorInstructions;
 exports.installClaudeCodeMcp = installClaudeCodeMcp;
 exports.installCursorMcp = installCursorMcp;
 exports.installVSCodeMcp = installVSCodeMcp;
+exports.cleanupClaudeCodeMcp = cleanupClaudeCodeMcp;
+exports.cleanupCursorMcp = cleanupCursorMcp;
+exports.cleanupVSCodeMcp = cleanupVSCodeMcp;
+exports.cleanupCodexMcp = cleanupCodexMcp;
 exports.installCodexMcp = installCodexMcp;
 exports.installCodexHook = installCodexHook;
 exports.installCursorHook = installCursorHook;
@@ -186,11 +190,8 @@ function resolveHookCommand(subcommand) {
     }
     return `npx codiedev-hook ${subcommand}`;
 }
-function isCodiedevHookCommand(cmd) {
-    if (!cmd)
-        return false;
-    return cmd.includes("codiedev-hook") || /codiedev[\\/]dist[\\/]hook/.test(cmd);
-}
+// `isCodiedevHookCommand` is defined in `./detection` so it's testable
+// without mocking fs/path. Re-imported below; do not re-define here.
 function claudeBinOnPath() {
     try {
         (0, child_process_1.execSync)("command -v claude", { stdio: ["pipe", "pipe", "pipe"] });
@@ -254,9 +255,9 @@ function installHook() {
     const filtered = existing.filter((hook) => {
         const inner = hook.hooks;
         if (Array.isArray(inner)) {
-            return !inner.some((h) => isCodiedevHookCommand(h.command));
+            return !inner.some((h) => (0, detection_1.isCodiedevHookCommand)(h.command));
         }
-        return !isCodiedevHookCommand(hook.matcher);
+        return !(0, detection_1.isCodiedevHookCommand)(hook.matcher);
     });
     filtered.push({
         matcher: ".*",
@@ -294,20 +295,20 @@ thought, use the \`codiedev\` CLI via Bash:**
 | Intent | Command |
 |---|---|
 | "push this spec" / "save this as a skill" | \`codiedev push <file.md>\` |
-| "pull X" / "grab the latest spec-X" / "what did Maya push?" | \`codiedev pull <key>\` |
+| "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 Nic about this" / "ask Maya for her take" | \`codiedev ping <name> "<msg>" [--with <key>]\` |
-| "any messages?" / "check my inbox" / "what did Nic say?" | \`codiedev inbox\` |
-| "read Nic's reply" / "mark that ping read" | \`codiedev read <ping-id>\` |
+| "ping a teammate about this" / "ask someone for their take" | \`codiedev ping <name> "<msg>" [--with <key>]\` |
+| "any messages?" / "check my inbox" / "what did a teammate say?" | \`codiedev inbox\` |
+| "read that reply" / "mark that ping read" | \`codiedev read <ping-id>\` |
 | "note that X is a follow-up" / "remember X" | \`codiedev note "<text>"\` |
 | "promote the extracted spec" | \`codiedev promote <artifact-id>\` |
-| "post this to the team" / "publish to the feed" / "share with the team" | MCP tool \`codiedev_post_to_feed\` |
-| "share with Greg" / "give Jason access" (no notification) | MCP tool \`codiedev_share_with\` |
-| "send this to Greg" / "ask Greg to look at this" | MCP tool \`codiedev_send_to\` |
-| "find something about X" / "has anyone solved Y?" | MCP tool \`codiedev_search\` |
-| "why did we…?" / "what does the team know about X?" | MCP tool \`codiedev_ask\` (synthesized answer + citations) |
-| "show my library" / "what artifacts exist?" | MCP tool \`codiedev_get_library\` |
-| "react 🛠 to that post" / "mark as used" | MCP tool \`codiedev_react\` |
+| "post this to the team" / "publish to the feed" / "share with the team" | \`codiedev post --title "<t>" --body "<b>" [--intent <intent>] [--filename <key>] [--mention <name>]\` |
+| "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>"]\` |
+| "find something about X" / "has anyone solved Y?" | \`codiedev search "<query>" [--limit N]\` |
+| "why did we…?" / "what does the team know about X?" | \`codiedev ask "<question>"\` (synthesized answer + citations) |
+| "show my library" / "what artifacts exist?" | \`codiedev library [--scope mine\\|shared\\|all] [--kind doc\\|skill]\` |
+| "react 🛠 to that post" / "mark as used" | \`codiedev react <postId> <emoji>\` |
 
 **Just push the file — we'll figure out where it goes.** Every artifact
 is classified into one of two kinds at upload time:
@@ -332,16 +333,17 @@ read it back to the user so they can confirm.
 - If content was drafted inline in the conversation, write it to a file
   first (e.g., \`/tmp/spec-xxx.md\`) then push.
 
-**Teammate names:** first name usually works (\`codiedev ping nic ...\`).
+**Teammate names:** first name usually works (\`codiedev ping <name> ...\`).
 If ambiguous, the CLI returns candidates — retry with the full email.
 
-**Feed posts (broad team reach):** use \`codiedev_post_to_feed\` when the
-user wants visibility beyond one teammate — e.g., announcing a new skill,
-asking the team who knows about X, proposing a change. Always pass an
-\`intent\` that matches the request: \`share\` (here's a skill),
+**Feed posts (broad team reach):** use \`codiedev post\` when the user
+wants visibility beyond one teammate — e.g., announcing a new skill,
+asking the team who knows about X, proposing a change. Always pass
+\`--intent\` to match the request: \`share\` (here's a skill),
 \`request_review\`, \`request_expertise\` (stuck, who knows this),
-\`link_share\` (fyi), or \`rfc\` (proposing a change). Attach a \`filename\`
-to link a specific artifact and \`mentions\` to tag teammates.
+\`link_share\` (fyi), or \`rfc\` (proposing a change). Pass \`--filename\`
+to link a specific artifact and \`--mention <name>\` (repeatable) to
+tag teammates.
 
 **Default feed-post shape.** When the user explicitly says "push/share/post
 to the feed", default to this shape unless they ask for something else:
@@ -359,12 +361,12 @@ to the feed", default to this shape unless they ask for something else:
 This is the default. If the user wants a one-liner or a different
 structure, follow their lead.
 
-**Search before pushing.** For any "save this as …" request, call
-\`codiedev_search\` first with a relevant query. If prior art exists, pull
-it and iterate rather than duplicating.
+**Search before pushing.** For any "save this as …" request, run
+\`codiedev search "<query>"\` first. If prior art exists, pull it and
+iterate rather than duplicating.
 
-**Sharing vs sending:** \`codiedev_share_with\` is silent (access only, no
-notification). \`codiedev_send_to\` both grants access AND pings the
+**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.
 
 **Errors:**
@@ -538,6 +540,94 @@ function installVSCodeMcp() {
     config.servers = servers;
     fs.writeFileSync(VSCODE_USER_MCP_PATH, JSON.stringify(config, null, 2), "utf8");
 }
+// ─────────────────────────────────────────────────────────────────────────────
+// Migration cleanup — strips MCP server entries written by pre-CLI-only
+// versions of `codiedev connect`. Those entries pointed at `npx codiedev-mcp`,
+// a binary that was removed from package.json in 0.3.4. Without these
+// cleanups, customers who upgrade to 0.7.11+ keep seeing "MCP server failed
+// to start" errors in their agent UIs even though the CLI works fine.
+// All cleanup helpers are idempotent and safe to run when no entry exists.
+// ─────────────────────────────────────────────────────────────────────────────
+function removeJsonKey(filePath, parentKey) {
+    if (!fs.existsSync(filePath))
+        return;
+    let parsed;
+    try {
+        parsed = JSON.parse(fs.readFileSync(filePath, "utf8"));
+    }
+    catch {
+        return; // Don't damage a file we can't parse.
+    }
+    const parent = parsed[parentKey];
+    if (!parent || typeof parent !== "object")
+        return;
+    if (!("codiedev" in parent))
+        return;
+    delete parent.codiedev;
+    fs.writeFileSync(filePath, JSON.stringify(parsed, null, 2), "utf8");
+}
+/**
+ * Removes `mcpServers.codiedev` from `~/.claude.json` if present. Leaves
+ * other MCP servers and unrelated top-level settings untouched.
+ */
+function cleanupClaudeCodeMcp() {
+    removeJsonKey(CLAUDE_USER_CONFIG_PATH, "mcpServers");
+}
+/**
+ * Removes `mcpServers.codiedev` from `~/.cursor/mcp.json` if present.
+ */
+function cleanupCursorMcp() {
+    removeJsonKey(CURSOR_MCP_PATH, "mcpServers");
+}
+/**
+ * Removes `servers.codiedev` from VS Code's user-scope mcp.json. VS Code
+ * uses a different schema (`servers` not `mcpServers`), so this is a
+ * separate helper.
+ */
+function cleanupVSCodeMcp() {
+    removeJsonKey(VSCODE_USER_MCP_PATH, "servers");
+}
+/**
+ * Removes the `# codiedev-mcp` block from `~/.codex/config.toml`. The
+ * install side appends a well-marked block; we strip it the same way —
+ * the marker line through the end of its TOML section. Whitespace-only
+ * gaps between sections are preserved.
+ */
+function cleanupCodexMcp() {
+    if (!fs.existsSync(CODEX_CONFIG_PATH))
+        return;
+    const existing = fs.readFileSync(CODEX_CONFIG_PATH, "utf8");
+    const marker = "# codiedev-mcp";
+    if (!existing.includes(marker))
+        return;
+    const lines = existing.split("\n");
+    const out = [];
+    let skipping = false;
+    for (const line of lines) {
+        if (line.trim() === marker) {
+            skipping = true;
+            continue;
+        }
+        if (skipping) {
+            // Stay in skip mode through the [mcp_servers.codiedev] block until
+            // we hit a blank line or a different TOML section header.
+            const trimmed = line.trim();
+            if (trimmed === "") {
+                skipping = false;
+                continue; // also drop the blank that immediately follows the block
+            }
+            if (trimmed.startsWith("[") && !trimmed.startsWith("[mcp_servers.codiedev")) {
+                skipping = false;
+                out.push(line);
+                continue;
+            }
+            // Skip lines belonging to the codiedev block.
+            continue;
+        }
+        out.push(line);
+    }
+    fs.writeFileSync(CODEX_CONFIG_PATH, out.join("\n"), "utf8");
+}
 /**
  * Best-effort append of the CodieDev MCP server block to ~/.codex/config.toml.
  *
@@ -592,7 +682,7 @@ function installCodexHook() {
         const inner = hook.hooks;
         if (!Array.isArray(inner))
             return true;
-        return !inner.some((h) => isCodiedevHookCommand(h.command));
+        return !inner.some((h) => (0, detection_1.isCodiedevHookCommand)(h.command));
     });
     filtered.push({
         hooks: [
@@ -638,7 +728,7 @@ function installCursorHook() {
         hooks.sessionEnd = [];
     }
     const existing = hooks.sessionEnd;
-    const filtered = existing.filter((h) => !isCodiedevHookCommand(h.command));
+    const filtered = existing.filter((h) => !(0, detection_1.isCodiedevHookCommand)(h.command));
     filtered.push({
         command: resolveHookCommand("capture-cursor"),
         type: "command",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codiedev",
-  "version": "0.7.10",
+  "version": "0.7.11",
   "description": "Connect Claude Code, Codex, Cursor, or VS Code Copilot to CodieDev for org-wide session capture and artifact collaboration",
   "bin": {
     "codiedev": "dist/cli.js",