@vellumai/assistant 0.4.37 → 0.4.41

package/src/cli/sequence.ts

@@ -1,5 +1,5 @@
 /**
- * CLI command group: `vellum sequence`
+ * CLI command group: `assistant sequence`
  *
  * Manage email sequences — list, inspect, pause, resume, and view stats.
  */
@@ -81,10 +81,10 @@ Guardrails enforce rate limits, daily send caps, cooldown periods, and
 duplicate enrollment checks to prevent abuse.
 
 Examples:
-  $ vellum sequence list --status active
-  $ vellum sequence get seq_abc123
-  $ vellum sequence pause seq_abc123
-  $ vellum sequence stats`,
+  $ assistant sequence list --status active
+  $ assistant sequence get seq_abc123
+  $ assistant sequence pause seq_abc123
+  $ assistant sequence stats`,
   );
 
   // ── list ──────────────────────────────────────────────────────────
@@ -102,9 +102,9 @@ and active enrollment count.
 If omitted, returns all sequences regardless of status.
 
 Examples:
-  $ vellum sequence list
-  $ vellum sequence list --status active
-  $ vellum sequence list --status paused --json`,
+  $ assistant sequence list
+  $ assistant sequence list --status active
+  $ assistant sequence list --status paused --json`,
     )
     .action((opts: { status?: string }, cmd: Command) => {
       initializeDb();
@@ -149,8 +149,8 @@ setting, all steps with delay and approval configuration, and enrollment
 breakdown by status (active, paused, completed, replied, cancelled, failed).
 
 Examples:
-  $ vellum sequence get seq_abc123
-  $ vellum sequence get seq_abc123 --json`,
+  $ assistant sequence get seq_abc123
+  $ assistant sequence get seq_abc123 --json`,
     )
     .action((id: string, _opts: Record<string, unknown>, cmd: Command) => {
       initializeDb();
@@ -222,8 +222,8 @@ enrollments remain in their current state but no new steps will be sent
 until the sequence is resumed. No-op if the sequence is already paused.
 
 Examples:
-  $ vellum sequence pause seq_abc123
-  $ vellum sequence pause seq_abc123 --json`,
+  $ assistant sequence pause seq_abc123
+  $ assistant sequence pause seq_abc123 --json`,
     )
     .action((id: string, _opts: Record<string, unknown>, cmd: Command) => {
       initializeDb();
@@ -252,8 +252,8 @@ Resumes a paused sequence, re-enabling scheduled step deliveries for all
 active enrollments. No-op if the sequence is already active.
 
 Examples:
-  $ vellum sequence resume seq_abc123
-  $ vellum sequence resume seq_abc123 --json`,
+  $ assistant sequence resume seq_abc123
+  $ assistant sequence resume seq_abc123 --json`,
     )
     .action((id: string, _opts: Record<string, unknown>, cmd: Command) => {
       initializeDb();
@@ -284,8 +284,8 @@ changes to "cancelled". This does not affect the sequence itself or
 other enrollments.
 
 Examples:
-  $ vellum sequence cancel-enrollment enr_xyz789
-  $ vellum sequence cancel-enrollment enr_xyz789 --json`,
+  $ assistant sequence cancel-enrollment enr_xyz789
+  $ assistant sequence cancel-enrollment enr_xyz789 --json`,
     )
     .action(
       (enrollmentId: string, _opts: Record<string, unknown>, cmd: Command) => {
@@ -310,8 +310,8 @@ Returns aggregate statistics across all sequences: total and active
 sequence counts, total and active enrollment counts.
 
 Examples:
-  $ vellum sequence stats
-  $ vellum sequence stats --json`,
+  $ assistant sequence stats
+  $ assistant sequence stats --json`,
     )
     .action((_opts: Record<string, unknown>, cmd: Command) => {
       initializeDb();
@@ -358,9 +358,9 @@ hourly rate limits, minimum delays between steps, maximum concurrent active
 enrollments, duplicate enrollment prevention, and cooldown periods.
 
 Examples:
-  $ vellum sequence guardrails show
-  $ vellum sequence guardrails set dailySendCap 200
-  $ vellum sequence guardrails set cooldown_days 7`,
+  $ assistant sequence guardrails show
+  $ assistant sequence guardrails set dailySendCap 200
+  $ assistant sequence guardrails set cooldown_days 7`,
   );
 
   guardrailsCmd
@@ -379,8 +379,8 @@ Displays the current guardrail configuration with all safety limits:
   Cooldown period         Time before a contact can be re-enrolled after completion
 
 Examples:
-  $ vellum sequence guardrails show
-  $ vellum sequence guardrails show --json`,
+  $ assistant sequence guardrails show
+  $ assistant sequence guardrails show --json`,
     )
     .action((_opts: Record<string, unknown>, cmd: Command) => {
       const json = getJson(cmd);
@@ -428,10 +428,10 @@ Valid keys:
   cooldown_days                                Cooldown period in days (converted to ms internally) (numeric)
 
 Examples:
-  $ vellum sequence guardrails set dailySendCap 200
-  $ vellum sequence guardrails set hourly_rate 50
-  $ vellum sequence guardrails set duplicate_check true
-  $ vellum sequence guardrails set cooldown_days 7`,
+  $ assistant sequence guardrails set dailySendCap 200
+  $ assistant sequence guardrails set hourly_rate 50
+  $ assistant sequence guardrails set duplicate_check true
+  $ assistant sequence guardrails set cooldown_days 7`,
     )
     .action(
       (

package/src/cli/sessions.ts

@@ -31,10 +31,10 @@ communicate via IPC), while "export" and "clear" operate on the local SQLite
 database directly.
 
 Examples:
-  $ vellum sessions list
-  $ vellum sessions new "Project planning"
-  $ vellum sessions export
-  $ vellum sessions clear`,
+  $ assistant sessions list
+  $ assistant sessions new "Project planning"
+  $ assistant sessions export
+  $ assistant sessions clear`,
   );
 
   sessions
@@ -50,7 +50,7 @@ Requires the assistant to be running — communicates via IPC. If auto-start is
 enabled, the assistant will be started automatically.
 
 Examples:
-  $ vellum sessions list`,
+  $ assistant sessions list`,
     )
     .action(async () => {
       if (shouldAutoStartDaemon()) await ensureDaemonRunning();
@@ -82,9 +82,9 @@ Creates a new conversation session and prints its title and ID. Requires the
 assistant to be running — communicates via IPC.
 
 Examples:
-  $ vellum sessions new
-  $ vellum sessions new "Project planning"
-  $ vellum sessions new "Bug triage 2026-03-05"`,
+  $ assistant sessions new
+  $ assistant sessions new "Project planning"
+  $ assistant sessions new "Bug triage 2026-03-05"`,
     )
     .action(async (title?: string) => {
       if (shouldAutoStartDaemon()) await ensureDaemonRunning();
@@ -121,9 +121,9 @@ Two output formats are available:
 Operates on the local SQLite database directly — does not require the assistant.
 
 Examples:
-  $ vellum sessions export
-  $ vellum sessions export --format json -o conversation.json
-  $ vellum sessions export abc123 --format md`,
+  $ assistant sessions export
+  $ assistant sessions export --format json -o conversation.json
+  $ assistant sessions export abc123 --format md`,
     )
     .action(
       async (
@@ -204,7 +204,7 @@ the assistant, but will notify it if running.
 Intended for development use. This action cannot be undone.
 
 Examples:
-  $ vellum sessions clear`,
+  $ assistant sessions clear`,
     )
     .action(async () => {
       log.info(

package/src/cli/trust.ts

@@ -24,9 +24,9 @@ a scope, a decision (allow or deny), and a priority. Rules are stored in
 assistant invokes a tool.
 
 Examples:
-  $ vellum trust list
-  $ vellum trust remove abc123
-  $ vellum trust clear`,
+  $ assistant trust list
+  $ assistant trust remove abc123
+  $ assistant trust clear`,
   );
 
   trust
@@ -49,7 +49,7 @@ IDs are shown truncated to 8 characters. Use the full ID or any unique
 prefix with "trust remove".
 
 Examples:
-  $ vellum trust list`,
+  $ assistant trust list`,
     )
     .action(() => {
       const rules = getAllRules();
@@ -104,9 +104,9 @@ no rule matches, exits with an error. Use "trust list" to see rule IDs
 (shown truncated to 8 chars).
 
 Examples:
-  $ vellum trust remove abc12345
-  $ vellum trust remove abc1
-  $ vellum trust remove a1b2c3d4-e5f6-7890-abcd-ef1234567890`,
+  $ assistant trust remove abc12345
+  $ assistant trust remove abc1
+  $ assistant trust remove a1b2c3d4-e5f6-7890-abcd-ef1234567890`,
     )
     .action((id: string) => {
       const rules = getAllRules();
@@ -148,7 +148,7 @@ confirmation before proceeding (y/N). This action is irreversible — all
 rules must be re-created manually after clearing.
 
 Examples:
-  $ vellum trust clear`,
+  $ assistant trust clear`,
     )
     .action(async () => {
       const rules = getAllRules();

package/src/cli/twitter.ts

@@ -1,5 +1,5 @@
 /**
- * CLI command group: `vellum twitter`
+ * CLI command group: `assistant twitter`
  *
  * Post tweets and manage Twitter sessions via the command line.
  * All commands output JSON to stdout. Use --json for machine-readable output.
@@ -24,6 +24,7 @@ import {
   searchTweets,
   SessionExpiredError,
 } from "../twitter/client.js";
+import type { TwitterStrategy } from "../twitter/router.js";
 import { routedPostTweet } from "../twitter/router.js";
 import {
   clearSession,
@@ -58,7 +59,7 @@ function getJson(cmd: Command): boolean {
 
 const SESSION_EXPIRED_MSG =
   "Your Twitter session has expired. Please sign in to Twitter in Chrome — " +
-  "run `vellum twitter refresh` to capture your session automatically.";
+  "run `assistant twitter refresh` to capture your session automatically.";
 
 async function run(cmd: Command, fn: () => Promise<unknown>): Promise<void> {
   try {
@@ -142,11 +143,11 @@ Session management:
   - "logout" clears the saved browser session cookies
 
 Examples:
-  $ vellum x status
-  $ vellum x post "Hello world"
-  $ vellum x timeline elonmusk --count 10
-  $ vellum x search "from:vaborsh AI agents" --product Latest
-  $ vellum x strategy set oauth`,
+  $ assistant x status
+  $ assistant x post "Hello world"
+  $ assistant x timeline elonmusk --count 10
+  $ assistant x search "from:vaborsh AI agents" --product Latest
+  $ assistant x strategy set oauth`,
   );
 
   // =========================================================================
@@ -166,8 +167,8 @@ After import, all browser-path commands (timeline, search, bookmarks, etc.)
 will use these cookies for authentication.
 
 Examples:
-  $ vellum x login --recording /tmp/ride-shotgun/recording-abc123.json
-  $ vellum x login --recording ~/recordings/twitter-session.json`,
+  $ assistant x login --recording /tmp/ride-shotgun/recording-abc123.json
+  $ assistant x login --recording ~/recordings/twitter-session.json`,
     )
     .action(async (opts: { recording: string }, cmd: Command) => {
       await run(cmd, async () => {
@@ -193,7 +194,7 @@ will fail until a new session is imported via "login" or captured via "refresh".
 OAuth credentials are not affected.
 
 Examples:
-  $ vellum x logout`,
+  $ assistant x logout`,
     )
     .action((_opts: unknown, cmd: Command) => {
       clearSession();
@@ -224,9 +225,9 @@ cookies are imported automatically and Chrome is minimized.
 Requires the assistant to be running (Ride Shotgun runs via the assistant).
 
 Examples:
-  $ vellum x refresh
-  $ vellum x refresh --duration 120
-  $ vellum x refresh --duration 300`,
+  $ assistant x refresh
+  $ assistant x refresh --duration 120
+  $ assistant x refresh --duration 300`,
     )
     .action(async (opts: { duration: string }, cmd: Command) => {
       const json = getJson(cmd);
@@ -287,8 +288,8 @@ Shows the current state of both authentication paths:
 If the assistant is not running, OAuth fields will be reported as undefined.
 
 Examples:
-  $ vellum x status
-  $ vellum x status --json`,
+  $ assistant x status
+  $ assistant x status --json`,
     )
     .action(async (_opts: unknown, cmd: Command) => {
       const session = loadSession();
@@ -363,9 +364,9 @@ support both OAuth and browser session:
 Run without a subcommand to display the current strategy. Use "set" to change it.
 
 Examples:
-  $ vellum x strategy
-  $ vellum x strategy set oauth
-  $ vellum x strategy set auto`,
+  $ assistant x strategy
+  $ assistant x strategy set oauth
+  $ assistant x strategy set auto`,
     )
     .action(async (_opts: unknown, cmd: Command) => {
       const json = getJson(cmd);
@@ -399,9 +400,9 @@ routing. The setting is persisted by the assistant and applies to all subsequent
 operations until changed.
 
 Examples:
-  $ vellum x strategy set oauth
-  $ vellum x strategy set browser
-  $ vellum x strategy set auto`,
+  $ assistant x strategy set oauth
+  $ assistant x strategy set browser
+  $ assistant x strategy set auto`,
     )
     .action(async (value: string, _opts: unknown, cmd: Command) => {
       const json = getJson(cmd);
@@ -435,31 +436,59 @@ Examples:
   tw.command("post")
     .description("Post a tweet")
     .argument("<text>", "Tweet text")
+    .requiredOption(
+      "--strategy <strategy>",
+      "Operation strategy: oauth, browser, or auto",
+    )
+    .option(
+      "--oauth-token <token>",
+      "OAuth access token (required when strategy is oauth or auto)",
+    )
     .addHelpText(
       "after",
       `
 Arguments:
   text   The tweet text to post (max 280 characters)
 
-Posts a new tweet using the routed dual-path system. The path used (oauth or
-browser) depends on the current strategy setting. The response includes the
-tweet ID, URL, and which path was used.
+Posts a new tweet using the routed dual-path system. The --strategy flag
+controls which path is used. The response includes the tweet ID, URL, and
+which path was used.
 
 Examples:
-  $ vellum x post "Hello world"
-  $ vellum x post "Check out this thread on AI agents" --json`,
+  $ assistant x post "Hello world" --strategy browser
+  $ assistant x post "Hello world" --strategy oauth --oauth-token "$TOKEN"
+  $ assistant x post "Hello world" --strategy auto --oauth-token "$TOKEN"`,
     )
-    .action(async (text: string, _opts: unknown, cmd: Command) => {
-      await run(cmd, async () => {
-        const { result, pathUsed } = await routedPostTweet(text);
-        return {
-          tweetId: result.tweetId,
-          text: result.text,
-          url: result.url,
-          pathUsed,
-        };
-      });
-    });
+    .action(
+      async (
+        text: string,
+        opts: { strategy: string; oauthToken?: string },
+        cmd: Command,
+      ) => {
+        await run(cmd, async () => {
+          const strategy = opts.strategy as TwitterStrategy;
+          if (
+            strategy !== "oauth" &&
+            strategy !== "browser" &&
+            strategy !== "auto"
+          ) {
+            throw new Error(
+              `Invalid strategy "${opts.strategy}". Must be oauth, browser, or auto.`,
+            );
+          }
+          const { result, pathUsed } = await routedPostTweet(text, {
+            strategy,
+            oauthToken: opts.oauthToken,
+          });
+          return {
+            tweetId: result.tweetId,
+            text: result.text,
+            url: result.url,
+            pathUsed,
+          };
+        });
+      },
+    );
 
   // =========================================================================
   // reply — reply to a tweet
@@ -468,6 +497,14 @@ Examples:
     .description("Reply to a tweet")
     .argument("<tweetUrl>", "Tweet URL or tweet ID")
     .argument("<text>", "Reply text")
+    .requiredOption(
+      "--strategy <strategy>",
+      "Operation strategy: oauth, browser, or auto",
+    )
+    .option(
+      "--oauth-token <token>",
+      "OAuth access token (required when strategy is oauth or auto)",
+    )
     .addHelpText(
       "after",
       `
@@ -477,15 +514,30 @@ Arguments:
 
 Posts a reply to the specified tweet. Accepts either a full tweet URL or a bare
 numeric tweet ID. The tweet ID is extracted from the last numeric segment of the
-URL. Uses the routed dual-path system based on the current strategy.
+URL. The --strategy flag controls which path is used.
 
 Examples:
-  $ vellum x reply https://x.com/elonmusk/status/1234567890 "Great point!"
-  $ vellum x reply 1234567890 "Interesting thread"`,
+  $ assistant x reply https://x.com/elonmusk/status/1234567890 "Great point!" --strategy browser
+  $ assistant x reply 1234567890 "Interesting thread" --strategy oauth --oauth-token "$TOKEN"`,
     )
     .action(
-      async (tweetUrl: string, text: string, _opts: unknown, cmd: Command) => {
+      async (
+        tweetUrl: string,
+        text: string,
+        opts: { strategy: string; oauthToken?: string },
+        cmd: Command,
+      ) => {
         await run(cmd, async () => {
+          const strategy = opts.strategy as TwitterStrategy;
+          if (
+            strategy !== "oauth" &&
+            strategy !== "browser" &&
+            strategy !== "auto"
+          ) {
+            throw new Error(
+              `Invalid strategy "${opts.strategy}". Must be oauth, browser, or auto.`,
+            );
+          }
           // Extract tweet ID: either a bare numeric ID or the last numeric segment of a URL
           const idMatch = tweetUrl.match(/(\d+)\s*$/);
           if (!idMatch) {
@@ -494,6 +546,8 @@ Examples:
           const inReplyToTweetId = idMatch[1];
           const { result, pathUsed } = await routedPostTweet(text, {
             inReplyToTweetId,
+            strategy,
+            oauthToken: opts.oauthToken,
           });
           return {
             tweetId: result.tweetId,
@@ -523,9 +577,9 @@ to a user ID first, then retrieves their tweet timeline. The --count flag contro
 how many tweets to return (default: 20).
 
 Examples:
-  $ vellum x timeline elonmusk
-  $ vellum x timeline vaborsh --count 50
-  $ vellum x timeline openai --count 10 --json`,
+  $ assistant x timeline elonmusk
+  $ assistant x timeline vaborsh --count 50
+  $ assistant x timeline openai --count 10 --json`,
     )
     .action(
       async (screenName: string, opts: { count: string }, cmd: Command) => {
@@ -558,9 +612,9 @@ ID is extracted from the last numeric segment of the input. Returns an array of
 tweets representing the conversation thread.
 
 Examples:
-  $ vellum x tweet 1234567890
-  $ vellum x tweet https://x.com/elonmusk/status/1234567890
-  $ vellum x tweet https://x.com/openai/status/9876543210 --json`,
+  $ assistant x tweet 1234567890
+  $ assistant x tweet https://x.com/elonmusk/status/1234567890
+  $ assistant x tweet https://x.com/openai/status/9876543210 --json`,
     )
     .action(async (tweetIdOrUrl: string, _opts: unknown, cmd: Command) => {
       await run(cmd, async () => {
@@ -595,9 +649,9 @@ The --product flag selects the search result type:
 Uses the browser session path. Requires an active browser session.
 
 Examples:
-  $ vellum x search "AI agents"
-  $ vellum x search "from:elonmusk SpaceX" --product Latest
-  $ vellum x search "machine learning" --product Media --json`,
+  $ assistant x search "AI agents"
+  $ assistant x search "from:elonmusk SpaceX" --product Latest
+  $ assistant x search "machine learning" --product Media --json`,
     )
     .action(async (query: string, opts: { product: string }, cmd: Command) => {
       await run(cmd, async () => {
@@ -625,9 +679,9 @@ Requires an active browser session. Bookmarks are private and only available
 for the logged-in account.
 
 Examples:
-  $ vellum x bookmarks
-  $ vellum x bookmarks --count 50
-  $ vellum x bookmarks --json`,
+  $ assistant x bookmarks
+  $ assistant x bookmarks --count 50
+  $ assistant x bookmarks --json`,
     )
     .action(async (opts: { count: string }, cmd: Command) => {
       await run(cmd, async () => {
@@ -651,9 +705,9 @@ browser session. The --count flag controls how many tweets to return (default: 2
 Requires an active browser session.
 
 Examples:
-  $ vellum x home
-  $ vellum x home --count 50
-  $ vellum x home --json`,
+  $ assistant x home
+  $ assistant x home --count 50
+  $ assistant x home --json`,
     )
     .action(async (opts: { count: string }, cmd: Command) => {
       await run(cmd, async () => {
@@ -678,9 +732,9 @@ how many notifications to return (default: 20).
 Requires an active browser session.
 
 Examples:
-  $ vellum x notifications
-  $ vellum x notifications --count 50
-  $ vellum x notifications --json`,
+  $ assistant x notifications
+  $ assistant x notifications --count 50
+  $ assistant x notifications --json`,
     )
     .action(async (opts: { count: string }, cmd: Command) => {
       await run(cmd, async () => {
@@ -707,9 +761,9 @@ screen name to a user ID first. The --count flag controls how many liked tweets
 to return (default: 20).
 
 Examples:
-  $ vellum x likes elonmusk
-  $ vellum x likes vaborsh --count 50
-  $ vellum x likes openai --json`,
+  $ assistant x likes elonmusk
+  $ assistant x likes vaborsh --count 50
+  $ assistant x likes openai --json`,
     )
     .action(
       async (screenName: string, opts: { count: string }, cmd: Command) => {
@@ -737,8 +791,8 @@ Fetches the list of accounts following the specified user via the browser sessio
 Resolves the screen name to a user ID first.
 
 Examples:
-  $ vellum x followers elonmusk
-  $ vellum x followers vaborsh --json`,
+  $ assistant x followers elonmusk
+  $ assistant x followers vaborsh --json`,
     )
     .action(async (screenName: string, _opts: unknown, cmd: Command) => {
       await run(cmd, async () => {
@@ -767,9 +821,9 @@ Resolves the screen name to a user ID first. The --count flag controls how many
 results to return (default: 20).
 
 Examples:
-  $ vellum x following elonmusk
-  $ vellum x following vaborsh --count 100
-  $ vellum x following openai --json`,
+  $ assistant x following elonmusk
+  $ assistant x following vaborsh --count 100
+  $ assistant x following openai --json`,
     )
     .action(
       async (screenName: string, opts: { count: string }, cmd: Command) => {
@@ -802,9 +856,9 @@ session. Resolves the screen name to a user ID first. The --count flag controls
 how many media tweets to return (default: 20).
 
 Examples:
-  $ vellum x media elonmusk
-  $ vellum x media nasa --count 50
-  $ vellum x media openai --json`,
+  $ assistant x media elonmusk
+  $ assistant x media nasa --count 50
+  $ assistant x media openai --json`,
     )
     .action(
       async (screenName: string, opts: { count: string }, cmd: Command) => {

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

@@ -3,7 +3,7 @@
 Use this pattern for setup/status reads in bundled skills:
 
 1. Run Vellum CLI reads through `bash` (not `host_bash`).
-2. Use domain commands (for example `vellum integrations twilio config`) instead of direct gateway `curl`.
+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.
 
 When a skill needs outbound API calls with a stored credential (outside of Vellum CLI reads), use proxied bash: