codiedev 0.9.88 → 0.9.89

package/dist/cli.d.ts

@@ -6,7 +6,7 @@
  *   codiedev connect                   — link agent CLIs to your org
  *   codiedev push <file>               — author/update a spec/review/decision/etc.
  *   codiedev pull <key>                — fetch an artifact by filename key
- *   codiedev ping <user> "<msg>"       — send a message (optionally --with <key>)
+ *   codiedev ping <user> ["<msg>"]     — message and/or share (--with <key>)
  *   codiedev inbox                     — list pings (use --unread to filter)
  *   codiedev read <ping-id>            — mark read + show full message
  *   codiedev reply <ping-id> "<msg>"   — answer a ping in its thread

package/dist/cli.js

@@ -7,7 +7,7 @@
  *   codiedev connect                   — link agent CLIs to your org
  *   codiedev push <file>               — author/update a spec/review/decision/etc.
  *   codiedev pull <key>                — fetch an artifact by filename key
- *   codiedev ping <user> "<msg>"       — send a message (optionally --with <key>)
+ *   codiedev ping <user> ["<msg>"]     — message and/or share (--with <key>)
  *   codiedev inbox                     — list pings (use --unread to filter)
  *   codiedev read <ping-id>            — mark read + show full message
  *   codiedev reply <ping-id> "<msg>"   — answer a ping in its thread
@@ -103,11 +103,10 @@ Artifacts:
                                          Asks for confirmation; -y to skip.
 
 Messaging:
-  codiedev ping <user> "<msg>" [--with <key>] [--file <path>]
-                                         Send a message to a teammate
-  codiedev send <key> <user> ["<msg>"]   Share an artifact + ping in one step
-  codiedev share <key> <user> [--role read|edit]
-                                         Silently grant access (no notification)
+  codiedev ping <user> ["<msg>"] [--with <key>] [--edit] [--file <path>]
+                                         Message a teammate (emails them). --with
+                                         gives them access to an artifact; with
+                                         no message it's a silent share
   codiedev inbox [--unread] [--limit N]  Show messages
   codiedev read <ping-id>                Mark read + show full message
   codiedev reply <ping-id> "<msg>" [--file <path>]
@@ -280,10 +279,14 @@ codiedev pull — fetch an artifact
     codiedev pull spec-cart-clear.md | less
 `.trim(),
     ping: `
-codiedev ping — send a teammate a message, optionally attached to an artifact
+codiedev ping — send a teammate a message, an artifact, or both
 
   Usage:
-    codiedev ping <user> "<message>" [--with <artifact-key>] [--file <path>]
+    codiedev ping <user> ["<message>"] [--with <artifact-key>] [--edit] [--file <path>]
+
+  --with gives them read access to the artifact (--edit: edit access; only
+  the owner can give edit access or share a private skill). With no message,
+  it's a silent share: access only, no inbox entry, no email.
 
   <user> resolves to a teammate in your org by first name, full name,
   or email. Ambiguous matches return a list — retry with the full email.

package/dist/commands/ping.d.ts

@@ -1 +1,10 @@
-export declare function runPing(args: string[]): Promise<void>;
+import type { CodiedevConfig } from "../utils";
+export declare const PING_USAGE = "Usage: codiedev ping <user> [\"<message>\"] [--with <artifact-key>] [--edit] [--file <path>]";
+export declare function parsePingArgs(allArgs: string[]): {
+    to: string;
+    body: string;
+    subjectKey?: string;
+    edit: boolean;
+    files: string[];
+};
+export declare function runPing(args: string[], configOverride?: CodiedevConfig): Promise<void>;

package/dist/commands/ping.js

@@ -1,16 +1,30 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.PING_USAGE = void 0;
+exports.parsePingArgs = parsePingArgs;
 exports.runPing = runPing;
+// `codiedev ping <user> ["<message>"] [--with <artifact>] [--edit] [--file <path>]`
+// The one way to send a teammate something:
+//   message only            → inbox + email
+//   message + --with        → inbox + email, and they get access to the artifact
+//   --with, no message      → access only, no notification (what `share` did)
+// `send` and `share` are kept as aliases that route here.
 const shared_1 = require("./shared");
 const pingFiles_1 = require("./pingFiles");
-function parseArgs(allArgs) {
+const share_1 = require("./share");
+exports.PING_USAGE = 'Usage: codiedev ping <user> ["<message>"] [--with <artifact-key>] [--edit] [--file <path>]';
+function parsePingArgs(allArgs) {
     const { files, rest: args } = (0, pingFiles_1.takeFileArgs)(allArgs);
     let to;
     const positional = [];
     let subjectKey;
+    let edit = false;
     for (let i = 0; i < args.length; i++) {
         const a = args[i];
-        if ((a === "--with" || a === "-w") && i + 1 < args.length) {
+        if (a === "--edit") {
+            edit = true;
+        }
+        else if ((a === "--with" || a === "-w") && i + 1 < args.length) {
             subjectKey = args[++i];
         }
         else if (a.startsWith("--with=")) {
@@ -20,26 +34,41 @@ function parseArgs(allArgs) {
             positional.push(a);
         }
     }
-    // A file can stand in for the message.
-    if (positional.length < 2 && !(positional.length === 1 && files.length > 0)) {
-        console.error("Usage: codiedev ping <user> \"<message>\" [--with <artifact-key>] [--file <path>]");
+    // A file can stand in for the message; --with alone shares without one.
+    if (positional.length < 2 && !(positional.length === 1 && (files.length > 0 || subjectKey))) {
+        console.error(exports.PING_USAGE);
+        process.exit(1);
+    }
+    if (edit && !subjectKey) {
+        console.error("--edit needs an artifact: --with <artifact-key>");
         process.exit(1);
     }
     to = positional[0];
     // Join remaining positionals in case the shell split the message on spaces
     // despite quoting (happens with some escape sequences).
     const body = (0, shared_1.stripQuotes)(positional.slice(1).join(" "));
-    return { to, body: body || (files.length ? "Sent a file." : ""), subjectKey, files };
+    return { to, body: body || (files.length ? "Sent a file." : ""), subjectKey, edit, files };
 }
-async function runPing(args) {
-    const { to, body, subjectKey, files } = parseArgs(args);
-    const config = (0, shared_1.requireConfig)();
+async function runPing(args, configOverride) {
+    const { to, body, subjectKey, edit, files } = parsePingArgs(args);
+    // Nothing to say, just access: a silent share.
+    if (!body && subjectKey) {
+        await (0, share_1.runShare)([subjectKey, to, "--role", edit ? "edit" : "read"], configOverride);
+        return;
+    }
+    const config = configOverride ?? (0, shared_1.requireConfig)();
     const start = Date.now();
     try {
         const attachmentIds = await (0, pingFiles_1.uploadOrExit)(config, files);
         const res = await (0, shared_1.apiRequest)("POST", "/api/cli/ping", {
             config,
-            body: { to, body, subjectKey, ...(attachmentIds.length ? { attachmentIds } : {}) },
+            body: {
+                to,
+                body,
+                subjectKey,
+                ...(subjectKey ? { grant: edit ? "edit" : "read" } : {}),
+                ...(attachmentIds.length ? { attachmentIds } : {}),
+            },
         });
         (0, shared_1.recordAgentEvent)(config, {
             tool: "codiedev_ping",

package/dist/commands/send.d.ts

@@ -1,2 +1,3 @@
 import type { CodiedevConfig } from "../utils";
+export declare function sendToPingArgs(args: string[]): string[] | null;
 export declare function runSend(args: string[], configOverride?: CodiedevConfig): Promise<void>;

package/dist/commands/send.js

@@ -1,67 +1,27 @@
 "use strict";
-// `codiedev send <filename> <recipient> [message]` — share an artifact AND
-// send a short message that lands in the teammate's inbox. The active-
-// handoff version of `codiedev share`. Use this when the user is actively
-// looping someone in.
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.sendToPingArgs = sendToPingArgs;
 exports.runSend = runSend;
+// `codiedev send <artifact> <recipient> ["<message>"]` — kept as an alias for
+// `codiedev ping <recipient> ["<message>"] --with <artifact>`. With a message
+// the teammate gets it in their inbox and by email plus read access; without
+// one it's a silent share.
+const ping_1 = require("./ping");
 const shared_1 = require("./shared");
-function parseArgs(args) {
+function sendToPingArgs(args) {
     const positionals = args.filter((a) => !a.startsWith("--"));
     const [filename, to, ...rest] = positionals;
-    if (!filename || !to) {
-        console.error('Usage: codiedev send <filename> <recipient> ["<message>"]');
-        process.exit(1);
-    }
+    if (!filename || !to)
+        return null;
     // Recombine remaining tokens — supports both quoted and unquoted messages.
-    const message = rest.length > 0 ? (0, shared_1.stripQuotes)(rest.join(" ")) : undefined;
-    return { filename, to, message };
+    const message = rest.length > 0 ? (0, shared_1.stripQuotes)(rest.join(" ")) : "";
+    return [to, ...(message ? [message] : []), "--with", filename];
 }
 async function runSend(args, configOverride) {
-    const parsed = parseArgs(args);
-    const config = configOverride ?? (0, shared_1.requireConfig)();
-    const start = Date.now();
-    try {
-        const body = {
-            filename: parsed.filename,
-            to: parsed.to,
-        };
-        if (parsed.message)
-            body.message = parsed.message;
-        const res = await (0, shared_1.apiRequest)("POST", "/api/cli/send-to", {
-            config,
-            body,
-        });
-        (0, shared_1.recordAgentEvent)(config, {
-            tool: "codiedev_send_to",
-            ok: true,
-            latencyMs: Date.now() - start,
-        });
-        const who = res.recipient ? `${res.recipient.name} (${res.recipient.email})` : parsed.to;
-        if (parsed.message) {
-            console.log(`Sent ${parsed.filename} to ${who}.`);
-        }
-        else {
-            console.log(`Shared ${parsed.filename} with ${who} (no message).`);
-        }
-    }
-    catch (err) {
-        (0, shared_1.recordAgentEvent)(config, {
-            tool: "codiedev_send_to",
-            ok: false,
-            latencyMs: Date.now() - start,
-            error: err.message,
-        });
-        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(`Send failed: ${err.message}`);
-        }
+    const pingArgs = sendToPingArgs(args);
+    if (!pingArgs) {
+        console.error('Usage: codiedev send <artifact> <recipient> ["<message>"]  (same as: codiedev ping <recipient> ["<message>"] --with <artifact>)');
         process.exit(1);
     }
+    await (0, ping_1.runPing)(pingArgs, configOverride);
 }

package/dist/commands/share.js

@@ -1,7 +1,7 @@
 "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.
+// grant a teammate access to an artifact (no notification). Kept as an alias:
+// `codiedev ping <recipient> --with <filename> [--edit]` lands here too.
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.runShare = runShare;
 const shared_1 = require("./shared");

package/dist/mcp.js

@@ -174,10 +174,10 @@ 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 a teammate about " +
-            "this spec'). Recipients are resolved by first name, full name, or email " +
+        description: "Send a message to a teammate on Codiedev, optionally with an " +
+            "artifact (they also get read access to it). Use when the user asks to " +
+            "ping, ask, send something to, or get feedback from a teammate by name " +
+            "(e.g. 'send this spec to a teammate'). 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: {
@@ -194,8 +194,13 @@ const TOOLS = [
                 },
                 subjectKey: {
                     type: "string",
-                    description: "Optional filename key of an artifact the message is about " +
-                        "(e.g. 'spec-214.md'). Leaving blank sends a standalone ping.",
+                    description: "Optional filename key of an artifact to send (e.g. " +
+                        "'spec-214.md'). The teammate also gets read access to it. " +
+                        "Leaving blank sends a standalone ping.",
+                },
+                edit: {
+                    type: "boolean",
+                    description: "With subjectKey: give edit access instead of read (owner only).",
                 },
             },
             required: ["to", "body"],
@@ -245,7 +250,7 @@ const TOOLS = [
             "without sending a notification. Use when the user says 'share this " +
             "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.",
+            "codiedev_ping with subjectKey instead.",
         inputSchema: {
             type: "object",
             properties: {
@@ -264,27 +269,6 @@ const TOOLS = [
             required: ["filename", "to"],
         },
     },
-    {
-        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 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: {
-            type: "object",
-            properties: {
-                filename: { type: "string", description: "Artifact filename." },
-                to: { type: "string", description: "Teammate first name, full name, or email." },
-                message: {
-                    type: "string",
-                    description: "Optional short note to send with the share. If omitted, only " +
-                        "the grant is created (no ping).",
-                },
-            },
-            required: ["filename", "to"],
-        },
-    },
     {
         name: "codiedev_search",
         description: "Search the team's artifact library by natural-language query. Use " +
@@ -534,12 +518,13 @@ async function handlePing(args, config) {
     const to = asString(args.to);
     const body = asString(args.body);
     const subjectKey = asStringOrUndefined(args.subjectKey);
+    const grant = subjectKey ? (args.edit === true ? "edit" : "read") : undefined;
     if (!to)
         throw new Error("to required");
     if (!body)
         throw new Error("body required");
     try {
-        const res = await (0, shared_1.apiRequest)("POST", "/api/cli/ping", { config, body: { to, body, subjectKey } });
+        const res = await (0, shared_1.apiRequest)("POST", "/api/cli/ping", { config, body: { to, body, subjectKey, ...(grant ? { grant } : {}) } });
         return {
             content: [
                 {

package/dist/utils.d.ts

@@ -143,7 +143,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

@@ -1674,13 +1674,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 +1755,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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codiedev",
-  "version": "0.9.88",
+  "version": "0.9.89",
   "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",