@vellumai/assistant 0.7.3 → 0.8.1

package/src/cli/utils/__tests__/conversation-id.test.ts

@@ -0,0 +1,66 @@
+import { afterEach, beforeEach, describe, expect, test } from "bun:test";
+
+import { resolveConversationId } from "../conversation-id.js";
+
+const FAILURE_HELP = "No conversation ID. Provide one explicitly.";
+
+let savedConvId: string | undefined;
+let savedSkillCtx: string | undefined;
+
+beforeEach(() => {
+  savedConvId = process.env.__CONVERSATION_ID;
+  savedSkillCtx = process.env.__SKILL_CONTEXT_JSON;
+  delete process.env.__CONVERSATION_ID;
+  delete process.env.__SKILL_CONTEXT_JSON;
+});
+
+afterEach(() => {
+  if (savedConvId !== undefined) {
+    process.env.__CONVERSATION_ID = savedConvId;
+  } else {
+    delete process.env.__CONVERSATION_ID;
+  }
+  if (savedSkillCtx !== undefined) {
+    process.env.__SKILL_CONTEXT_JSON = savedSkillCtx;
+  } else {
+    delete process.env.__SKILL_CONTEXT_JSON;
+  }
+});
+
+describe("resolveConversationId", () => {
+  test("explicit provided → returns it", () => {
+    const result = resolveConversationId({
+      explicit: "conv-explicit-123",
+      failureHelp: FAILURE_HELP,
+    });
+    expect(result).toBe("conv-explicit-123");
+  });
+
+  test("explicit absent, __SKILL_CONTEXT_JSON has conversationId → returns it", () => {
+    process.env.__SKILL_CONTEXT_JSON = JSON.stringify({
+      conversationId: "conv-from-skill-ctx",
+    });
+    const result = resolveConversationId({ failureHelp: FAILURE_HELP });
+    expect(result).toBe("conv-from-skill-ctx");
+  });
+
+  test("both envs absent → throws with provided failureHelp", () => {
+    expect(() =>
+      resolveConversationId({ failureHelp: FAILURE_HELP }),
+    ).toThrow(FAILURE_HELP);
+  });
+
+  test("malformed __SKILL_CONTEXT_JSON → falls through to __CONVERSATION_ID", () => {
+    process.env.__SKILL_CONTEXT_JSON = "not-valid-json{{{";
+    process.env.__CONVERSATION_ID = "conv-from-env";
+    const result = resolveConversationId({ failureHelp: FAILURE_HELP });
+    expect(result).toBe("conv-from-env");
+  });
+
+  test("__SKILL_CONTEXT_JSON without conversationId field → falls through to __CONVERSATION_ID", () => {
+    process.env.__SKILL_CONTEXT_JSON = JSON.stringify({ other: "value" });
+    process.env.__CONVERSATION_ID = "conv-from-env-fallback";
+    const result = resolveConversationId({ failureHelp: FAILURE_HELP });
+    expect(result).toBe("conv-from-env-fallback");
+  });
+});

package/src/cli/utils/__tests__/parse-duration.test.ts

@@ -0,0 +1,49 @@
+import { describe, expect, test } from "bun:test";
+
+import { parseDuration } from "../parse-duration.js";
+
+describe("parseDuration", () => {
+  test('"30s" → 30', () => {
+    expect(parseDuration("30s")).toBe(30);
+  });
+
+  test('"5m" → 300', () => {
+    expect(parseDuration("5m")).toBe(300);
+  });
+
+  test('"1h" → 3600', () => {
+    expect(parseDuration("1h")).toBe(3600);
+  });
+
+  test('"1h30m" → 5400', () => {
+    expect(parseDuration("1h30m")).toBe(5400);
+  });
+
+  test('"90m" → 5400', () => {
+    expect(parseDuration("90m")).toBe(5400);
+  });
+
+  test('"60" (bare number) → 60', () => {
+    expect(parseDuration("60")).toBe(60);
+  });
+
+  test("invalid string → throws Error", () => {
+    expect(() => parseDuration("abc")).toThrow('Invalid duration: "abc"');
+  });
+
+  test("empty string → throws Error", () => {
+    expect(() => parseDuration("")).toThrow();
+  });
+
+  test('"1hxyz" (partial parse) → throws with "Invalid duration"', () => {
+    expect(() => parseDuration("1hxyz")).toThrow("Invalid duration");
+  });
+
+  test('"1h-30m" (partial parse with dash) → throws with "Invalid duration"', () => {
+    expect(() => parseDuration("1h-30m")).toThrow("Invalid duration");
+  });
+
+  test('"30mxyz" (partial parse) → throws with "Invalid duration"', () => {
+    expect(() => parseDuration("30mxyz")).toThrow("Invalid duration");
+  });
+});

package/src/cli/utils/conversation-id.ts

@@ -0,0 +1,30 @@
+/**
+ * Resolve the conversation ID by precedence:
+ *   1. Explicit value provided in `opts.explicit`
+ *   2. `__SKILL_CONTEXT_JSON` env var (set by skill sandbox runner)
+ *   3. `__CONVERSATION_ID` env var (set by bash tool subprocess)
+ *   4. Throw with the provided `failureHelp` message
+ */
+export function resolveConversationId(opts: {
+  explicit?: string;
+  failureHelp: string;
+}): string {
+  if (opts.explicit) return opts.explicit;
+
+  const contextJson = process.env.__SKILL_CONTEXT_JSON;
+  if (contextJson) {
+    try {
+      const parsed = JSON.parse(contextJson) as Record<string, unknown>;
+      if (typeof parsed.conversationId === "string" && parsed.conversationId) {
+        return parsed.conversationId;
+      }
+    } catch {
+      // ignore malformed JSON
+    }
+  }
+
+  const envConvId = process.env.__CONVERSATION_ID;
+  if (envConvId && typeof envConvId === "string") return envConvId;
+
+  throw new Error(opts.failureHelp);
+}

package/src/cli/utils/parse-duration.ts

@@ -0,0 +1,41 @@
+/**
+ * Parse a human-friendly duration string into seconds.
+ *
+ * Accepted formats:
+ *   "60"     → 60   (bare number = seconds)
+ *   "60s"    → 60
+ *   "5m"     → 300
+ *   "1h"     → 3600
+ *   "1h30m"  → 5400
+ *   "90s"    → 90
+ *
+ * Note: `--ttl never` is handled at the call site (mapped to ttlSeconds: null);
+ * do NOT pass "never" to this function.
+ */
+export function parseDuration(input: string): number {
+  if (/^\d+$/.test(input)) return parseInt(input, 10);
+  // Validate the whole string is composed entirely of <digits><unit> groups
+  if (!/^(\d+[hms])+$/.test(input)) {
+    throw new Error(`Invalid duration: "${input}"`);
+  }
+
+  let total = 0;
+  const re = /(\d+)(h|m|s)/g;
+  let match;
+  while ((match = re.exec(input)) !== null) {
+    const val = parseInt(match[1], 10);
+    switch (match[2]) {
+      case "h":
+        total += val * 3600;
+        break;
+      case "m":
+        total += val * 60;
+        break;
+      case "s":
+        total += val;
+        break;
+    }
+  }
+  if (total === 0) throw new Error(`Invalid duration: "${input}"`);
+  return total;
+}

package/src/config/acp-defaults.test.ts

@@ -29,10 +29,14 @@ describe("DEFAULT_ACP_AGENT_PROFILES", () => {
     });
   });
 
-  test("is frozen at runtime so mutation throws in strict mode", () => {
+  test("is deeply frozen so mutation throws in strict mode", () => {
     expect(Object.isFrozen(DEFAULT_ACP_AGENT_PROFILES)).toBe(true);
     for (const profile of Object.values(DEFAULT_ACP_AGENT_PROFILES)) {
       expect(Object.isFrozen(profile)).toBe(true);
+      // `args` arrays must also be frozen — `Object.freeze` is shallow, so
+      // an unfrozen `args` would let one caller silently corrupt every other
+      // read of the shared default via `.push(...)` / `.splice(...)`.
+      expect(Object.isFrozen(profile.args)).toBe(true);
     }
   });
 });

package/src/config/acp-defaults.ts

@@ -1,5 +1,11 @@
 import type { AcpAgentConfig } from "./acp-schema.js";
 
+// Shared frozen empty args array — these defaults are read by every ACP spawn,
+// so a single accidental `args.push(...)` from one caller would corrupt every
+// subsequent read. Cast through `unknown` because `AcpAgentConfig.args` is
+// `string[]` (Zod-inferred) but the value is genuinely immutable at runtime.
+const FROZEN_EMPTY_ARGS = Object.freeze([] as string[]) as unknown as string[];
+
 /**
  * Default ACP agent profiles that ship with the assistant.
  *
@@ -7,20 +13,21 @@ import type { AcpAgentConfig } from "./acp-schema.js";
  * agent id, the resolver falls back to this map so common agents like `claude`
  * and `codex` Just Work without requiring per-user config.
  *
- * Keyed by agent id. Frozen so accidental runtime mutation throws in strict
- * mode and the readonly type matches actual runtime behavior.
+ * Keyed by agent id. Deeply frozen — the outer object, each profile, and the
+ * `args` arrays — so mutation throws in strict mode rather than silently
+ * corrupting the shared defaults.
  */
 export const DEFAULT_ACP_AGENT_PROFILES: Readonly<
   Record<string, AcpAgentConfig>
 > = Object.freeze({
   claude: Object.freeze({
     command: "claude-agent-acp",
-    args: [],
+    args: FROZEN_EMPTY_ARGS,
     description: "Claude Code (via @agentclientprotocol/claude-agent-acp)",
   }),
   codex: Object.freeze({
     command: "codex-acp",
-    args: [],
+    args: FROZEN_EMPTY_ARGS,
     description: "OpenAI Codex CLI (via @zed-industries/codex-acp)",
   }),
 });

package/src/config/bundled-skills/acp/TOOLS.json

@@ -11,7 +11,7 @@
         "properties": {
           "agent": {
             "type": "string",
-            "description": "Which agent to spawn (e.g. 'claude', 'codex', 'gemini'). Defaults to 'claude'."
+            "description": "Which agent to spawn (e.g. 'claude', 'codex'). Defaults to 'claude'."
           },
           "task": {
             "type": "string",
@@ -67,7 +67,7 @@
       "name": "acp_steer",
       "description": "**Interrupts** the in-flight prompt of a running ACP session and replaces it with `instruction`. Use to redirect the agent (e.g., 'stop, do X instead'). For follow-up work that should happen *after* the current task, do NOT use this — wait for `acp_session_completed` and `acp_spawn` again.",
       "category": "orchestration",
-      "risk": "medium",
+      "risk": "high",
       "input_schema": {
         "type": "object",
         "properties": {

package/src/config/bundled-skills/app-builder/SKILL.md

@@ -6,8 +6,6 @@ metadata:
   emoji: "🏗️"
   vellum:
     display-name: "App Builder"
-    includes:
-      - "frontend-design"
     activation-hints:
       - "User asks to build an app, landing page, website, dashboard, tool, calculator, game, tracker, or interactive page"
       - "User asks to visualize data or says 'let's visualize this' — use the app sandbox to build interactive visualizations"
@@ -20,7 +18,7 @@ You are an expert app builder and visual designer. When the user asks you to cre
 
 **Your default behavior:** Build immediately. The user types "build me a habit tracker" and you deliver a complete, polished app with a domain-matched color palette, atmospheric background, and thoughtful interactions. Don't ask what colors they want. Don't show wireframes. Just build something stunning and let them refine from there.
 
-**Design quality is delegated to the `frontend-design` skill.** That skill defines your aesthetic principles: typography, color strategy, motion, spatial composition, and visual detail. Follow it completely for every build. This skill (app-builder) handles the technical infrastructure: sandbox constraints, data bridge, widget API, app lifecycle, and interaction patterns.
+**Design quality is delegated to the `frontend-design` skill, so you must also load/install that before proceeding.** That skill defines your aesthetic principles: typography, color strategy, motion, spatial composition, and visual detail. Follow it completely for every build. This skill (app-builder) handles the technical infrastructure: sandbox constraints, data bridge, widget API, app lifecycle, and interaction patterns.
 
 ## Filesystem Layout
 

package/src/config/bundled-skills/app-control/TOOLS.json

@@ -21,6 +21,10 @@
           "reasoning": {
             "type": "string",
             "description": "Explanation of why you are starting this app"
+          },
+          "target_client_id": {
+            "type": "string",
+            "description": "ID of the specific client to target. Required when multiple clients support host_app_control; omit when only one is connected. Obtain IDs from `assistant clients list --capability host_app_control`."
           }
         },
         "required": ["app", "reasoning"]
@@ -43,6 +47,10 @@
           "settle_ms": {
             "type": "integer",
             "description": "Milliseconds to wait before capturing so the target app and the WindowServer can flush pending input + composite a fresh frame. Default ~200ms (sized for emulator-class apps at 60fps). Pass 0 for static UIs; raise for slow-feedback apps."
+          },
+          "target_client_id": {
+            "type": "string",
+            "description": "ID of the specific client to target. Required when multiple clients support host_app_control; omit when only one is connected. Obtain IDs from `assistant clients list --capability host_app_control`."
           }
         },
         "required": ["app"]
@@ -78,6 +86,10 @@
           "reasoning": {
             "type": "string",
             "description": "Explanation of why you are pressing this key"
+          },
+          "target_client_id": {
+            "type": "string",
+            "description": "ID of the specific client to target. Required when multiple clients support host_app_control; omit when only one is connected. Obtain IDs from `assistant clients list --capability host_app_control`."
           }
         },
         "required": ["app", "key", "reasoning"]
@@ -109,6 +121,10 @@
           "reasoning": {
             "type": "string",
             "description": "Explanation of why you are pressing this combo"
+          },
+          "target_client_id": {
+            "type": "string",
+            "description": "ID of the specific client to target. Required when multiple clients support host_app_control; omit when only one is connected. Obtain IDs from `assistant clients list --capability host_app_control`."
           }
         },
         "required": ["app", "keys", "reasoning"]
@@ -158,6 +174,10 @@
           "reasoning": {
             "type": "string",
             "description": "Explanation of what this sequence does and why"
+          },
+          "target_client_id": {
+            "type": "string",
+            "description": "ID of the specific client to target. Required when multiple clients support host_app_control; omit when only one is connected. Obtain IDs from `assistant clients list --capability host_app_control`."
           }
         },
         "required": ["app", "steps", "reasoning"]
@@ -184,6 +204,10 @@
           "reasoning": {
             "type": "string",
             "description": "Explanation of what you are typing and why"
+          },
+          "target_client_id": {
+            "type": "string",
+            "description": "ID of the specific client to target. Required when multiple clients support host_app_control; omit when only one is connected. Obtain IDs from `assistant clients list --capability host_app_control`."
           }
         },
         "required": ["app", "text", "reasoning"]
@@ -223,6 +247,10 @@
           "reasoning": {
             "type": "string",
             "description": "Explanation of what you see and why you are clicking here"
+          },
+          "target_client_id": {
+            "type": "string",
+            "description": "ID of the specific client to target. Required when multiple clients support host_app_control; omit when only one is connected. Obtain IDs from `assistant clients list --capability host_app_control`."
           }
         },
         "required": ["app", "x", "y", "reasoning"]
@@ -266,6 +294,10 @@
           "reasoning": {
             "type": "string",
             "description": "Explanation of what you are dragging and why"
+          },
+          "target_client_id": {
+            "type": "string",
+            "description": "ID of the specific client to target. Required when multiple clients support host_app_control; omit when only one is connected. Obtain IDs from `assistant clients list --capability host_app_control`."
           }
         },
         "required": ["app", "from_x", "from_y", "to_x", "to_y", "reasoning"]

package/src/config/bundled-skills/contacts/SKILL.md

@@ -15,27 +15,7 @@ Manage the user's contacts, relationship graph, access control (trusted contacts
 
 ## Contact Management
 
-### Create or update a contact
-
-Create a new contact or update an existing one in the relationship graph. Use this to track people the user interacts with across channels.
-
-```bash
-assistant contacts upsert --display-name "<name>" --notes "<notes>" --channels '<json_array>' --json
-```
-
-To update an existing contact, include the `--id` flag.
-
-Required flags:
-
-- `--display-name` -- the contact's name
-
-Optional flags:
-
-- `--id` -- contact ID to update (omit to create new, or auto-match by channel address)
-- `--notes` -- free-text notes about this contact (e.g. relationship, communication preferences, response expectations)
-- `--role` -- contact role: `contact` or `guardian` (default: `contact`)
-- `--contact-type` -- contact type: `human` or `assistant` (default: `human`)
-- `--channels` -- JSON array of channel objects, each with `type`, `address`, and optional `isPrimary`, `externalUserId`, `externalChatId`, `status`, `policy`
+> **Contact writes are guardian-only.** You can list, search, and merge contacts, but creating contacts and granting access happen through the guardian-facing flows: the **Contacts tab in the assistant web UI** for new contacts and channel verification, and `assistant contacts invites create` for invite-based onboarding. The LLM does **not** have a direct create/update tool — when a user asks for one, walk them to the guardian flow instead.
 
 ### Search contacts
 
@@ -116,25 +96,12 @@ The response contains `{ ok: true, contacts: [...] }` where each contact has:
 
 ### Allow a user (add trusted contact)
 
-Use this when the user wants to grant someone access to message the assistant. **Always confirm with the user before executing this action.**
-
-Ask the user: _"I'll add [name/identifier] on [channel] as an allowed contact. Should I proceed?"_
-
-```bash
-assistant contacts upsert --display-name "<display_name>" --channels '[{"type":"<channel>","address":"<user_id>","externalUserId":"<user_id>","status":"active","policy":"allow"}]' --json
-```
-
-Required flags:
+You can't add a trusted contact directly — contact writes are guardian-only. When the user wants to grant someone access, walk them through one of these guardian paths:
 
-- `--display-name` -- human-readable name for the contact
-- `--channels` -- at least one channel entry with:
-  - `type` -- the channel type (e.g., `telegram`)
-  - `address` -- the channel-specific identifier
-  - `externalUserId` -- the user's ID on that channel (or `externalChatId` for chat-based channels)
-  - `status` -- set to `"active"` for immediate access
-  - `policy` -- set to `"allow"` to grant messaging access
+1. **Web UI** — open the Contacts tab in the assistant dashboard, click "Add contact", and verify the channel via the outbound verification flow (SMS code, Telegram message, etc.).
+2. **Invite link** — for channels that support it (Telegram, email, etc.), create an invite with `assistant contacts invites create --source-channel <channel> --contact-id <existing_contact_id>` (the contact must already exist).
 
-If the user provides a name but not an external ID, explain that you need the channel-specific user ID or chat ID to create the contact entry. For Telegram, this is a numeric user ID.
+If the user insists on adding someone, tell them: _"I can't add trusted contacts directly — that's a guardian-only action. You can add them from the Contacts tab in the assistant dashboard, or I can create an invite link for an existing contact."_
 
 ### Revoke a user (remove access)
 
@@ -169,7 +136,7 @@ Replace `<channel_id>` with the channel's `id` from the contact's `channels` arr
 
 Invite links let the guardian share a link or code that automatically grants access when used. Telegram invites use a deep link; voice invites use a phone number + numeric code; email, WhatsApp, and Slack invites use a 6-digit code that the invitee sends to the assistant on the respective channel.
 
-**Every invite must be bound to a contact.** Before creating an invite, look up the contact with `assistant contacts list` or create one with `assistant contacts upsert`, then pass the contact's `id` via the required `--contact-id` flag.
+**Every invite must be bound to a contact.** Before creating an invite, look up the contact with `assistant contacts list` and pass the contact's `id` via the required `--contact-id` flag. **You cannot create new contacts** — if the target contact doesn't exist yet, tell the user to add them from the **Contacts tab in the assistant web UI** first, then come back to create the invite.
 
 ### Create a Telegram invite link
 
@@ -216,7 +183,7 @@ echo "$INVITE_URL"
 Required flags:
 
 - `--source-channel` -- must be `telegram`
-- `--contact-id` -- the ID of the contact this invite is for. Look up or create the contact first with `assistant contacts list` or `assistant contacts upsert`.
+- `--contact-id` -- the ID of the contact this invite is for. Look up the contact first with `assistant contacts list`. New contacts must be added via the Contacts tab in the assistant web UI; you cannot create them here.
 
 Optional flags:
 
@@ -256,7 +223,7 @@ assistant contacts invites create --source-channel phone --contact-id "<contact_
 Required flags:
 
 - `--source-channel` -- must be `phone`
-- `--contact-id` -- the ID of the contact this invite is for. Look up or create the contact first with `assistant contacts list` or `assistant contacts upsert`.
+- `--contact-id` -- the ID of the contact this invite is for. Look up the contact first with `assistant contacts list`. New contacts must be added via the Contacts tab in the assistant web UI; you cannot create them here.
 - `--expected-external-user-id` -- the invitee's phone number in E.164 format (e.g., `+15551234567`)
 - `--friend-name` -- the invitee's display name (e.g., "Mom", "Dr. Smith"). Used during the voice verification call to personalize the experience.
 - `--guardian-name` -- the guardian's display name (e.g., "Alex"). Used during the voice verification call so the invitee knows who invited them.
@@ -302,7 +269,7 @@ assistant contacts invites create --source-channel email --contact-id "<contact_
 Required flags:
 
 - `--source-channel` -- must be `email`
-- `--contact-id` -- the ID of the contact this invite is for. Look up or create the contact first with `assistant contacts list` or `assistant contacts upsert`.
+- `--contact-id` -- the ID of the contact this invite is for. Look up the contact first with `assistant contacts list`. New contacts must be added via the Contacts tab in the assistant web UI; you cannot create them here.
 
 The response contains `{ ok: true, invite: { id, token, inviteCode, guardianInstruction, channelHandle, ... } }`.
 
@@ -333,7 +300,7 @@ assistant contacts invites create --source-channel whatsapp --contact-id "<conta
 Required flags:
 
 - `--source-channel` -- must be `whatsapp`
-- `--contact-id` -- the ID of the contact this invite is for. Look up or create the contact first with `assistant contacts list` or `assistant contacts upsert`.
+- `--contact-id` -- the ID of the contact this invite is for. Look up the contact first with `assistant contacts list`. New contacts must be added via the Contacts tab in the assistant web UI; you cannot create them here.
 
 The response contains `{ ok: true, invite: { id, token, inviteCode, guardianInstruction, channelHandle?, ... } }`.
 
@@ -366,7 +333,7 @@ assistant contacts invites create --source-channel slack --contact-id "<contact_
 Required flags:
 
 - `--source-channel` -- must be `slack`
-- `--contact-id` -- the ID of the contact this invite is for. Look up or create the contact first with `assistant contacts list` or `assistant contacts upsert`.
+- `--contact-id` -- the ID of the contact this invite is for. Look up the contact first with `assistant contacts list`. New contacts must be added via the Contacts tab in the assistant web UI; you cannot create them here.
 
 The response follows the same shape as email and WhatsApp invites (`inviteCode`, `guardianInstruction`, `channelHandle`).
 
@@ -497,7 +464,7 @@ Each channel has:
 
 **"Who can message me?"** -- List all contacts with `assistant contacts list --json`, present active channels as a formatted list.
 
-**"Add my friend to Telegram"** -- Ask for their Telegram user ID (numeric) and display name, confirm, then create a contact with `assistant contacts upsert` including a channel entry with `policy: "allow"` and `status: "active"`.
+**"Add my friend to Telegram"** -- You can't add trusted contacts directly (guardian-only action). Tell the user to add the contact from the Contacts tab in the assistant dashboard, where they can enter the Telegram user ID and verify the channel. Once the contact exists, you can create an invite with `assistant contacts invites create --source-channel telegram --contact-id <contact_id>`.
 
 **"Remove [name]'s access"** -- List contacts with `assistant contacts list --json` to find them, identify the channel to revoke, confirm the revocation, then run `assistant contacts channels update-status <channel_id> --status revoked --json`.
 

package/src/config/bundled-skills/contacts/TOOLS.json

@@ -1,63 +1,6 @@
 {
   "version": 1,
   "tools": [
-    {
-      "name": "contact_upsert",
-      "description": "Create or update a contact in the relationship graph. Use this to track people the user interacts with across channels (email, Slack, etc.).",
-      "category": "contacts",
-      "risk": "low",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "id": {
-            "type": "string",
-            "description": "Contact ID to update. Omit to create a new contact (or auto-match by channel address)."
-          },
-          "display_name": {
-            "type": "string",
-            "description": "Display name for the contact"
-          },
-          "notes": {
-            "type": "string",
-            "description": "Free-text notes about this contact (e.g. relationship, communication preferences, response expectations)"
-          },
-          "channels": {
-            "type": "array",
-            "description": "Communication channels for this contact",
-            "items": {
-              "type": "object",
-              "properties": {
-                "type": {
-                  "type": "string",
-                  "enum": [
-                    "email",
-                    "slack",
-                    "whatsapp",
-                    "phone",
-                    "telegram",
-                    "discord",
-                    "other"
-                  ],
-                  "description": "Channel type"
-                },
-                "address": {
-                  "type": "string",
-                  "description": "Channel address (email address, Slack handle, phone number, etc.)"
-                },
-                "is_primary": {
-                  "type": "boolean",
-                  "description": "Whether this is the primary channel for this type"
-                }
-              },
-              "required": ["type", "address"]
-            }
-          }
-        },
-        "required": ["display_name"]
-      },
-      "executor": "tools/contact-upsert.ts",
-      "execution_target": "host"
-    },
     {
       "name": "contact_search",
       "description": "Search for contacts by name, channel address, or other criteria. Returns matching contacts with their channel information.",

package/src/config/bundled-skills/messaging/tools/messaging-archive-by-sender.ts

@@ -1,13 +1,9 @@
-import { emitFeedEvent } from "../../../../home/emit-feed-event.js";
 import type {
   ToolContext,
   ToolExecutionResult,
 } from "../../../../tools/types.js";
-import { getLogger } from "../../../../util/logger.js";
 import { err, getProviderConnection, ok, resolveProvider } from "./shared.js";
 
-const log = getLogger("messaging-archive-by-sender");
-
 export async function run(
   input: Record<string, unknown>,
   context: ToolContext,
@@ -50,14 +46,6 @@ export async function run(
     }
 
     const summary = `Archived ${result.archived} message(s) matching query: ${query}`;
-    void emitFeedEvent({
-      source: "gmail",
-      title: "Messages Archived",
-      summary,
-      dedupKey: `email-archive:${Date.now()}`,
-    }).catch((err) => {
-      log.warn({ err }, "Failed to emit email archive feed event");
-    });
     if (result.truncated) {
       return ok(
         `${summary}\n\nNote: this operation was capped at 5000 messages. Additional messages matching the query may remain in the inbox. Run the command again to archive more.`,