@vellumai/assistant 0.6.5 → 0.7.0

package/src/config/bundled-skills/messaging/tools/messaging-send.ts

@@ -1,6 +1,7 @@
 import { readFile } from "node:fs/promises";
 import { basename } from "node:path";
 
+import { emitFeedEvent } from "../../../../home/emit-feed-event.js";
 import {
   addMessage,
   getConversation,
@@ -149,6 +150,14 @@ export async function run(
             ccList.length > 0
               ? `To: ${toList.join(", ")}; Cc: ${ccList.join(", ")}`
               : `To: ${toList.join(", ")}`;
+          void emitFeedEvent({
+            source: "gmail",
+            title: "Email Draft Created",
+            summary: `Drafted reply to ${recipientSummary}.`,
+            dedupKey: `email-draft:${draft.id}`,
+          }).catch((err) => {
+            log.warn({ err }, "Failed to emit email draft feed event");
+          });
           return ok(
             `Gmail draft created with ${attachments.length} attachment(s): ${filenames} (Draft ID: ${draft.id}). ${recipientSummary}. Review in Gmail Drafts, then tell me to send it or send it yourself.`,
           );
@@ -169,6 +178,14 @@ export async function run(
           ccList.length > 0
             ? `To: ${toList.join(", ")}; Cc: ${ccList.join(", ")}`
             : `To: ${toList.join(", ")}`;
+        void emitFeedEvent({
+          source: "gmail",
+          title: "Email Draft Created",
+          summary: `Drafted reply to ${recipientSummary}.`,
+          dedupKey: `email-draft:${draft.id}`,
+        }).catch((err) => {
+          log.warn({ err }, "Failed to emit email draft feed event");
+        });
         return ok(
           `Gmail draft created (ID: ${draft.id}). ${recipientSummary}. Review in Gmail Drafts, then tell me to send it or send it yourself.`,
         );
@@ -195,6 +212,14 @@ export async function run(
         const draft = await createDraftRaw(gmailConn, raw, threadId);
 
         const filenames = attachments.map((a) => a.filename).join(", ");
+        void emitFeedEvent({
+          source: "gmail",
+          title: "Email Draft Created",
+          summary: "Created an email draft.",
+          dedupKey: `email-draft:${draft.id}`,
+        }).catch((err) => {
+          log.warn({ err }, "Failed to emit email draft feed event");
+        });
         return ok(
           `Gmail draft created with ${attachments.length} attachment(s): ${filenames} (Draft ID: ${draft.id}). Review in Gmail Drafts, then tell me to send it or send it yourself.`,
         );
@@ -211,6 +236,14 @@ export async function run(
         undefined,
         threadId,
       );
+      void emitFeedEvent({
+        source: "gmail",
+        title: "Email Draft Created",
+        summary: "Created an email draft.",
+        dedupKey: `email-draft:${draft.id}`,
+      }).catch((err) => {
+        log.warn({ err }, "Failed to emit email draft feed event");
+      });
       return ok(
         `Gmail draft created (ID: ${draft.id}). Review it in your Gmail Drafts, then tell me to send it or send it yourself from Gmail.`,
       );
@@ -224,6 +257,31 @@ export async function run(
       assistantId: context.assistantId,
     });
 
+    const sendSummary =
+      provider.id === "slack"
+        ? "Sent a Slack message."
+        : provider.id === "telegram"
+          ? "Sent a Telegram message."
+          : "Sent an email.";
+    void emitFeedEvent({
+      source:
+        provider.id === "slack"
+          ? "slack"
+          : provider.id === "telegram"
+            ? "telegram"
+            : "gmail",
+      title:
+        provider.id === "slack"
+          ? "Slack Message Sent"
+          : provider.id === "telegram"
+            ? "Telegram Message Sent"
+            : "Email Sent",
+      summary: sendSummary,
+      dedupKey: `message-sent:${result.id}`,
+    }).catch((err) => {
+      log.warn({ err }, "Failed to emit message send feed event");
+    });
+
     const threadSuffix = result.threadId
       ? `, "thread_id": "${result.threadId}"`
       : "";

package/src/config/bundled-skills/playbooks/tools/playbook-create.ts

@@ -1,6 +1,6 @@
 import { sql } from "drizzle-orm";
 
-import { getDb } from "../../../../memory/db.js";
+import { getDb } from "../../../../memory/db-connection.js";
 import { createNode, updateNode } from "../../../../memory/graph/store.js";
 import type { NewNode } from "../../../../memory/graph/types.js";
 import { enqueueMemoryJob } from "../../../../memory/jobs-store.js";

package/src/config/bundled-skills/playbooks/tools/playbook-list.ts

@@ -1,6 +1,6 @@
 import { and, eq, sql } from "drizzle-orm";
 
-import { getDb } from "../../../../memory/db.js";
+import { getDb } from "../../../../memory/db-connection.js";
 import { memoryGraphNodes } from "../../../../memory/schema.js";
 import { parsePlaybookStatement } from "../../../../playbooks/types.js";
 import type {

package/src/config/bundled-skills/playbooks/tools/playbook-update.ts

@@ -1,6 +1,6 @@
 import { and, eq, sql } from "drizzle-orm";
 
-import { getDb } from "../../../../memory/db.js";
+import { getDb } from "../../../../memory/db-connection.js";
 import { getNode, updateNode } from "../../../../memory/graph/store.js";
 import { enqueueMemoryJob } from "../../../../memory/jobs-store.js";
 import { memoryGraphNodes } from "../../../../memory/schema.js";

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

@@ -8,7 +8,7 @@ metadata:
     display-name: "Schedule"
 ---
 
-Manage scheduled automations. Schedules can be **recurring** (cron or RRULE expression) or **one-shot** (a single `fire_at` timestamp). Both recurring and one-shot schedules support two modes: **execute** (run a message through the assistant) and **notify** (send a notification to the user).
+Manage scheduled automations. Schedules can be **recurring** (cron or RRULE expression) or **one-shot** (a single `fire_at` timestamp). Schedules support three modes: **execute** (run a message through the assistant), **notify** (send a notification to the user), and **script** (run a shell command directly without LLM involvement).
 
 ## Schedule Syntax
 
@@ -70,11 +70,13 @@ Exclusions (EXDATE, EXRULE) always take precedence over inclusions (RRULE, RDATE
 To create a one-time schedule that fires once and is done, pass `fire_at` (an ISO 8601 timestamp) instead of an `expression`. This replaces the old reminder concept - "remind me at 3pm" becomes a one-shot schedule with `fire_at`.
 
 One-shot schedules:
+
 - Fire once at the specified time, then are marked as `fired` and disabled.
 - Support both `execute` and `notify` modes (see below).
 - Can be cancelled before they fire.
 
 Examples:
+
 - "remind me at 3pm" → `schedule_create` with `fire_at: "2025-03-15T15:00:00-05:00"`, `mode: "notify"`
 - "at 5pm, check my email and summarize it" → `schedule_create` with `fire_at`, `mode: "execute"`
 
@@ -84,8 +86,9 @@ The `mode` parameter controls what happens when a schedule fires:
 
 - **execute** (default) - sends the schedule's message to a background assistant conversation for autonomous handling. The assistant processes the message as if the user sent it.
 - **notify** - sends a notification to the user via the notification pipeline. No assistant processing occurs.
+- **script** - runs the `script` field as a shell command directly. No LLM invoked, no conversation created. stdout/stderr are captured in the schedule run record. Exit code 0 = success, non-zero = error. Commands run in the workspace directory with a 60-second timeout.
 
-Use `notify` for simple reminders ("remind me to take medicine at 9am") and `execute` for tasks that need assistant action ("check my calendar at 8am and send me a digest").
+Use `notify` for simple reminders ("remind me to take medicine at 9am"), `execute` for tasks that need assistant action ("check my calendar at 8am and send me a digest"), and `script` for lightweight shell automations that don't need LLM involvement ("refresh a cache", "poll an API", "rotate logs").
 
 ## Conversation Reuse
 
@@ -121,6 +124,7 @@ Optionally pass `routing_hints` (a JSON object) to influence routing decisions (
   3. If neither field is present or the interface is `cli`, omit `preferred_channels`.
 
   When a channel is determined, include it as a routing hint:
+
   ```
   routing_hints: { preferred_channels: ["<resolved channel>"] }
   routing_intent: "all_channels"
@@ -157,6 +161,7 @@ Phrases like "at the 45 minute mark", "at the top of the hour", "at noon", or "2
    - "noon" / "midnight" → 12:00 PM or 12:00 AM today; if past, tomorrow
 
 3. **Ask only if truly ambiguous** - if neither rule resolves, ask for clarification. Never silently default to "from now."
+
 - Timezones default to the system timezone if omitted. Use IANA timezone identifiers (e.g. "America/Los_Angeles").
 - Prefer RRULE for complex patterns that cron cannot express (e.g. "every other Tuesday", "last weekday of the month").
 
@@ -184,7 +189,7 @@ Scheduled messages run without user interaction. If the task produces output tha
 Choose the right delivery tool based on the content:
 
 - **Rich content** (digests, summaries, reports): For Gmail, use `messaging_send` with the target platform and conversation ID. For Slack, use the Slack Web API directly via CLI (`chat.postMessage`). This preserves the full content and posts directly.
-- **Short alerts** (status updates, completion notices): Use `send_notification` to let the notification router pick the best channel. Note: the router's decision engine rewrites content into short alerts, so it is not suitable for rich content.
+- **Short alerts** (status updates, completion notices): Use `assistant notifications send` via `bash` to let the notification router pick the best channel. Note: the router's decision engine rewrites content into short alerts, so it is not suitable for rich content.
 
 Example schedule message for a Slack digest:
 

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

@@ -32,7 +32,11 @@
           },
           "message": {
             "type": "string",
-            "description": "The message to send to the assistant when the schedule triggers"
+            "description": "The message to send to the assistant when the schedule triggers. Required for execute and notify modes."
+          },
+          "script": {
+            "type": "string",
+            "description": "The shell command to run when the schedule triggers. Required for script mode. Runs in the workspace directory with a sanitized environment."
           },
           "enabled": {
             "type": "boolean",
@@ -40,8 +44,8 @@
           },
           "mode": {
             "type": "string",
-            "enum": ["notify", "execute"],
-            "description": "Whether to notify the user or execute autonomously when triggered. Defaults to \"execute\"."
+            "enum": ["notify", "execute", "script"],
+            "description": "Whether to notify the user, execute autonomously via LLM, or run a shell command directly. Defaults to \"execute\"."
           },
           "routing_intent": {
             "type": "string",
@@ -65,7 +69,7 @@
             "description": "Brief non-technical explanation of why this tool is being called"
           }
         },
-        "required": ["name", "message"]
+        "required": ["name"]
       },
       "executor": "tools/schedule-create.ts",
       "execution_target": "host"
@@ -127,7 +131,11 @@
           },
           "message": {
             "type": "string",
-            "description": "New message to send when triggered"
+            "description": "New message to send when triggered (for execute/notify modes)"
+          },
+          "script": {
+            "type": "string",
+            "description": "New shell command to run when triggered (for script mode)"
           },
           "enabled": {
             "type": "boolean",
@@ -135,8 +143,8 @@
           },
           "mode": {
             "type": "string",
-            "enum": ["notify", "execute"],
-            "description": "Whether to notify the user or execute autonomously when triggered"
+            "enum": ["notify", "execute", "script"],
+            "description": "Whether to notify the user, execute autonomously via LLM, or run a shell command directly"
           },
           "routing_intent": {
             "type": "string",

package/src/config/bundled-skills/schedule/references/SCRIPT_MODE_PATTERNS.md

@@ -0,0 +1,59 @@
+# Script Mode Patterns
+
+Script mode runs shell commands without LLM involvement, but scripts can escalate to the assistant or notify the user via CLI commands when conditions are met. This makes script mode a building block for conditional automation — fast, deterministic checks that only invoke heavier machinery when needed.
+
+## Script → LLM Escalation
+
+Use `assistant conversations wake` to hand off to the assistant when a script detects something that needs LLM reasoning. The wake command injects a hint into an existing conversation without creating a user-visible message.
+
+Example: poll an API and wake the assistant only when results change.
+
+```sh
+LAST="/workspace/data/api-status-last.txt"
+CURRENT=$(curl -sf https://api.example.com/status)
+[ "$CURRENT" = "$(cat "$LAST" 2>/dev/null)" ] && exit 0
+echo "$CURRENT" > "$LAST"
+assistant conversations wake CONVERSATION_ID --hint "API status changed: $CURRENT" --source scheduled-poll
+```
+
+Example: check disk usage and escalate to the assistant when it's high.
+
+```sh
+USAGE=$(df /workspace --output=pcent | tail -1 | tr -d ' %')
+[ "$USAGE" -lt 90 ] && exit 0
+assistant conversations wake CONVERSATION_ID --hint "Disk usage at ${USAGE}% — investigate and clean up" --source disk-monitor
+```
+
+## Script → Notification
+
+Use `assistant notifications send` to alert the user directly when a script detects something noteworthy. No LLM is involved — the notification goes straight to the user's connected channels.
+
+Example: check if a service is down and notify the user.
+
+```sh
+if ! curl -sf --max-time 5 https://myapp.example.com/health > /dev/null; then
+  assistant notifications send \
+    --source-channel scheduler \
+    --source-event-name schedule.notify \
+    --message "myapp.example.com health check failed" \
+    --urgency high \
+    --dedupe-key "myapp-health-$(date +%Y%m%d)"
+fi
+```
+
+Example: notify when a long-running background job finishes.
+
+```sh
+if [ -f /workspace/data/export-complete.flag ]; then
+  assistant notifications send \
+    --source-channel scheduler \
+    --source-event-name schedule.notify \
+    --message "Data export finished — file ready at /workspace/data/export.csv" \
+    --no-requires-action
+  rm /workspace/data/export-complete.flag
+fi
+```
+
+## Tips
+
+Both patterns keep scheduled runs fast and cheap — the script exits immediately when nothing interesting happens, and only reaches for the assistant or notification system when there's something to act on. Use `quiet: true` on the schedule to suppress the per-run completion noise.

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

@@ -1,6 +1,6 @@
 ---
 name: settings
-description: Manage assistant voice, avatar (set, remove, view, show), and system settings
+description: Manage assistant voice and system settings
 compatibility: "Designed for Vellum personal assistants"
 metadata:
   emoji: "\u2699\uFE0F"
@@ -8,19 +8,4 @@ metadata:
     display-name: "Settings"
 ---
 
-Tools for managing assistant settings: voice configuration (TTS voice, PTT activation key, conversation timeout), avatar management (set, remove, view/show current avatar), system settings navigation, and in-app settings tab navigation.
-
-## Avatar
-
-When the user asks to set, change, or update your avatar to an image they provide:
-
-1. Find the uploaded image in the conversation attachments directory
-2. Use the `set_avatar` tool with the `image_path` parameter set to the workspace-relative path (e.g. `conversations/<id>/attachments/Dropped Image.png`)
-
-The tool copies the image to the canonical location (`data/avatar/avatar-image.png`) and notifies the app to refresh automatically.
-
-When the user asks to remove, clear, or reset their avatar, use the `remove_avatar` tool. It deletes only the custom image and preserves the native character traits so the character avatar is restored automatically.
-
-When the user asks to see, view, or show their current avatar, use the `get_avatar` tool. It returns the avatar image inline. If no custom image exists but character traits are set, it regenerates the static PNG from traits and returns that.
-
-**Do NOT use `bash`, `cp`, `rm`, or `file_read` for avatar operations** — always use `set_avatar` / `remove_avatar` / `get_avatar` so the app is properly notified and character traits are preserved.
+Tools for managing assistant settings: voice configuration (TTS voice, PTT activation key, conversation timeout), system settings navigation, and in-app settings tab navigation.

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

@@ -87,62 +87,6 @@
       },
       "executor": "tools/navigate-settings-tab.ts",
       "execution_target": "host"
-    },
-    {
-      "name": "set_avatar",
-      "description": "Set the assistant's avatar to an image file. Copies the source image to the canonical avatar location (data/avatar/avatar-image.png), removes any native character avatar files, and notifies the app to refresh. Use this when the user asks to set, change, or update the avatar to a specific image (e.g. from a conversation attachment).",
-      "category": "system",
-      "risk": "low",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "image_path": {
-            "type": "string",
-            "description": "Path to the image file. Can be absolute or relative to the workspace directory (e.g. 'conversations/<id>/attachments/Dropped Image.png')."
-          },
-          "activity": {
-            "type": "string",
-            "description": "Brief non-technical explanation of what you are doing, shown to the user as a status update."
-          }
-        },
-        "required": ["image_path"]
-      },
-      "executor": "tools/avatar-update.ts",
-      "execution_target": "host"
-    },
-    {
-      "name": "remove_avatar",
-      "description": "Remove the custom avatar image and restore the native character avatar. Only deletes the custom image — preserves character traits so the character avatar is automatically restored. Use this when the user asks to remove, clear, or reset their avatar.",
-      "category": "system",
-      "risk": "low",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "activity": {
-            "type": "string",
-            "description": "Brief non-technical explanation of what you are doing, shown to the user as a status update."
-          }
-        }
-      },
-      "executor": "tools/avatar-remove.ts",
-      "execution_target": "host"
-    },
-    {
-      "name": "get_avatar",
-      "description": "Read and return the current avatar image so the user can see it. Use this when the user asks to see, view, or show their avatar. Returns the image inline — do NOT copy the file or use bash commands.",
-      "category": "system",
-      "risk": "low",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "activity": {
-            "type": "string",
-            "description": "Brief non-technical explanation of what you are doing, shown to the user as a status update."
-          }
-        }
-      },
-      "executor": "tools/avatar-get.ts",
-      "execution_target": "host"
     }
   ]
 }

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

@@ -26,6 +26,8 @@ Subagents follow this status flow: `pending` -> `running` -> `completed` / `fail
 
 Each subagent is spawned with a role that determines its tool access. Choose the most restrictive role that can accomplish the task.
 
+`recall` is local information search across memory, the personal knowledge base, past conversations, and workspace files. Use it when a subagent needs prior context that is not already in the prompt.
+
 | Role | Tools | When to use |
 |---|---|---|
 | `general` | Full tool access | Task genuinely needs unrestricted capabilities (rare -- prefer a specialized role) |

package/src/config/bundled-tool-registry.ts

@@ -15,8 +15,10 @@
 import type { SkillToolScript } from "../tools/skills/script-contract.js";
 // ── acp ────────────────────────────────────────────────────────────────────────
 import * as acpAbort from "./bundled-skills/acp/tools/acp-abort.js";
+import * as acpListAgents from "./bundled-skills/acp/tools/acp-list-agents.js";
 import * as acpSpawn from "./bundled-skills/acp/tools/acp-spawn.js";
 import * as acpStatus from "./bundled-skills/acp/tools/acp-status.js";
+import * as acpSteer from "./bundled-skills/acp/tools/acp-steer.js";
 // ── app-builder ────────────────────────────────────────────────────────────────
 import * as appCreate from "./bundled-skills/app-builder/tools/app-create.js";
 import * as appDelete from "./bundled-skills/app-builder/tools/app-delete.js";
@@ -39,8 +41,6 @@ import * as contactMerge from "./bundled-skills/contacts/tools/contact-merge.js"
 import * as contactSearch from "./bundled-skills/contacts/tools/contact-search.js";
 import * as contactUpsert from "./bundled-skills/contacts/tools/contact-upsert.js";
 import * as googleContacts from "./bundled-skills/contacts/tools/google-contacts.js";
-// ── conversations ──────────────────────────────────────────────────────────────
-import * as renameConversation from "./bundled-skills/conversations/tools/rename-conversation.js";
 // ── document ───────────────────────────────────────────────────────────────────
 import * as documentCreate from "./bundled-skills/document/tools/document-create.js";
 import * as documentUpdate from "./bundled-skills/document/tools/document-update.js";
@@ -68,8 +68,6 @@ import * as messagingRead from "./bundled-skills/messaging/tools/messaging-read.
 import * as messagingSearch from "./bundled-skills/messaging/tools/messaging-search.js";
 import * as messagingSend from "./bundled-skills/messaging/tools/messaging-send.js";
 import * as messagingSenderDigest from "./bundled-skills/messaging/tools/messaging-sender-digest.js";
-// ── notifications ──────────────────────────────────────────────────────────────
-import * as sendNotification from "./bundled-skills/notifications/tools/send-notification.js";
 // ── phone-calls ────────────────────────────────────────────────────────────────
 import * as callEnd from "./bundled-skills/phone-calls/tools/call-end.js";
 import * as callStart from "./bundled-skills/phone-calls/tools/call-start.js";
@@ -84,8 +82,6 @@ import * as scheduleCreate from "./bundled-skills/schedule/tools/schedule-create
 import * as scheduleDelete from "./bundled-skills/schedule/tools/schedule-delete.js";
 import * as scheduleList from "./bundled-skills/schedule/tools/schedule-list.js";
 import * as scheduleUpdate from "./bundled-skills/schedule/tools/schedule-update.js";
-// ── screen-watch ───────────────────────────────────────────────────────────────
-import * as startScreenWatch from "./bundled-skills/screen-watch/tools/start-screen-watch.js";
 // ── sequences ──────────────────────────────────────────────────────────────────
 import * as sequenceAnalytics from "./bundled-skills/sequences/tools/sequence-analytics.js";
 import * as sequenceCreate from "./bundled-skills/sequences/tools/sequence-create.js";
@@ -97,9 +93,6 @@ import * as sequenceImport from "./bundled-skills/sequences/tools/sequence-impor
 import * as sequenceList from "./bundled-skills/sequences/tools/sequence-list.js";
 import * as sequenceUpdate from "./bundled-skills/sequences/tools/sequence-update.js";
 // ── settings ───────────────────────────────────────────────────────────────────
-import * as avatarGet from "./bundled-skills/settings/tools/avatar-get.js";
-import * as avatarRemove from "./bundled-skills/settings/tools/avatar-remove.js";
-import * as avatarUpdate from "./bundled-skills/settings/tools/avatar-update.js";
 import * as navigateSettingsTab from "./bundled-skills/settings/tools/navigate-settings-tab.js";
 import * as openSystemSettings from "./bundled-skills/settings/tools/open-system-settings.js";
 import * as voiceConfigUpdate from "./bundled-skills/settings/tools/voice-config-update.js";
@@ -123,6 +116,8 @@ export const bundledToolRegistry = new Map<string, SkillToolScript>([
   ["acp:tools/acp-spawn.ts", acpSpawn],
   ["acp:tools/acp-status.ts", acpStatus],
   ["acp:tools/acp-abort.ts", acpAbort],
+  ["acp:tools/acp-steer.ts", acpSteer],
+  ["acp:tools/acp-list-agents.ts", acpListAgents],
 
   // app-builder
   ["app-builder:tools/app-create.ts", appCreate],
@@ -152,9 +147,6 @@ export const bundledToolRegistry = new Map<string, SkillToolScript>([
   ["contacts:tools/contact-merge.ts", contactMerge],
   ["contacts:tools/google-contacts.ts", googleContacts],
 
-  // conversations
-  ["conversations:tools/rename-conversation.ts", renameConversation],
-
   // document
   ["document:tools/document-create.ts", documentCreate],
   ["document:tools/document-update.ts", documentUpdate],
@@ -190,9 +182,6 @@ export const bundledToolRegistry = new Map<string, SkillToolScript>([
   ["messaging:tools/messaging-sender-digest.ts", messagingSenderDigest],
   ["messaging:tools/messaging-archive-by-sender.ts", messagingArchiveBySender],
 
-  // notifications
-  ["notifications:tools/send-notification.ts", sendNotification],
-
   // phone-calls
   ["phone-calls:tools/call-start.ts", callStart],
   ["phone-calls:tools/call-status.ts", callStatus],
@@ -210,9 +199,6 @@ export const bundledToolRegistry = new Map<string, SkillToolScript>([
   ["schedule:tools/schedule-update.ts", scheduleUpdate],
   ["schedule:tools/schedule-delete.ts", scheduleDelete],
 
-  // screen-watch
-  ["screen-watch:tools/start-screen-watch.ts", startScreenWatch],
-
   // sequences
   ["sequences:tools/sequence-create.ts", sequenceCreate],
   ["sequences:tools/sequence-list.ts", sequenceList],
@@ -228,9 +214,6 @@ export const bundledToolRegistry = new Map<string, SkillToolScript>([
   ["settings:tools/voice-config-update.ts", voiceConfigUpdate],
   ["settings:tools/open-system-settings.ts", openSystemSettings],
   ["settings:tools/navigate-settings-tab.ts", navigateSettingsTab],
-  ["settings:tools/avatar-update.ts", avatarUpdate],
-  ["settings:tools/avatar-remove.ts", avatarRemove],
-  ["settings:tools/avatar-get.ts", avatarGet],
 
   // skill-management
   ["skill-management:tools/scaffold-managed.ts", scaffoldManaged],

package/src/config/env.ts

@@ -48,7 +48,7 @@ function int(name: string, fallback?: number): number | undefined {
 
 const DEFAULT_GATEWAY_PORT = 7830;
 
-export function getGatewayPort(): number {
+function getGatewayPort(): number {
   return int("GATEWAY_PORT", DEFAULT_GATEWAY_PORT);
 }
 
@@ -87,10 +87,6 @@ export function getRuntimeHttpHost(): string {
   return str("RUNTIME_HTTP_HOST") || "127.0.0.1";
 }
 
-export function getRuntimeGatewayOriginSecret(): string | undefined {
-  return str("RUNTIME_GATEWAY_ORIGIN_SECRET");
-}
-
 /**
  * True when HTTP API auth is disabled via DISABLE_HTTP_AUTH=true AND the
  * safety gate VELLUM_UNSAFE_AUTH_BYPASS=1 is also set. Without the safety
@@ -221,11 +217,14 @@ export function setPlatformAssistantId(value: string | undefined): void {
 }
 
 /**
- * PLATFORM_ASSISTANT_ID — UUID of this assistant on the platform.
- * Required for registering callback routes when containerized.
+ * Platform assistant ID — UUID of this assistant on the platform.
+ *
+ * Resolved from the in-memory override (populated by providers-setup
+ * rehydration from the credential store at daemon startup, or by
+ * secret-routes when the platform pushes the value).
  */
 export function getPlatformAssistantId(): string {
-  return str("PLATFORM_ASSISTANT_ID") ?? _platformAssistantIdOverride ?? "";
+  return _platformAssistantIdOverride ?? "";
 }
 
 let _platformOrganizationIdOverride: string | undefined;

package/src/config/feature-flag-registry.json

@@ -169,14 +169,6 @@
       "description": "Show the Embedding service card in Models & Services settings",
       "defaultEnabled": false
     },
-    {
-      "id": "settings-schedules",
-      "scope": "assistant",
-      "key": "settings-schedules",
-      "label": "Schedules Settings Tab",
-      "description": "Show the Schedules tab in Settings for viewing and managing schedules",
-      "defaultEnabled": false
-    },
     {
       "id": "multi-platform-assistant",
       "scope": "assistant",
@@ -281,14 +273,6 @@
       "description": "Enable teleport UI in General settings for moving assistants between hosting environments",
       "defaultEnabled": false
     },
-    {
-      "id": "permission-controls-v2",
-      "scope": "assistant",
-      "key": "permission-controls-v2",
-      "label": "Permission Controls V2",
-      "description": "Replace risk-level permission system with two independent controls: 'Ask before acting' (LLM behavior toggle) and 'Host access' (system-enforced gate)",
-      "defaultEnabled": false
-    },
     {
       "id": "apple-container",
       "scope": "macos",
@@ -327,7 +311,7 @@
       "key": "onboarding-pre-chat",
       "label": "Pre-Chat Onboarding Flow",
       "description": "Gates the 3-screen pre-chat onboarding flow (tools, tasks/tone, name exchange) shown before the first conversation",
-      "defaultEnabled": false
+      "defaultEnabled": true
     },
     {
       "id": "home-tab",
@@ -376,6 +360,30 @@
       "label": "Message Height Cache",
       "description": "Swap the transcript's LazyVStack for a plain VStack so scrollContentHeight is the true sum of row heights (no LazyVStack estimator drift). Row frames are not pinned — the earlier frame-pinning approach was removed because it caused overlap when rows grew past their first measurement (streaming, expanding thinking blocks). Tradeoff: eager layout — every row measures up-front, which can stall for many seconds to minutes on very long conversations.",
       "defaultEnabled": true
+    },
+    {
+      "id": "compaction-playground",
+      "scope": "assistant",
+      "key": "compaction-playground",
+      "label": "Compaction Playground",
+      "description": "Expose the developer-only Compaction Playground tab in macOS Settings and enable the /playground/* HTTP endpoints for exercising compaction conditions. Dev-only; default off.",
+      "defaultEnabled": false
+    },
+    {
+      "id": "memory-v2-enabled",
+      "scope": "assistant",
+      "key": "memory-v2-enabled",
+      "label": "Memory v2 (concept-page activation model)",
+      "description": "Enables the v2 memory subsystem: prose concept pages with bidirectional edges, activation-based retrieval, and hourly LLM-driven consolidation. v1 graph + PKB stays write-active until cutover.",
+      "defaultEnabled": false
+    },
+    {
+      "id": "inference-profiles",
+      "scope": "assistant",
+      "key": "inference-profiles",
+      "label": "Inference Profiles",
+      "description": "Show inference profile picker in chat, active profile dropdown, Manage Profiles button, and per-task overrides link in Settings",
+      "defaultEnabled": false
     }
   ]
 }