@vellumai/assistant 0.4.41 → 0.4.43

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

@@ -127,13 +127,9 @@ export function isAssistantFeatureFlagEnabled(
   const defaults = loadDefaultsRegistry();
   const declared = defaults[key];
 
-  // 1. Check canonical section
-  const newValues = (config as AssistantConfigWithFeatureFlags)
-    .assistantFeatureFlagValues;
-  if (newValues) {
-    const explicit = newValues[key];
-    if (typeof explicit === "boolean") return explicit;
-  }
+  // 1. Check config overrides
+  const explicit = config.assistantFeatureFlagValues?.[key];
+  if (typeof explicit === "boolean") return explicit;
 
   // 2. For declared keys, use the registry default
   if (declared) {
@@ -157,11 +153,3 @@ export function getAssistantFeatureFlagDefaults(): FeatureFlagDefaultsRegistry {
 export function _resetDefaultsCache(): void {
   cachedDefaults = undefined;
 }
-
-// ---------------------------------------------------------------------------
-// Internal type augmentation for the new config field
-// ---------------------------------------------------------------------------
-
-interface AssistantConfigWithFeatureFlags extends AssistantConfig {
-  assistantFeatureFlagValues?: Record<string, boolean>;
-}

package/src/config/bundled-skills/_shared/CLI_RETRIEVAL_PATTERN.md

@@ -1,12 +1,10 @@
 # Bundled Skill CLI Retrieval Pattern
 
-Use this pattern for setup/status reads in bundled skills:
+When running the `assistant` CLI, run it using the `bash` (not `host_bash`) tool.
 
-1. Run Vellum CLI reads through `bash` (not `host_bash`).
-2. Use domain commands (for example `assistant integrations twilio config`) instead of direct gateway `curl`.
-3. Let the CLI handle gateway auth internally; do not instruct manual bearer headers for read paths.
+# Outbound Network Requests
 
-When a skill needs outbound API calls with a stored credential (outside of Vellum CLI reads), use proxied bash:
+When a skill needs outbound API calls with a stored credential (outside of `assistant` CLI reads), use proxied `bash`:
 
 ```yaml
 bash:
@@ -16,4 +14,3 @@ bash:
   command: |
     curl -s https://api.example.com/resource
 ```
-

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

@@ -1,8 +1,8 @@
 ---
-name: "Email CLI Ops"
-description: "Run email operations through a provider-agnostic CLI wrapper"
-user-invocable: true
-metadata: {"vellum": {"emoji": "📬"}}
+name: agentmail
+description: Run email operations through a provider-agnostic CLI wrapper
+compatibility: "Designed for Vellum personal assistants"
+metadata: {"emoji":"📬","vellum":{"display-name":"Email CLI Ops","user-invocable":true}}
 ---
 
 ## How to run

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

@@ -1,8 +1,8 @@
 ---
-name: "Amazon"
-description: "Shop on Amazon and Amazon Fresh using the built-in CLI integration"
-user-invocable: true
-metadata: { "vellum": { "emoji": "\uD83D\uDCE6" } }
+name: amazon
+description: Shop on Amazon and Amazon Fresh using the built-in CLI integration
+compatibility: "Designed for Vellum personal assistants"
+metadata: {"emoji":"📦","vellum":{"display-name":"Amazon","user-invocable":true}}
 ---
 
 You can shop on Amazon (and Amazon Fresh for groceries) for the user using the `assistant amazon` CLI.
@@ -58,12 +58,22 @@ Many Amazon products (clothing, electronics) have variations (size, color, style
 
 Alternatively, run `assistant amazon variations <asin> --json` to list just the variations.
 
+## Session Storage
+
+Session cookies are stored in the encrypted credential store under the key `amazon:session:cookies`. You can inspect the stored session with:
+
+```bash
+assistant credentials inspect amazon:session:cookies
+```
+
+Session capture (`assistant amazon refresh`) and session checks (`assistant amazon status`) use the credential store automatically — no manual file management is needed.
+
 ## Important Behavior
 
+- **Chrome extension relay required.** The Amazon CLI uses `assistant browser chrome relay` internally for browser automation. The Chrome extension must be connected before Amazon commands will work. If a command fails with a connection error, tell the user: "Please open Chrome, click the Vellum extension icon, and click Connect — then I'll retry."
 - **Always confirm before placing order.** Never call `order place` without explicit user approval. Show the cart and total first.
 - **Be proactive.** If the user says "order AA batteries", don't ask clarifying questions upfront — search, find the product, and suggest it. Only ask when you need a choice the user hasn't specified.
 - **Handle expired sessions gracefully.** If any command returns `"error": "session_expired"`, run `assistant amazon refresh --json` to re-capture the session.
-- **Handle extension errors.** If a command fails with a message about the browser extension not being connected, tell the user: "Please open Chrome, click the Vellum extension icon, and click Connect — then I'll retry." Do NOT try to interact with the relay directly.
 - **Show prices.** Always show prices when presenting products or the cart summary.
 - **Use `--json` flag** on all commands for reliable parsing.
 - **Do NOT use the browser skill.** All Amazon interaction goes through the CLI, not browser automation.

package/src/config/bundled-skills/api-mapping/SKILL.md

@@ -1,8 +1,8 @@
 ---
-name: "API Mapping"
-description: "Record and analyze API surfaces of web services"
-user-invocable: true
-metadata: {"vellum": {"emoji": "🗺️"}}
+name: api-mapping
+description: Record and analyze API surfaces of web services
+compatibility: "Designed for Vellum personal assistants"
+metadata: {"emoji":"🗺️","vellum":{"display-name":"API Mapping","user-invocable":true}}
 ---
 
 You can record and analyze the API surface of any web service using the `map` CLI.

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

@@ -1,7 +1,8 @@
 ---
-name: "App Builder"
-description: "Build interactive apps, dashboards, calculators, games, trackers, tools, landing pages, and data visualizations with HTML/CSS/JS. Use when the user says build, create, or make an app/dashboard/calculator/game."
-includes: ["frontend-design"]
+name: app-builder
+description: Build interactive apps, dashboards, calculators, games, trackers, tools, landing pages, and data visualizations with HTML/CSS/JS. Use when the user says build, create, or make an app/dashboard/calculator/game.
+compatibility: "Designed for Vellum personal assistants"
+metadata: {"emoji":"🏗️","vellum":{"display-name":"App Builder","includes":["frontend-design"]}}
 ---
 
 You are an expert app builder and visual designer. When the user asks you to create an app, tool, or utility, you immediately design a data schema, choose a stunning visual direction, build a self-contained HTML/CSS/JS interface, and open it — all in one step. You don't discuss or ask for permission to be creative. You ARE the designer: you pick the colors, the layout, the atmosphere, the micro-interactions. Your apps should make users stop and say "whoa" — they should feel designed, not generated.
@@ -25,8 +26,17 @@ You are an expert app builder and visual designer. When the user asks you to cre
 
 **Make creative decisions on behalf of the user.** They want to be delighted, not consulted. Pick the accent color. Choose between a dark moody aesthetic or a light airy one. Decide if cards should have glassmorphism or layered shadows. Add a background pattern or gradient. These are YOUR decisions as the designer.
 
+<!-- feature:app-builder-multifile:start -->
+
 **Prefer multi-file TSX projects** for any non-trivial app. They give you component reuse, TypeScript safety, and cleaner organization. Fall back to single-file HTML only for the simplest one-off pages.
 
+<!-- feature:app-builder-multifile:end -->
+<!-- feature:app-builder-multifile:alt -->
+
+**Always build single-file HTML apps.** Write a complete, self-contained HTML document with all CSS in `<style>` and all JavaScript in `<script>`. Do not use multi-file projects or TSX.
+
+<!-- feature:app-builder-multifile:alt:end -->
+
 **Only ask questions when the request is genuinely ambiguous** — e.g., "build me an app" with no indication of what kind. Even then, prefer building something impressive based on context clues over asking a battery of questions.
 
 **When in doubt, build something impressive** and let the user refine with `app_update`. The first impression matters most — a beautiful app with the wrong shade of blue is easy to fix. A correct but ugly app is hard to come back from.
@@ -69,7 +79,11 @@ Example schema for a project tracker:
 
 ### 3. Build the App
 
-Apps are rendered inside a sandboxed WebView on macOS. You can build them in two formats: **multi-file TSX** (preferred) or **single-file HTML** (legacy).
+Apps are rendered inside a sandboxed WebView on macOS.
+
+<!-- feature:app-builder-multifile:start -->
+
+You can build them in two formats: **multi-file TSX** (preferred) or **single-file HTML** (legacy).
 
 #### Multi-file TSX projects (preferred)
 
@@ -198,10 +212,11 @@ app_file_write(app_id, "src/styles.css", `.app { padding: var(--v-spacing-lg); }
 - No external fonts, images, or resources — use system fonts and CSS/SVG for visuals
 - Design for 400-600px width with graceful resizing
 - The WebView blocks all navigation — links and form `action` attributes won't work
+<!-- feature:app-builder-multifile:end -->
 
-#### Single HTML file (legacy)
+#### Single HTML file
 
-Use this format only for the simplest one-off pages. Write a complete, self-contained HTML document.
+Write a complete, self-contained HTML document.
 
 **Technical constraints (single-file):**
 

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

@@ -1,9 +1,8 @@
 ---
-name: "Browser"
-description: "Navigate and interact with web pages using a headless browser"
-user-invocable: true
-disable-model-invocation: false
-metadata: {"vellum": {"emoji": "🌐"}}
+name: browser
+description: Navigate and interact with web pages using a headless browser
+compatibility: "Designed for Vellum personal assistants"
+metadata: {"emoji":"🌐","vellum":{"display-name":"Browser","user-invocable":true}}
 ---
 
 Use this skill to browse the web. After loading this skill, the following browser tools become available:

package/src/config/bundled-skills/chatgpt-import/SKILL.md

@@ -1,8 +1,8 @@
 ---
-name: "ChatGPT Import"
-description: "Import conversation history from ChatGPT into Vellum"
-metadata: {"vellum": {"emoji": "📥"}}
-user-invocable: true
+name: chatgpt-import
+description: Import conversation history from ChatGPT into Vellum
+compatibility: "Designed for Vellum personal assistants"
+metadata: {"emoji":"📥","vellum":{"display-name":"ChatGPT Import","user-invocable":true}}
 ---
 
 Import ChatGPT conversation history into Vellum so users can keep their conversation context and memory when switching from ChatGPT.

package/src/config/bundled-skills/chatgpt-import/tools/chatgpt-import.ts

@@ -8,7 +8,7 @@ import { getConfig } from "../../../../config/loader.js";
 import {
   addMessage,
   createConversation,
-} from "../../../../memory/conversation-store.js";
+} from "../../../../memory/conversation-crud.js";
 import { getDb } from "../../../../memory/db.js";
 import { indexMessageNow } from "../../../../memory/indexer.js";
 import {

package/src/config/bundled-skills/claude-code/SKILL.md

@@ -1,8 +1,8 @@
 ---
-name: "Claude Code"
-description: "Delegate coding tasks to Claude Code, an AI-powered coding agent"
-user-invocable: true
-metadata: {"vellum": {"emoji": "💻"}}
+name: claude-code
+description: Delegate coding tasks to Claude Code, an AI-powered coding agent
+compatibility: "Designed for Vellum personal assistants"
+metadata: {"emoji":"💻","vellum":{"display-name":"Claude Code","user-invocable":true}}
 ---
 
 You are delegating a coding task to Claude Code, an autonomous AI coding agent. Use this skill when the user needs hands-on software engineering work done.

package/src/config/bundled-skills/cli-discover/SKILL.md

@@ -1,8 +1,8 @@
 ---
-name: "CLI Discovery"
-description: "Discover which CLI tools are installed, their versions, and authentication status"
-user-invocable: false
-metadata: {"vellum": {"emoji": "🔍"}}
+name: cli-discover
+description: Discover which CLI tools are installed, their versions, and authentication status
+compatibility: "Designed for Vellum personal assistants"
+metadata: {"emoji":"🔍","vellum":{"display-name":"CLI Discovery","user-invocable":false}}
 ---
 
 # CLI Discovery

package/src/config/bundled-skills/computer-use/SKILL.md

@@ -1,8 +1,8 @@
 ---
-name: "Computer Use"
-description: "Computer-use action tools for controlling the macOS desktop via accessibility and screen capture."
-user-invocable: false
-disable-model-invocation: true
+name: computer-use
+description: Computer-use action tools for controlling the macOS desktop via accessibility and screen capture.
+compatibility: "Designed for Vellum personal assistants"
+metadata: {"emoji":"🖥️","vellum":{"display-name":"Computer Use","user-invocable":false,"disable-model-invocation":true}}
 ---
 
 This skill provides the 12 computer*use*\* action tools for controlling