@vellumai/assistant 0.8.3 → 0.8.5

package/src/cli/commands/notifications.ts

@@ -8,6 +8,7 @@ import {
 import { registerCommand } from "../lib/register-command.js";
 import { log } from "../logger.js";
 import { shouldOutputJson, writeOutput } from "../output.js";
+import { tryResolveConversationId } from "../utils/conversation-id.js";
 
 // ---------------------------------------------------------------------------
 // Command registration
@@ -248,8 +249,6 @@ Examples:
                 }
               }
 
-              const sourceContextId = opts.sessionId ?? `cli-${Date.now()}`;
-
               // Validate --conversation-id if provided
               const conversationId = opts.conversationId?.trim();
               if (opts.conversationId != null && !conversationId) {
@@ -261,6 +260,26 @@ Examples:
                 return;
               }
 
+              // Picks up __CONVERSATION_ID / __SKILL_CONTEXT_JSON env vars
+              // so deferred-emit can buffer notifications when called from a
+              // background job that hasn't confirmed success yet.
+              const originatingConversationId = tryResolveConversationId();
+
+              // The signal's `sourceContextId` doubles as the home-feed's
+              // navigation target — `resolveHomeFeedMirror` looks it up via
+              // `getConversation()` and only renders a "Go to Convo" button
+              // when it resolves to a real row. Prefer the conversation the
+              // CLI was invoked from (env-derived) so notifications emitted
+              // by background jobs and skills link back to their producing
+              // convo; an explicit --session-id still wins to preserve
+              // caller intent, and --conversation-id is the last resort
+              // before the unresolvable `cli-<ts>` sentinel.
+              const sourceContextId =
+                opts.sessionId ??
+                originatingConversationId ??
+                conversationId ??
+                `cli-${Date.now()}`;
+
               const result = await cliIpcCall<{
                 signalId: string;
                 dispatched: boolean;
@@ -289,6 +308,9 @@ Examples:
                   ...(conversationId
                     ? { conversationAffinityHint: { vellum: conversationId } }
                     : {}),
+                  ...(originatingConversationId
+                    ? { originatingConversationId }
+                    : {}),
                   throwOnError: true,
                 },
               });

package/src/cli/program.ts

@@ -34,6 +34,7 @@ import { registerInferenceCommand } from "./commands/inference.js";
 import { registerKeysCommand } from "./commands/keys.js";
 import { registerMcpCommand } from "./commands/mcp.js";
 import { registerMemoryV2Command } from "./commands/memory-v2.js";
+import { registerMemoryV3Command } from "./commands/memory-v3.js";
 import { registerNotificationsCommand } from "./commands/notifications.js";
 import { registerOAuthCommand } from "./commands/oauth/index.js";
 import { registerPendingCommand } from "./commands/pending.js";
@@ -129,6 +130,7 @@ Examples:
   registerKeysCommand(program);
   registerMcpCommand(program);
   registerMemoryV2Command(program);
+  registerMemoryV3Command(program);
   registerNotificationsCommand(program);
   registerOAuthCommand(program);
   registerPendingCommand(program);

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

@@ -3,12 +3,11 @@
  *   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
+ *   4. `undefined`
  */
-export function resolveConversationId(opts: {
-  explicit?: string;
-  failureHelp: string;
-}): string {
+export function tryResolveConversationId(
+  opts: { explicit?: string } = {},
+): string | undefined {
   if (opts.explicit) return opts.explicit;
 
   const contextJson = process.env.__SKILL_CONTEXT_JSON;
@@ -26,5 +25,18 @@ export function resolveConversationId(opts: {
   const envConvId = process.env.__CONVERSATION_ID;
   if (envConvId && typeof envConvId === "string") return envConvId;
 
+  return undefined;
+}
+
+/**
+ * Same precedence as `tryResolveConversationId` but throws with the
+ * provided `failureHelp` when no source produces a value.
+ */
+export function resolveConversationId(opts: {
+  explicit?: string;
+  failureHelp: string;
+}): string {
+  const resolved = tryResolveConversationId({ explicit: opts.explicit });
+  if (resolved) return resolved;
   throw new Error(opts.failureHelp);
 }

package/src/config/assistant-feature-flags.ts

@@ -7,7 +7,7 @@
  * (in priority order):
  *   1. Override values from the gateway IPC socket
  *   2. defaults registry `defaultEnabled`         (for declared keys)
- *   3. `true`                                     (for undeclared keys)
+ *   3. `false`                                    (for undeclared keys)
  *
  * Key format:
  *   Canonical:  simple kebab-case string (e.g., "browser", "ces-tools")
@@ -172,8 +172,8 @@ const DEFAULT_INIT_RETRY_BACKOFFS_MS: readonly number[] = [
  * Retries the gateway IPC fetch on empty/failed results — the gateway
  * may not have bound its IPC socket yet when the daemon races ahead at
  * startup. After exhausting retries, the cache is left unset so
- * subsequent sync calls return an empty override map (registry defaults
- * only).
+ * subsequent sync calls return an empty override map (registry defaults for
+ * declared flags, fail-closed for undeclared flags).
  *
  * Pass `retryBackoffsMs: []` to disable retries (used by unit tests that
  * intentionally simulate an unreachable gateway and want immediate
@@ -229,12 +229,11 @@ export async function initFeatureFlagOverrides(options?: {
 
   // Exhausted retries — leave cache unset so loadOverrides() returns an
   // empty map on subsequent sync reads. Flag checks fall through to the
-  // registry default (`defaultEnabled`), which biases toward off for
-  // newer assistant-scope flags.
+  // registry default (`defaultEnabled`) or the fail-closed undeclared default.
   if (backoffs.length > 0) {
     log.warn(
       { attempts: backoffs.length + 1 },
-      "Feature flag overrides empty after all retries; falling back to registry defaults",
+      "Feature flag overrides empty after all retries; falling back to registry defaults and fail-closed undeclared flags",
     );
   }
 }
@@ -260,6 +259,19 @@ export function clearFeatureFlagOverridesCache(): void {
   cachedOverridesFromGateway = false;
 }
 
+/**
+ * Re-fetch feature flag overrides from the gateway.
+ *
+ * Clears the cached overrides and re-runs the gateway IPC fetch without
+ * retries (the gateway is known to be up because it just pushed an event).
+ * Called by the gateway flag listener when a `feature_flags_changed` event
+ * arrives.
+ */
+export async function refreshOverridesFromGateway(): Promise<void> {
+  clearFeatureFlagOverridesCache();
+  await initFeatureFlagOverrides({ retryBackoffsMs: [] });
+}
+
 /**
  * Directly inject override values into the module-level cache.
  *
@@ -287,7 +299,7 @@ export function _setOverridesForTesting(
  *      values, which the gateway merges server-side: persisted > remote >
  *      registry)
  *   2. Registry `defaultEnabled` (for declared assistant-scope keys)
- *   3. `true` (for undeclared keys with no override)
+ *   3. `false` (for undeclared keys with no override)
  */
 export function isAssistantFeatureFlagEnabled(
   key: string,
@@ -304,6 +316,6 @@ export function isAssistantFeatureFlagEnabled(
   // 2. For declared keys, use the registry default.
   if (declared) return declared.defaultEnabled;
 
-  // 3. Undeclared keys with no override default to enabled.
-  return true;
+  // 3. Undeclared keys with no override fail closed.
+  return false;
 }

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

@@ -127,10 +127,10 @@ App building is design-heavy judgment work — color palettes, layout decisions,
 assistant inference session list
 ```
 
-If no session is active, check the current default profile:
+If no session is active, check the current active profile:
 
 ```
-assistant config get llm.default.profile
+assistant config get llm.activeProfile
 ```
 
 If the profile is already `quality-optimized`, skip the rest of this step and proceed to Step 1.

package/src/config/bundled-skills/document-editor/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: document-editor
+description: Rich text document editor with collaborative editing tools — create, read, update, and annotate documents
+compatibility: "Designed for Vellum personal assistants"
+metadata:
+  emoji: "📄"
+  vellum:
+    display-name: "Document Editor"
+    activation-hints:
+      - "User asks to write, draft, or collaborate on long-form content — use the document editor for a better editing experience"
+      - "When content will be iterated on, reviewed, or exported, prefer the document editor over inline markdown"
+      - "When a file attachment contains a draft or document the user wants to iterate on, open it in the editor"
+---
+
+Create and edit long-form documents using the built-in rich text editor. Documents open in workspace mode with chat docked to the side.
+
+## Tools
+
+- **document_open** - Opens an existing document in the editor panel by `surface_id`. Use this when a document exists but isn't visible in the editor — for example after the user switches devices, refreshes the page, or when the editor panel was closed. Fetches the document from storage and sends it to the client.
+- **document_create** - Opens a new document editor with an optional title and initial Markdown content. Returns a `surface_id` for subsequent updates.
+- **document_update** - Updates content in an open document editor by `surface_id`. Supports `replace` (overwrite) and `append` (add to end) modes.
+- **document_read** - Reads the current content of a document by `surface_id` when it belongs to the current conversation, or when the current actor is the guardian/local user. Use to verify content before editing.
+- **document_list** - Lists documents. Without `query`, lists the current conversation's documents. With `query`, searches by title; guardian/local users can search across conversations, while other actors are scoped to the current conversation.
+- **document_find** - Searches a document for text or regex patterns. Returns matching lines with line numbers, match positions, and matched text.
+- **document_replace_text** - Targeted find-and-replace within a document. Supports literal and regex patterns (with backreferences). Optionally limit the number of replacements.
+- **document_delete** - Deletes a document by `surface_id`. Use to clean up unwanted documents.
+
+## Retrieving existing documents
+
+When the user asks to see, open, or pull up a document:
+
+1. Check the `<active_documents>` block in your context — it lists all documents in this conversation with their `surface_id` and title.
+2. If the document is NOT in `<active_documents>`, call `document_list` with a `query` matching the document title. For guardian/local users, this searches across previous conversations and sessions.
+3. Once you have the `surface_id`, call `document_open` to open the editor panel. This both surfaces the editor on the client and returns the document content. If the user only needs the text (not the editor), use `document_read` instead.
+
+**Never** search the filesystem, conversation history, or archives to find a document. Always use `document_list` with a `query`.
+
+**If the user says they can't see a document you know exists** (e.g. after switching from macOS to web, or after a page refresh), call `document_open` with the `surface_id` to re-surface the editor panel on their current client.
+
+## Creating a new document
+
+1. **Create the document**: Call `document_create` with a title (inferred from the request). Call the tool immediately, not after conversational preamble.
+2. **Write content in Markdown**: Use proper structure (`#` for titles, `##` for sections), **bold**, _italic_, code blocks, tables, lists, blockquotes as appropriate.
+3. **CRITICAL - Stream content in chunks**: Call `document_update` MULTIPLE times, not just once. Break content into logical chunks (paragraphs, sections, or every 200-300 words). Call `document_update` with `mode: "append"` for EACH chunk separately. The user experiences real-time content appearing as you write.
+
+## Editing an existing document
+
+When the user requests changes to a document:
+
+1. Find the `surface_id` from the `<active_documents>` context block.
+2. Use `document_update` with the existing `surface_id` — do NOT call `document_create` again.
+3. **Choose the right editing tool:**
+   - `document_update` with `mode: "append"` — adding new content to the end.
+   - `document_update` with `mode: "replace"` — ONLY for full rewrites where the majority of the document is changing.
+   - `document_find` + `document_replace_text` — **for everything else**. Fixing typos, renaming terms, swapping sections, reordering content, adjusting formatting, or any edit that touches only part of the document. This is the default choice for edits. It avoids rewriting the entire document and eliminates the risk of accidentally dropping content.
+4. **Do NOT use `document_update` with `mode: "replace"` for targeted edits.** Rewriting the entire document to change a few words or rearrange sections is wasteful and error-prone.
+
+## Find & Replace
+
+Use `document_find` and `document_replace_text` for surgical edits that target specific text patterns without rewriting the entire document.
+
+### document_find
+
+Search a document for literal text or regex patterns. Parameters:
+
+- `surface_id` (required) — the document to search
+- `query` (required) — the search string or regex pattern
+- `regex` (optional, default `false`) — treat `query` as a regular expression
+- `case_sensitive` (optional, default `false`) — match case exactly
+
+Returns a list of matches with line numbers, line content, match positions, and matched text. Use this to preview what will be affected before making replacements.
+
+### document_replace_text
+
+Targeted find-and-replace within a document. Parameters:
+
+- `surface_id` (required) — the document to modify
+- `find` (required) — the search string or regex pattern
+- `replace` (required) — the replacement string (supports `$1`, `$2` backreferences when `regex` is `true`)
+- `regex` (optional, default `false`) — treat `find` as a regular expression
+- `case_sensitive` (optional, default `false`) — match case exactly
+- `max_replacements` (optional) — limit the number of replacements made
+
+Returns the number of replacements made and whether the content changed.
+
+### Workflow
+
+1. Call `document_find` to preview matches and confirm the pattern is correct.
+2. Call `document_replace_text` to apply the changes.
+
+**Examples:**
+
+- **Fix a recurring typo**: Find `"recieve"`, replace with `"receive"`.
+- **Rename a term throughout**: Find `"widget"` (case-insensitive), replace with `"component"`.
+- **Reformat dates with regex**: Find `(\d{2})/(\d{2})/(\d{4})` with `regex: true`, replace with `$3-$1-$2` to convert `MM/DD/YYYY` to `YYYY-MM-DD`.
+- **Swap or reorder sections**: Use `document_read` to get the content, identify the sections to swap, then call `document_replace_text` to replace the first section with the second and vice versa. For complex rearrangements, use multiple `document_replace_text` calls with `max_replacements: 1`.
+
+## Comments
+
+Users can leave inline comments on documents. Open comments are surfaced in a `<document_comments>` context block so you can see pending feedback.
+
+- **comment_list** — Lists open comments on a document by `surface_id`. Use this to check for feedback before or after editing, especially when the user asks you to address comments.
+- **comment_resolve** — Marks a comment as resolved by `comment_id`. Use this after you have addressed the feedback in the document content. Always edit the document first, then resolve the comment.
+- **comment_reply** — Posts a reply to an existing comment by `comment_id`. Use this to ask clarifying questions or explain why you made (or declined) a change before resolving.
+
+### Addressing comments workflow
+
+1. Read the `<document_comments>` block or call `comment_list` to see open comments.
+2. For each comment, edit the document to address the feedback.
+3. Call `comment_resolve` on comments you have addressed.
+4. If a comment is ambiguous, call `comment_reply` to ask for clarification instead of guessing.
+
+## Anti-Patterns
+
+- **Don't use `app_create` for blog posts, articles, or written content.** Use `document_create` — apps are for interactive content with state/data.
+- **Don't output the full content in chat.** The content goes in the document editor, not in the chat response. Acknowledge what you're doing and stream to the editor.
+- **Don't wait to generate everything before sending.** Stream content in chunks via `document_update` with `mode: "append"` so users see progress in real time.
+
+## Usage Notes
+
+- The `mode` parameter on `document_update` defaults to `append`.
+- Documents are automatically saved and accessible via the Generated panel.
+- Users can manually edit documents at any time.
+- Write in clear, engaging prose. Use active voice, vary sentence structure, and break content into logical sections with descriptive headings.

package/src/config/bundled-skills/document-editor/TOOLS.json

@@ -0,0 +1,258 @@
+{
+  "version": 1,
+  "tools": [
+    {
+      "name": "document_open",
+      "description": "Open an existing document in the editor panel. Use this when the user asks to see or pull up a document that exists but isn't currently visible in the editor — for example after switching devices, refreshing, or when the editor panel was closed.",
+      "category": "document-editor",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "surface_id": {
+            "type": "string",
+            "description": "The ID of the document to open"
+          }
+        },
+        "required": ["surface_id"]
+      },
+      "executor": "tools/document-open.ts",
+      "execution_target": "host"
+    },
+    {
+      "name": "document_create",
+      "description": "Create a new long-form document with a rich text editor. Use this when the user asks to write a blog post, article, or any long-form content. The editor opens in workspace mode with chat docked to the side.",
+      "category": "document-editor",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "title": {
+            "type": "string",
+            "description": "Initial title for the document (optional, can be updated later)"
+          },
+          "initial_content": {
+            "type": "string",
+            "description": "Initial Markdown content to populate the editor (optional)"
+          }
+        }
+      },
+      "executor": "tools/document-create.ts",
+      "execution_target": "host"
+    },
+    {
+      "name": "document_update",
+      "description": "Update content in an open document editor. Use this to stream generated content or apply edits.",
+      "category": "document-editor",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "surface_id": {
+            "type": "string",
+            "description": "The ID of the document surface to update"
+          },
+          "content": {
+            "type": "string",
+            "description": "Markdown content to set or append"
+          },
+          "mode": {
+            "type": "string",
+            "enum": ["replace", "append"],
+            "description": "Whether to replace all content or append to the end. Defaults to append."
+          }
+        },
+        "required": ["surface_id", "content"]
+      },
+      "executor": "tools/document-update.ts",
+      "execution_target": "host"
+    },
+    {
+      "name": "document_read",
+      "description": "Read the current content of a document by its surface_id when it belongs to the current conversation, or when the current actor is the guardian/local user. Use this to verify document state before making edits.",
+      "category": "document-editor",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "surface_id": {
+            "type": "string",
+            "description": "The ID of the document to read"
+          }
+        },
+        "required": ["surface_id"]
+      },
+      "executor": "tools/document-read.ts",
+      "execution_target": "host"
+    },
+    {
+      "name": "document_list",
+      "description": "List documents. Without a query, lists documents in the current conversation. With a query, searches documents by title; guardian/local users can search across conversations, while other actors are scoped to the current conversation.",
+      "category": "document-editor",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "query": {
+            "type": "string",
+            "description": "Search documents by title. Omit to list only the current conversation's documents."
+          }
+        }
+      },
+      "executor": "tools/document-list.ts",
+      "execution_target": "host"
+    },
+    {
+      "name": "document_delete",
+      "description": "Delete a document by its surface_id.",
+      "category": "document-editor",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "surface_id": {
+            "type": "string",
+            "description": "The ID of the document to delete"
+          }
+        },
+        "required": ["surface_id"]
+      },
+      "executor": "tools/document-delete.ts",
+      "execution_target": "host"
+    },
+    {
+      "name": "document_find",
+      "description": "Search for text or a regex pattern within a document. Returns matching lines with line numbers and context — like grep. Use this to locate specific content before making targeted edits with document_replace_text.",
+      "category": "document-editor",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "surface_id": {
+            "type": "string",
+            "description": "The document surface ID"
+          },
+          "query": {
+            "type": "string",
+            "description": "Text or regex pattern to search for"
+          },
+          "regex": {
+            "type": "boolean",
+            "description": "Treat query as a regex pattern. Defaults to false (literal match)."
+          },
+          "case_sensitive": {
+            "type": "boolean",
+            "description": "Match case-sensitively. Defaults to false."
+          }
+        },
+        "required": ["surface_id", "query"]
+      },
+      "executor": "tools/document-find.ts",
+      "execution_target": "host"
+    },
+    {
+      "name": "document_replace_text",
+      "description": "Find and replace text within a document — like sed. Performs targeted replacements without rewriting the entire document. Supports literal text and regex patterns. Use document_find first to preview what will be matched.",
+      "category": "document-editor",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "surface_id": {
+            "type": "string",
+            "description": "The document surface ID"
+          },
+          "find": {
+            "type": "string",
+            "description": "Text or regex pattern to find"
+          },
+          "replace": {
+            "type": "string",
+            "description": "Replacement text. When using regex, supports backreferences ($1, $2, etc.)."
+          },
+          "regex": {
+            "type": "boolean",
+            "description": "Treat find as a regex pattern. Defaults to false (literal match)."
+          },
+          "case_sensitive": {
+            "type": "boolean",
+            "description": "Match case-sensitively. Defaults to false."
+          },
+          "max_replacements": {
+            "type": "number",
+            "description": "Maximum number of replacements to make. Omit to replace all occurrences."
+          }
+        },
+        "required": ["surface_id", "find", "replace"]
+      },
+      "executor": "tools/document-replace-text.ts",
+      "execution_target": "host"
+    },
+    {
+      "name": "comment_list",
+      "description": "List open comments on a document. Returns all unresolved comments with their content, anchor text, and thread context so you can address user feedback.",
+      "category": "document-editor",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "surface_id": {
+            "type": "string",
+            "description": "The document surface ID"
+          }
+        },
+        "required": ["surface_id"]
+      },
+      "executor": "tools/comment-list.ts",
+      "execution_target": "host"
+    },
+    {
+      "name": "comment_resolve",
+      "description": "Mark a comment as resolved after you have addressed the feedback. Use this after editing the document to satisfy the comment.",
+      "category": "document-editor",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "surface_id": {
+            "type": "string",
+            "description": "The document surface ID"
+          },
+          "comment_id": {
+            "type": "string",
+            "description": "The comment ID to resolve"
+          }
+        },
+        "required": ["surface_id", "comment_id"]
+      },
+      "executor": "tools/comment-resolve.ts",
+      "execution_target": "host"
+    },
+    {
+      "name": "comment_reply",
+      "description": "Reply to a comment thread. Use this to ask clarifying questions or explain your approach before or after making changes.",
+      "category": "document-editor",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "surface_id": {
+            "type": "string",
+            "description": "The document surface ID"
+          },
+          "comment_id": {
+            "type": "string",
+            "description": "The parent comment ID to reply to"
+          },
+          "content": {
+            "type": "string",
+            "description": "Reply text"
+          }
+        },
+        "required": ["surface_id", "comment_id", "content"]
+      },
+      "executor": "tools/comment-reply.ts",
+      "execution_target": "host"
+    }
+  ]
+}

package/src/config/bundled-skills/document-editor/tools/comment-list.ts

@@ -0,0 +1,12 @@
+import { executeCommentList } from "../../../../tools/document/document-comment-tool.js";
+import type {
+  ToolContext,
+  ToolExecutionResult,
+} from "../../../../tools/types.js";
+
+export async function run(
+  input: Record<string, unknown>,
+  context: ToolContext,
+): Promise<ToolExecutionResult> {
+  return executeCommentList(input, context);
+}

package/src/config/bundled-skills/document-editor/tools/comment-reply.ts

@@ -0,0 +1,12 @@
+import { executeCommentReply } from "../../../../tools/document/document-comment-tool.js";
+import type {
+  ToolContext,
+  ToolExecutionResult,
+} from "../../../../tools/types.js";
+
+export async function run(
+  input: Record<string, unknown>,
+  context: ToolContext,
+): Promise<ToolExecutionResult> {
+  return executeCommentReply(input, context);
+}

package/src/config/bundled-skills/document-editor/tools/comment-resolve.ts

@@ -0,0 +1,12 @@
+import { executeCommentResolve } from "../../../../tools/document/document-comment-tool.js";
+import type {
+  ToolContext,
+  ToolExecutionResult,
+} from "../../../../tools/types.js";
+
+export async function run(
+  input: Record<string, unknown>,
+  context: ToolContext,
+): Promise<ToolExecutionResult> {
+  return executeCommentResolve(input, context);
+}

package/src/config/bundled-skills/document-editor/tools/document-find.ts

@@ -0,0 +1,12 @@
+import { executeDocumentFind } from "../../../../tools/document/document-tool.js";
+import type {
+  ToolContext,
+  ToolExecutionResult,
+} from "../../../../tools/types.js";
+
+export async function run(
+  input: Record<string, unknown>,
+  context: ToolContext,
+): Promise<ToolExecutionResult> {
+  return executeDocumentFind(input, context);
+}

package/src/config/bundled-skills/document-editor/tools/document-open.ts

@@ -0,0 +1,12 @@
+import { executeDocumentOpen } from "../../../../tools/document/document-tool.js";
+import type {
+  ToolContext,
+  ToolExecutionResult,
+} from "../../../../tools/types.js";
+
+export async function run(
+  input: Record<string, unknown>,
+  context: ToolContext,
+): Promise<ToolExecutionResult> {
+  return executeDocumentOpen(input, context);
+}

package/src/config/bundled-skills/document-editor/tools/document-replace-text.ts

@@ -0,0 +1,12 @@
+import { executeDocumentReplaceText } from "../../../../tools/document/document-tool.js";
+import type {
+  ToolContext,
+  ToolExecutionResult,
+} from "../../../../tools/types.js";
+
+export async function run(
+  input: Record<string, unknown>,
+  context: ToolContext,
+): Promise<ToolExecutionResult> {
+  return executeDocumentReplaceText(input, context);
+}

package/src/config/bundled-skills/image-studio/SKILL.md

@@ -37,3 +37,7 @@ You are an image generation assistant. When the user asks you to create or edit
 - When editing images, clearly describe what changes you want made to the source image.
 - Use the `variants` parameter (1-4) to generate multiple options and pick the best one.
 - If no API key is configured for the selected model's provider (Gemini or OpenAI), the tool will return an error - ask the user to set one up.
+
+## Error handling
+
+When image generation fails, report the error to the user as-is. **Do not** attempt to fix the error by changing service configuration (e.g. switching between "managed" and "your-own" mode, or changing the provider/model). Service configuration changes should only be made at the user's explicit request via Settings.