@vellumai/assistant 0.12.1-dev.202609141913.5e16607 → 0.12.1-staging.2

package/src/cli/commands/apps.help.ts

@@ -4,30 +4,25 @@ import type { CliCommandHelp } from "../lib/cli-command-help.js";
 
 export const appsHelp: CliCommandHelp = {
   name: "apps",
-  description: "List, inspect, and compile apps",
+  description: "Inspect apps and their on-disk source",
   helpText: `
 Apps are mini-applications the assistant can surface. Each has a name and a
 source directory holding its HTML/TSX definition, pages, and records.
 
 Apps come from two places, distinguished by their source path:
-  workspace   User-created apps under the workspace apps directory.
+  workspace   User-created apps under the workspace apps directory
+              (~/.vellum/apps/<slug>/).
   plugin      Apps bundled by an installed plugin, each a directory under
-              the plugin's apps/ folder. Stray directories without a plugin
-              package.json, and disabled plugins, contribute nothing.
+              ~/.vellum/plugins/<name>/apps/<app>/. Stray directories without
+              a plugin package.json, and disabled plugins, contribute nothing.
 
-Create and delete workspace apps through the app-builder skill and its tools
-(app_create, app_delete). This command lists apps, inspects whether source
-has changed since the last compile, and compiles an app once you are done
-editing. File edits do not compile on their own.
-
-list and inspect read the workspace directly (the assistant does not need to
-be running). refresh compiles inside the running assistant so open surfaces
-pick up the new build, including plugin apps with local source changes.
+This surface is read-only. Workspace apps are created, edited, and deleted
+through the app-builder skill and its tools (app-create, app-update,
+app-delete); plugin apps are owned by their plugin.
 
 Examples:
   $ assistant apps list
-  $ assistant apps inspect Budget
-  $ assistant apps refresh Budget`,
+  $ assistant apps list --json`,
   subcommands: [
     {
       name: "list",
@@ -36,10 +31,10 @@ Examples:
         { flags: "--json", description: "Machine-readable JSON output" },
       ],
       helpText: `
-Lists every app with its name and the absolute path to its source directory.
-The path itself shows whether the app is a workspace app or bundled by a
-plugin. Workspace apps are listed first, then plugin-bundled apps; both are
-sorted by name.
+Lists every app with its name and the absolute path to its source directory —
+the path itself shows whether the app is a workspace app or bundled by a plugin
+(~/.vellum/plugins/<name>/apps/...). Workspace apps are listed first, then
+plugin-bundled apps; both are sorted by name.
 
 Pass --json for machine-readable output.
 
@@ -47,54 +42,5 @@ Examples:
   $ assistant apps list
   $ assistant apps list --json`,
     },
-    {
-      name: "inspect",
-      args: "<app_name>",
-      description:
-        "Show whether an app's source has changed since the last compile",
-      options: [
-        { flags: "--json", description: "Machine-readable JSON output" },
-      ],
-      helpText: `
-Arguments:
-  app_name   App display name, directory slug, or id. Run 'assistant apps list'
-             to see available apps.
-
-Compares the on-disk source against the fingerprint recorded in dist/ at the
-last successful compile. Reports clean (no changes), stale (source drifted),
-never compiled, or unknown baseline (compiled before fingerprints existed).
-
-Does not compile. Use 'assistant apps refresh <app_name>' after inspect when
-source has changed.
-
-Examples:
-  $ assistant apps inspect Budget
-  $ assistant apps inspect Budget --json`,
-    },
-    {
-      name: "refresh",
-      args: "<app_name>",
-      description:
-        "Compile an app and refresh open surfaces. Requires a running assistant",
-      options: [
-        { flags: "--json", description: "Machine-readable JSON output" },
-      ],
-      helpText: `
-Arguments:
-  app_name   App display name, directory slug, or id. Run 'assistant apps list'
-             to see available apps.
-
-Compiles src/ into dist/ inside the running assistant, then refreshes any
-open surfaces and published deployments. Call this once after a batch of
-edits, not after every file write. Workspace and plugin apps are both
-accepted so local plugin source changes can be compiled without waiting
-for the plugin watcher.
-
-The assistant must be running.
-
-Examples:
-  $ assistant apps refresh Budget
-  $ assistant apps refresh Budget --json`,
-    },
   ],
 };

package/src/cli/commands/apps.ts

@@ -1,13 +1,8 @@
 import type { Command } from "commander";
 
-import {
-  cliIpcCall,
-  exitCodeFromIpcResult,
-} from "../../ipc/cli-client.js";
 import { applyCommandHelp, subcommand } from "../lib/cli-command-help.js";
 import { registerCommand } from "../lib/register-command.js";
 import { log } from "../logger.js";
-import { shouldOutputJson, writeError, writeOutput } from "../output.js";
 import { appsHelp } from "./apps.help.js";
 
 interface AppListEntry {
@@ -15,36 +10,6 @@ interface AppListEntry {
   source: string;
 }
 
-interface AppsRefreshResponse {
-  ok: true;
-  appId: string;
-  name: string;
-  compiled: boolean;
-  compile_duration_ms: number;
-  compile_errors?: Array<{
-    text: string;
-    location?: { file: string; line: number; column: number };
-  }>;
-  compile_warnings?: Array<{
-    text: string;
-    location?: { file: string; line: number; column: number };
-  }>;
-}
-
-function refreshHint(appId: string): string {
-  return `Run 'assistant apps refresh ${appId}' to compile.`;
-}
-
-function formatDiagnostic(diag: {
-  text: string;
-  location?: { file: string; line: number; column: number };
-}): string {
-  if (!diag.location) {
-    return diag.text;
-  }
-  return `${diag.location.file}:${diag.location.line}: ${diag.text}`;
-}
-
 export function registerAppsCommand(program: Command): void {
   registerCommand(program, {
     name: appsHelp.name,
@@ -81,154 +46,6 @@ export function registerAppsCommand(program: Command): void {
           log.info(`  ${e.name.padEnd(nameWidth)}  ${e.source}`);
         }
       });
-
-      subcommand(apps, "inspect").action(
-        async (appName: string, opts: { json?: boolean }, cmd: Command) => {
-          const { resolveAppQuery, appNotFoundMessage, appAmbiguousMessage } =
-            await import("../../apps/resolve-app.js");
-          const { inspectAppSource } = await import(
-            "../../apps/source-fingerprint.js"
-          );
-
-          const resolved = resolveAppQuery(appName);
-          if (!resolved.ok) {
-            const message =
-              resolved.reason === "ambiguous"
-                ? appAmbiguousMessage(resolved.query, resolved.matches)
-                : appNotFoundMessage(resolved.query);
-            writeError(cmd, message);
-            process.exitCode = 1;
-            return;
-          }
-
-          const { app } = resolved;
-          const inspect = inspectAppSource(app.sourcePath);
-          const origin =
-            app.origin.kind === "plugin"
-              ? { kind: "plugin" as const, plugin: app.origin.pluginName }
-              : { kind: "workspace" as const };
-
-          if (opts.json || shouldOutputJson(cmd)) {
-            writeOutput(cmd, {
-              ok: true,
-              app: {
-                id: app.id,
-                name: app.name,
-                source: app.sourcePath,
-                origin,
-              },
-              compile: inspect,
-            });
-            return;
-          }
-
-          const originLabel =
-            origin.kind === "plugin"
-              ? `plugin ${origin.plugin}`
-              : "workspace";
-          log.info(`App: ${app.name} (${originLabel})`);
-          log.info(`Id: ${app.id}`);
-          log.info(`Source: ${app.sourcePath}`);
-
-          if (inspect.status === "clean") {
-            const when = inspect.compiledAt
-              ? ` (compiled ${inspect.compiledAt})`
-              : "";
-            log.info(`Compile: up to date${when}`);
-            return;
-          }
-          if (inspect.status === "never_compiled") {
-            log.info("Compile: never compiled");
-            log.info(refreshHint(app.id));
-            return;
-          }
-          if (inspect.status === "unknown_baseline") {
-            log.info(
-              "Compile: compiled, but no source fingerprint is recorded.",
-            );
-            log.info(
-              `Run 'assistant apps refresh ${app.id}' to record one and rebuild.`,
-            );
-            return;
-          }
-
-          const when = inspect.compiledAt
-            ? ` (last compiled ${inspect.compiledAt})`
-            : "";
-          log.info(`Compile: source changed since last compile${when}`);
-          if (inspect.modified.length > 0) {
-            log.info("Modified:");
-            for (const path of inspect.modified) {
-              log.info(`  ${path}`);
-            }
-          }
-          if (inspect.added.length > 0) {
-            log.info("Added:");
-            for (const path of inspect.added) {
-              log.info(`  ${path}`);
-            }
-          }
-          if (inspect.removed.length > 0) {
-            log.info("Removed:");
-            for (const path of inspect.removed) {
-              log.info(`  ${path}`);
-            }
-          }
-          log.info(refreshHint(app.id));
-        },
-      );
-
-      subcommand(apps, "refresh").action(
-        async (appName: string, opts: { json?: boolean }, cmd: Command) => {
-          const { resolveAppQuery, appNotFoundMessage, appAmbiguousMessage } =
-            await import("../../apps/resolve-app.js");
-
-          const resolved = resolveAppQuery(appName);
-          if (!resolved.ok) {
-            const message =
-              resolved.reason === "ambiguous"
-                ? appAmbiguousMessage(resolved.query, resolved.matches)
-                : appNotFoundMessage(resolved.query);
-            writeError(cmd, message);
-            process.exitCode = 1;
-            return;
-          }
-
-          const result = await cliIpcCall<AppsRefreshResponse>("apps_refresh", {
-            pathParams: { id: resolved.app.id },
-          });
-
-          if (!result.ok || !result.result) {
-            writeError(cmd, result.error ?? "Refresh failed");
-            process.exitCode = exitCodeFromIpcResult(result);
-            return;
-          }
-
-          const payload = result.result;
-          if (opts.json || shouldOutputJson(cmd)) {
-            writeOutput(cmd, payload);
-            if (!payload.compiled) {
-              process.exitCode = 1;
-            }
-            return;
-          }
-
-          if (!payload.compiled) {
-            log.error(
-              `Compile failed for "${payload.name}" (${payload.compile_duration_ms}ms).`,
-            );
-            for (const diag of payload.compile_errors ?? []) {
-              log.error(`  ${formatDiagnostic(diag)}`);
-            }
-            process.exitCode = 1;
-            return;
-          }
-
-          log.info(
-            `Compiled "${payload.name}" in ${payload.compile_duration_ms}ms.`,
-          );
-        },
-      );
     },
   });
 }

package/src/cli/commands/bash.help.ts

@@ -6,7 +6,7 @@ export const bashHelp: CliCommandHelp = {
   name: "bash",
   args: "<command>",
   description:
-    "Execute a shell command with the same sanitized environment as the bash tool",
+    "Execute a shell command through the assistant process for debugging",
   options: [
     {
       flags: "-t, --timeout <ms>",
@@ -15,19 +15,24 @@ export const bashHelp: CliCommandHelp = {
     },
   ],
   helpText: `
-Spawns the command with the same sanitized environment, working directory,
-and platform shell the bash tool uses for tool-call subprocesses. Vault
-bearers such as CES_SERVICE_TOKEN are stripped; CES_LOCAL_SOCKET and workspace
-paths are forwarded. The command does not go through the assistant HTTP or IPC
-API, and does not require a running assistant process.
+Sends a shell command to the running assistant for execution via the IPC
+socket. The assistant spawns the command in its own process environment and
+returns stdout, stderr, and the exit code.
+
+This is a developer debugging tool for inspecting how the assistant invokes and
+observes shell commands. The command runs with the assistant's environment, working
+directory, and process context — not the caller's shell.
+
+Requires the assistant to be running with VELLUM_DEBUG=1. When debug mode is off
+(the default), the assistant returns an error immediately.
 
 Arguments:
   command   The shell command string to execute (e.g. "echo hello", "ls -la").
-            Runs via the same platform shell invocation the bash tool uses.
+            Runs in bash via \`bash -c\` in the assistant's process environment.
 
 Examples:
   $ assistant bash "echo hello"
   $ assistant bash "which node"
   $ assistant bash "env | grep PATH" --timeout 10000
-  $ assistant bash "assistant oauth request --provider outlook --json https://graph.microsoft.com/v1.0/me"`,
+  $ assistant bash "ls -la"`,
 };

package/src/cli/commands/bash.ts

@@ -1,19 +1,28 @@
 /**
- * `assistant bash` runs a shell command with the same sanitized environment
- * the bash tool forwards to tool-call subprocesses.
+ * `assistant bash` — run a shell command in the assistant's process
+ * environment (debug tool, requires VELLUM_DEBUG=1 on the daemon).
  */
 
 import type { Command } from "commander";
 
+import { cliIpcCall } from "../../ipc/cli-client.js";
 import { applyCommandHelp, commandSpec } from "../lib/cli-command-help.js";
 import { registerCommand } from "../lib/register-command.js";
 import { log } from "../logger.js";
 import { bashHelp } from "./bash.help.js";
 
+interface DebugBashResult {
+  stdout: string;
+  stderr: string;
+  exitCode: number | null;
+  timedOut: boolean;
+  error?: string;
+}
+
 export function registerBashCommand(program: Command): void {
   registerCommand(program, {
     name: commandSpec(bashHelp),
-    transport: "local",
+    transport: "ipc",
     description: bashHelp.description,
     build: (cmd) => {
       applyCommandHelp(cmd, bashHelp);
@@ -25,10 +34,19 @@ export function registerBashCommand(program: Command): void {
           return;
         }
 
-        const { runSanitizedBash } = await import(
-          "../../tools/terminal/sanitized-bash.js"
+        const result = await cliIpcCall<DebugBashResult>(
+          "debug_bash",
+          { body: { command, timeoutMs } },
+          { timeoutMs: timeoutMs + 10_000 },
         );
-        const data = await runSanitizedBash(command, timeoutMs);
+
+        if (!result.ok) {
+          log.error(result.error ?? "Failed to reach the assistant.");
+          process.exitCode = 1;
+          return;
+        }
+
+        const data = result.result!;
 
         if (data.error) {
           log.error(data.error);
@@ -51,7 +69,7 @@ export function registerBashCommand(program: Command): void {
         }
 
         if (data.timedOut) {
-          log.info("Command timed out.");
+          log.info(`Command timed out in assistant.`);
         }
 
         if (data.exitCode != null && data.exitCode !== 0) {

package/src/cli/commands/channels/index.help.ts

@@ -36,14 +36,9 @@ assistant's own bot on that channel (${BOT_CHANNELS}), resolving the bot
 credential from the channel id so no token is handled. Acting as a person
 through their OAuth integration is 'assistant oauth request'.
 
-To say something in a chat, use 'send' rather than 'request': it goes
-through the channel's transport, so the post is threaded and rendered like
-every other message the assistant sends there, and it is recorded.
-
 Examples:
   $ assistant channels list
   $ assistant channels get slack
-  $ assistant channels send slack C0123456789 --text 'deploy is green'
   $ assistant channels request slack /auth.test --json
   $ assistant channels request slack -X POST \\
       -d '{"channel":"D0123456789","limit":20}' /conversations.history --json`,
@@ -70,9 +65,8 @@ This command can do anything the bot's API allows, including sending,
 editing, deleting, uploading, and reacting, so it is classified high risk
 and asks for approval like any action with irreversible effects. Reads are
 not distinguished from writes: the effect is the endpoint's. To send a
-message, use 'assistant channels send', which posts through the channel's
-transport and records what it sent; a message posted through this command
-reaches the platform directly and leaves no record of what was said.
+message, use the messaging tool, which records what it sent; do not post
+through this command.
 
 Arguments:
   <channel>  One of: ${BOT_CHANNELS}. A channel with no bot credential of
@@ -92,68 +86,6 @@ Examples:
   $ assistant channels request slack -X POST \\
       -d '{"channel":"D0123456789","limit":100}' /conversations.history --json
   $ assistant channels request discord /users/@me --json`,
-    },
-    {
-      name: "send",
-      description:
-        "Post text to a chat on the channel, as the assistant's bot, recorded",
-      arguments: [
-        {
-          name: "<channel>",
-          description: `Channel to post on. One with a transport that can be addressed from a named chat; anything else is refused before the send.`,
-        },
-        {
-          name: "<chat-id>",
-          description:
-            "The chat in the channel's own id space (a Slack channel or DM id, a Telegram chat id, a Discord channel id, a WhatsApp number).",
-        },
-      ],
-      options: [
-        {
-          flags: "--text <text>",
-          description: "The message text. Required.",
-        },
-        {
-          flags: "--thread <id>",
-          description:
-            "Post inside this thread or topic, in the channel's own id space. Omit to post to the chat itself.",
-        },
-        {
-          flags: "--plain",
-          description:
-            "Send the text verbatim instead of the channel's rich rendering.",
-        },
-        {
-          flags: "--json",
-          description: "Machine-readable compact JSON output",
-        },
-      ],
-      helpText: `
-Posts one message through the channel's own transport, the same path a
-reply takes. Once the channel acknowledges it, the daemon records it in
-the chat's conversation, which is what lets the assistant see later what
-it said here and lets a reaction or an edit naming that post resolve back
-to it. Recording is best effort and never fails a send that already went
-out, so the result names the conversation only when the record was
-written.
-
-This sends a message people will read, so it is classified high risk and
-asks for approval like any other action with effects nobody can take back.
-
-The send fails, and records nothing, when the channel does not acknowledge
-it or names no message id for it. A channel the assistant cannot address
-from a named chat is refused before anything is sent. If the daemon does
-not answer in time, the message may still go out: that is reported as an
-unknown outcome rather than a failure, so check the chat before sending
-again.
-
-Attachments are not sent from here.
-
-Examples:
-  $ assistant channels send slack C0123456789 --text 'deploy is green'
-  $ assistant channels send slack C0123456789 --thread 1700000000.000100 \
-      --text 'and the smoke tests passed'
-  $ assistant channels send telegram 123456789 --text 'morning' --json`,
     },
     {
       name: "list",

package/src/cli/commands/channels/index.ts

@@ -1,10 +1,9 @@
 /**
  * `assistant channels`: inspect messaging channels, and act as their bots.
  *
- *   list                          : overview of every channel + ready state
- *   get <channel>                 : detailed live snapshot of a single channel
- *   request <channel> <url>       : call the channel's platform API as its bot
- *   send <channel> <chat-id>      : post text to a chat, recorded
+ *   list                     : overview of every channel + ready state
+ *   get <channel>            : detailed live snapshot of a single channel
+ *   request <channel> <url>  : call the channel's platform API as its bot
  *
  * `get` always re-runs remote probes (it invalidates the readiness cache
  * before reading), so the CLI answer matches the live source-of-truth.
@@ -13,11 +12,6 @@
  * channel's bot credential and makes the same authenticated request
  * `oauth request` makes, without the caller naming a provider.
  *
- * `send` is the send door (see ./send.ts): it runs the daemon's one send
- * implementation for the channel, so the post is threaded, rendered, and
- * recorded like every other message the assistant sends there. Posting
- * through `request` instead reaches the platform API and leaves no record.
- *
  * A mutating `refresh` verb (for reconnecting channels, e.g. supplying
  * fresh Slack tokens) is intentionally not part of this group.
  */
@@ -32,7 +26,6 @@ import { log } from "../../logger.js";
 import { shouldOutputJson, writeOutput } from "../../output.js";
 import { CHANNELS_PLUGIN_SEARCH_HINT, channelsHelp } from "./index.help.js";
 import { registerChannelsRequestCommand } from "./request.js";
-import { registerChannelsSendCommand } from "./send.js";
 
 // ---------------------------------------------------------------------------
 // Snapshot shape
@@ -218,12 +211,6 @@ export function registerChannelsCommand(program: Command): void {
       // -----------------------------------------------------------------------
 
       registerChannelsRequestCommand(channels);
-
-      // -----------------------------------------------------------------------
-      // send: post text to a chat, through the channel's transport
-      // -----------------------------------------------------------------------
-
-      registerChannelsSendCommand(channels);
     },
   });
 }

package/src/cli/commands/credentials.help.ts

@@ -45,12 +45,8 @@ Examples:
         },
       ],
       helpText: `
-Lists credentials from the live credential vault. Each entry includes the same
-fields as inspect: scrubbed value, timestamps, policy, and metadata.
-
-Fails immediately with an error if the credential vault is unreachable. An
-empty list means the vault answered and has no matching credentials, not that
-the store is down.
+Lists all credentials in the vault. Each entry includes the same fields as
+"inspect" — scrubbed value, timestamps, policy, and metadata.
 
 The --search flag filters results by case-insensitive substring match against
 the credential's service name, field name, label, or description. For example, --search

package/src/cli/commands/credentials.ts

@@ -343,8 +343,8 @@ export function registerCredentialsCommand(program: Command): void {
           } else {
             printCredentialHuman(output);
             if (output.brokerUnreachable) {
-              log.warn(
-                "    Credential store is unreachable. Retry in a moment, or check that the credential vault is running.",
+              log.info(
+                "    ⚠ Credential store is unreachable — ensure the assistant is running",
               );
             }
           }

package/src/cli/commands/mcp.help.ts

@@ -7,8 +7,8 @@ export const mcpHelp: CliCommandHelp = {
   description: "Manage MCP (Model Context Protocol) servers",
   helpText: `
 MCP servers extend the assistant's capabilities with external tools. Servers
-are configured in the assistant's mcp.json, or declared by an installed
-plugin in its root mcp.json. Each
+are configured in the assistant's config.json under the mcp.servers key, or
+declared by an installed plugin in its root mcp.json. Each
 server uses one of three transport types:
 
   stdio             Local process communicating over stdin/stdout
@@ -30,8 +30,8 @@ Examples:
       options: [{ flags: "--json", description: "Output as JSON" }],
       helpText: `
 Shows each MCP server with its current status and configuration. Servers come
-from two places: the workspace mcp.json, and the root mcp.json of any
-installed plugin that declares one.
+from two places: the mcp.servers key in config.json, and the root mcp.json of
+any installed plugin that declares one.
 
   Name         The server identifier
   Status       Health check result for workspace servers:
@@ -43,7 +43,7 @@ installed plugin that declares one.
                health-checked, so no stored credential can reach a URL a
                plugin chose.
   Source       Shown only for plugin-declared servers, naming the plugin.
-               Servers from workspace mcp.json print no Source line.
+               Servers from config.json print no Source line.
   Transport    stdio, sse, or streamable-http
   URL/Command  The server URL (sse/streamable-http) or command (stdio)
 
@@ -64,7 +64,7 @@ on their next turn automatically. The assistant must be running.
 
 Examples:
   $ vellum mcp reload
-  $ vellum mcp reload   # after editing mcp.json to add a new server
+  $ vellum mcp reload   # after editing config.json to add a new server
   $ vellum mcp reload   # after running "vellum mcp auth <server>"`,
     },
     {
@@ -95,7 +95,7 @@ Examples:
       ],
       helpText: `
 Arguments:
-  name   Unique identifier for the server (used as the key in mcp.json)
+  name   Unique identifier for the server (used as the key in config.json)
 
 Transport-specific requirements:
   stdio             Requires --command (and optional --args for arguments)
@@ -149,7 +149,7 @@ Examples:
 Arguments:
   name   Name of the MCP server to remove
 
-Removes the server entry from mcp.json and performs best-effort cleanup of
+Removes the server entry from config.json and performs best-effort cleanup of
 any stored OAuth credentials (tokens, client info, discovery metadata) for
 sse/streamable-http servers. If no OAuth credentials exist, the cleanup is
 silently skipped.

package/src/cli/commands/mcp.ts

@@ -20,7 +20,7 @@ interface McpServerEntry {
     command?: string;
     args?: string[];
   };
-  /** Workspace `mcp.json` or a plugin's `mcp.json`. */
+  /** Workspace `config.json` or a plugin's `mcp.json`. */
   source?: "workspace" | "plugin";
   /** Plugin that declared the server, when `source` is `plugin`. */
   pluginName?: string;

package/src/cli/commands/roadmap.help.ts

@@ -4,12 +4,8 @@ import type { CliCommandHelp } from "../lib/cli-command-help.js";
 
 export const roadmapHelp: CliCommandHelp = {
   name: "roadmap",
-  description:
-    "Read and file public feature proposals as the assistant. For bugs and support, instruct the user to join the Discord community at https://vellum.ai/community",
+  description: "Read and file public Vellum roadmap feedback as the assistant",
   helpText: `
-Items created here must be public feature proposals. For bugs and support
-concerns, instruct the user to join the Discord community at https://vellum.ai/community.
-
 Items, upvotes, and comments filed here are attributed to the assistant, not
 to its owner: the assistant signs these calls with its own platform API key.
 The owner's own roadmap identity lives on \`vellum roadmap\`.