@vellumai/assistant 0.3.4 → 0.3.6

package/src/__tests__/session-process-bridge.test.ts

@@ -1,244 +0,0 @@
-import { describe, test, expect, beforeEach, mock } from 'bun:test';
-import { mkdtempSync } from 'node:fs';
-import { tmpdir } from 'node:os';
-import { join } from 'node:path';
-
-const testDir = mkdtempSync(join(tmpdir(), 'session-process-bridge-test-'));
-
-// ── Platform + logger mocks ─────────────────────────────────────────
-
-mock.module('../util/platform.js', () => ({
-  getDataDir: () => testDir,
-  isMacOS: () => process.platform === 'darwin',
-  isLinux: () => process.platform === 'linux',
-  isWindows: () => process.platform === 'win32',
-  getSocketPath: () => join(testDir, 'test.sock'),
-  getPidPath: () => join(testDir, 'test.pid'),
-  getDbPath: () => join(testDir, 'test.db'),
-  getLogPath: () => join(testDir, 'test.log'),
-  ensureDataDir: () => {},
-}));
-
-mock.module('../util/logger.js', () => ({
-  getLogger: () =>
-    new Proxy({} as Record<string, unknown>, {
-      get: () => () => {},
-    }),
-}));
-
-mock.module('../config/loader.js', () => ({
-  getConfig: () => ({
-    apiKeys: { anthropic: 'test-key' },
-    model: 'claude-sonnet-4-20250514',
-    provider: 'anthropic',
-    memory: { enabled: false },
-    calls: { enabled: false },
-    contextWindow: { maxInputTokens: 200000 },
-  }),
-}));
-
-// ── Mock the call bridge ─────────────────────────────────────────────
-
-import type { CallBridgeResult } from '../calls/call-bridge.js';
-
-const mockTryRouteCallMessage = mock(
-  (_convId: string, _text: string, _msgId?: string): Promise<CallBridgeResult> =>
-    Promise.resolve({ handled: false, reason: 'no_active_call' }),
-);
-
-mock.module('../calls/call-bridge.js', () => ({
-  tryRouteCallMessage: (...args: [string, string, string?]) => mockTryRouteCallMessage(...args),
-}));
-
-// ── Mock slash resolution ────────────────────────────────────────────
-
-mock.module('./session-slash.js', () => ({
-  resolveSlash: (content: string) => ({ kind: 'passthrough' as const, content }),
-}));
-
-// ── Import after mocks ──────────────────────────────────────────────
-
-import type { ServerMessage } from '../daemon/ipc-protocol.js';
-import type { ProcessSessionContext } from '../daemon/session-process.js';
-import { processMessage, drainQueue } from '../daemon/session-process.js';
-import { MessageQueue } from '../daemon/session-queue-manager.js';
-
-// ── Session mock factory ─────────────────────────────────────────────
-
-function createMockSession(overrides?: Partial<ProcessSessionContext>): ProcessSessionContext {
-  return {
-    conversationId: 'test-conv',
-    messages: [],
-    processing: false,
-    abortController: null,
-    currentRequestId: undefined,
-    queue: new MessageQueue(),
-    traceEmitter: {
-      emit: () => {},
-    } as unknown as ProcessSessionContext['traceEmitter'],
-    usageStats: { inputTokens: 0, outputTokens: 0, estimatedCost: 0 },
-    persistUserMessage: mock((_content: string, _attachments: unknown[], _requestId?: string) => 'mock-msg-id'),
-    runAgentLoop: mock(async () => {}),
-    ...overrides,
-  };
-}
-
-// ── Tests ────────────────────────────────────────────────────────────
-
-describe('session-process bridge consumption', () => {
-  beforeEach(() => {
-    mockTryRouteCallMessage.mockReset();
-  });
-
-  // ── Direct processMessage path ───────────────────────────────
-
-  test('processMessage emits assistant_text_delta + message_complete when bridge consumes with userFacingText', async () => {
-    mockTryRouteCallMessage.mockResolvedValue({
-      handled: true,
-      userFacingText: 'Instruction relayed to active call.',
-    });
-
-    const events: ServerMessage[] = [];
-    const onEvent = (msg: ServerMessage) => events.push(msg);
-    const session = createMockSession();
-
-    await processMessage(session, 'ask about pricing', [], onEvent);
-
-    // Should have emitted text delta then message_complete
-    const textDelta = events.find((e) => e.type === 'assistant_text_delta');
-    expect(textDelta).toBeDefined();
-    expect((textDelta as { text: string }).text).toBe('Instruction relayed to active call.');
-
-    const complete = events.find((e) => e.type === 'message_complete');
-    expect(complete).toBeDefined();
-
-    // Should NOT have called runAgentLoop
-    expect(session.runAgentLoop).not.toHaveBeenCalled();
-  });
-
-  test('processMessage emits failure text when bridge consumes with failure userFacingText', async () => {
-    mockTryRouteCallMessage.mockResolvedValue({
-      handled: true,
-      reason: 'instruction_relay_failed',
-      userFacingText: 'Failed to relay instruction to the active call.',
-    });
-
-    const events: ServerMessage[] = [];
-    const onEvent = (msg: ServerMessage) => events.push(msg);
-    const session = createMockSession();
-
-    await processMessage(session, 'change the topic', [], onEvent);
-
-    const textDelta = events.find((e) => e.type === 'assistant_text_delta');
-    expect(textDelta).toBeDefined();
-    expect((textDelta as { text: string }).text).toBe('Failed to relay instruction to the active call.');
-
-    const complete = events.find((e) => e.type === 'message_complete');
-    expect(complete).toBeDefined();
-
-    // Only one message_complete
-    const completeCount = events.filter((e) => e.type === 'message_complete').length;
-    expect(completeCount).toBe(1);
-
-    expect(session.runAgentLoop).not.toHaveBeenCalled();
-  });
-
-  test('processMessage skips text delta when bridge consumes without userFacingText', async () => {
-    mockTryRouteCallMessage.mockResolvedValue({
-      handled: true,
-    });
-
-    const events: ServerMessage[] = [];
-    const onEvent = (msg: ServerMessage) => events.push(msg);
-    const session = createMockSession();
-
-    await processMessage(session, 'hello', [], onEvent);
-
-    const textDelta = events.find((e) => e.type === 'assistant_text_delta');
-    expect(textDelta).toBeUndefined();
-
-    const complete = events.find((e) => e.type === 'message_complete');
-    expect(complete).toBeDefined();
-
-    expect(session.runAgentLoop).not.toHaveBeenCalled();
-  });
-
-  test('processMessage falls through to agent loop when bridge does not consume', async () => {
-    mockTryRouteCallMessage.mockResolvedValue({
-      handled: false,
-      reason: 'no_active_call',
-    });
-
-    const events: ServerMessage[] = [];
-    const onEvent = (msg: ServerMessage) => events.push(msg);
-    const session = createMockSession();
-
-    await processMessage(session, 'normal message', [], onEvent);
-
-    expect(session.runAgentLoop).toHaveBeenCalled();
-  });
-
-  // ── Queued routeOrProcess path ───────────────────────────────
-
-  test('drainQueue emits assistant_text_delta + message_complete for bridge-consumed queued message', async () => {
-    mockTryRouteCallMessage.mockResolvedValue({
-      handled: true,
-      userFacingText: 'Instruction relayed to active call.',
-    });
-
-    const events: ServerMessage[] = [];
-    const onEvent = (msg: ServerMessage) => events.push(msg);
-    const session = createMockSession({ processing: true });
-
-    // Enqueue a message
-    session.queue.push({
-      content: 'ask about pricing',
-      attachments: [],
-      requestId: 'req-1',
-      onEvent,
-    });
-
-    drainQueue(session);
-
-    // Wait for async routeOrProcess
-    await new Promise((r) => setTimeout(r, 50));
-
-    const textDelta = events.find((e) => e.type === 'assistant_text_delta');
-    expect(textDelta).toBeDefined();
-    expect((textDelta as { text: string }).text).toBe('Instruction relayed to active call.');
-
-    // message_complete (from dequeue + bridge consumption — only one expected for this request)
-    const completeEvents = events.filter((e) => e.type === 'message_complete');
-    expect(completeEvents.length).toBe(1);
-
-    expect(session.runAgentLoop).not.toHaveBeenCalled();
-  });
-
-  test('drainQueue emits failure text for bridge-consumed queued message with relay failure', async () => {
-    mockTryRouteCallMessage.mockResolvedValue({
-      handled: true,
-      reason: 'instruction_relay_failed',
-      userFacingText: 'Failed to relay instruction to the active call.',
-    });
-
-    const events: ServerMessage[] = [];
-    const onEvent = (msg: ServerMessage) => events.push(msg);
-    const session = createMockSession({ processing: true });
-
-    session.queue.push({
-      content: 'change the topic',
-      attachments: [],
-      requestId: 'req-2',
-      onEvent,
-    });
-
-    drainQueue(session);
-    await new Promise((r) => setTimeout(r, 50));
-
-    const textDelta = events.find((e) => e.type === 'assistant_text_delta');
-    expect(textDelta).toBeDefined();
-    expect((textDelta as { text: string }).text).toBe('Failed to relay instruction to the active call.');
-
-    expect(session.runAgentLoop).not.toHaveBeenCalled();
-  });
-});

package/src/calls/call-bridge.ts

@@ -1,168 +0,0 @@
-/**
- * Call message bridge: intercepts user messages in-thread and routes them
- * to the live call orchestrator — either as answers to pending questions
- * or as mid-call steering instructions.
- *
- * Decision priority:
- * 1. If a pending question exists → answer path (existing behavior).
- * 2. If no pending question but an active call exists → instruction path.
- *
- * When the bridge consumes a message it returns `{ handled: true }` so
- * the caller can skip agent processing.
- */
-
-import { getLogger } from '../util/logger.js';
-import {
-  getActiveCallSessionForConversation,
-  getPendingQuestion,
-  answerPendingQuestion,
-  recordCallEvent,
-  getCallSession,
-} from './call-store.js';
-import { getCallOrchestrator } from './call-state.js';
-import { relayInstruction } from './call-domain.js';
-import * as conversationStore from '../memory/conversation-store.js';
-
-const log = getLogger('call-bridge');
-
-export interface CallBridgeResult {
-  handled: boolean;
-  reason?: string;
-  /** User-facing text persisted in-thread by the bridge (success ack or failure notice). */
-  userFacingText?: string;
-}
-
-/**
- * Attempt to route a user message to an active call — as an answer to
- * a pending question (priority) or as a mid-call steering instruction.
- *
- * @param conversationId - The conversation the message belongs to.
- * @param userText - The user's message text.
- * @param _userMessageId - The persisted message ID (reserved for future use).
- * @returns `{ handled: true }` if the message was consumed by the call system,
- *          `{ handled: false, reason }` otherwise.
- */
-export async function tryRouteCallMessage(
-  conversationId: string,
-  userText: string,
-  _userMessageId?: string,
-): Promise<CallBridgeResult> {
-  // 1. Find an active call for this conversation
-  const callSession = getActiveCallSessionForConversation(conversationId);
-  if (!callSession) {
-    return { handled: false, reason: 'no_active_call' };
-  }
-
-  // 2. Check for a pending question — answer path takes priority
-  const pendingQuestion = getPendingQuestion(callSession.id);
-  if (pendingQuestion) {
-    return handleAnswer(conversationId, callSession.id, pendingQuestion, userText);
-  }
-
-  // 3. No pending question — instruction path
-  return handleInstruction(conversationId, callSession.id, userText);
-}
-
-/** @deprecated Use `tryRouteCallMessage` instead. */
-export const tryHandlePendingCallAnswer = tryRouteCallMessage;
-
-// ── Answer path ─────────────────────────────────────────────────────
-
-async function handleAnswer(
-  conversationId: string,
-  callSessionId: string,
-  pendingQuestion: { id: string; questionText: string },
-  userText: string,
-): Promise<CallBridgeResult> {
-  // Empty text (e.g. attachment-only messages) should not be consumed as
-  // an answer — fall through to normal processing so attachments are handled.
-  if (!userText.trim()) {
-    return { handled: false, reason: 'empty_answer_text' };
-  }
-
-  const orchestrator = getCallOrchestrator(callSessionId);
-  if (!orchestrator) {
-    // The call may have ended between the question being asked and the
-    // user replying. Persist a follow-up message so the user knows.
-    const freshSession = getCallSession(callSessionId);
-    const ended = freshSession && (freshSession.status === 'completed' || freshSession.status === 'failed');
-    if (ended) {
-      conversationStore.addMessage(
-        conversationId,
-        'assistant',
-        JSON.stringify([{
-          type: 'text',
-          text: 'The call ended before your answer could be relayed to the caller.',
-        }]),
-      );
-    }
-    return { handled: false, reason: 'orchestrator_not_found' };
-  }
-
-  if (orchestrator.getState() !== 'waiting_on_user') {
-    return { handled: false, reason: 'orchestrator_not_waiting' };
-  }
-
-  const accepted = await orchestrator.handleUserAnswer(userText);
-  if (!accepted) {
-    return { handled: false, reason: 'orchestrator_rejected' };
-  }
-
-  answerPendingQuestion(pendingQuestion.id, userText);
-  recordCallEvent(callSessionId, 'user_answered', { answer: userText });
-
-  log.info(
-    { conversationId, callSessionId, questionId: pendingQuestion.id },
-    'User reply routed as call answer via bridge',
-  );
-
-  return { handled: true };
-}
-
-// ── Instruction path ────────────────────────────────────────────────
-
-async function handleInstruction(
-  conversationId: string,
-  callSessionId: string,
-  userText: string,
-): Promise<CallBridgeResult> {
-  // Empty text (e.g. attachment-only messages) should not be relayed —
-  // fall through to normal processing so attachments are handled.
-  if (!userText.trim()) {
-    return { handled: false, reason: 'empty_instruction_text' };
-  }
-
-  const result = await relayInstruction({ callSessionId, instructionText: userText });
-
-  if (!result.ok) {
-    log.warn(
-      { conversationId, callSessionId, error: result.error },
-      'Instruction relay failed via bridge',
-    );
-
-    const failureText = 'Failed to relay instruction to the active call.';
-    conversationStore.addMessage(
-      conversationId,
-      'assistant',
-      JSON.stringify([{ type: 'text', text: failureText }]),
-    );
-
-    // Consumed: caller should NOT fall through to the agent loop
-    return { handled: true, reason: 'instruction_relay_failed', userFacingText: failureText };
-  }
-
-  // Persist a concise acknowledgement so the user sees confirmation
-  const ackText = 'Instruction relayed to active call.';
-  conversationStore.addMessage(
-    conversationId,
-    'assistant',
-    JSON.stringify([{ type: 'text', text: ackText }]),
-  );
-
-  log.info(
-    { conversationId, callSessionId },
-    'User message routed as call instruction via bridge',
-  );
-
-  return { handled: true, userFacingText: ackText };
-}

package/src/config/vellum-skills/google-oauth-setup/SKILL.md

@@ -1,199 +0,0 @@
----
-name: "Google OAuth Setup"
-description: "Create Google Cloud OAuth credentials for Gmail integration using browser automation"
-user-invocable: true
-includes: ["browser", "public-ingress"]
-metadata: {"vellum": {"emoji": "\ud83d\udd11"}}
----
-
-You are helping your user create Google Cloud OAuth credentials so the Gmail and Google Calendar integrations can connect. Walk through each step below using `browser_navigate`, `browser_snapshot`, `browser_screenshot`, `browser_click`, `browser_type`, and `browser_extract` tools.
-
-**Tone:** Be friendly and reassuring throughout. Narrate what you're doing in plain language so the user always knows what's happening. After each step, briefly confirm what was accomplished before moving on.
-
-## Prerequisites
-
-Before starting, check that `ingress.publicBaseUrl` is configured (Settings > Public Ingress, or `INGRESS_PUBLIC_BASE_URL` env var). If it is not set, load and execute the **public-ingress** skill first (`skill_load` with `skill: "public-ingress"`) to set up an ngrok tunnel and persist the public URL. The OAuth redirect URI depends on this value.
-
-## Before You Start
-
-Tell the user:
-- "I'll walk you through setting up Google Cloud so Vellum can connect to your Gmail and Google Calendar. The whole process takes a few minutes."
-- "I'll be automating the Google Cloud Console in the browser — you'll be able to see everything I'm doing."
-- "I'll ask for your approval before each major step, so nothing happens without your say-so."
-- "No sensitive credentials will be shown in the conversation."
-
-## Step 1: Navigate to Google Cloud Console
-
-Tell the user: "First, let me open Google Cloud Console."
-
-Use `browser_navigate` to go to `https://console.cloud.google.com/`.
-
-Take a `browser_screenshot` to show the user what loaded, then take a `browser_snapshot` to check the page state:
-- **If a sign-in page appears:** Tell the user "Please sign in to your Google account in the browser window. Let me know when you're done." Wait for their confirmation, then take another snapshot.
-- **If a CAPTCHA appears:** Tell the user "There's a CAPTCHA to solve. Please complete it in the browser window and let me know." Wait, then retry.
-- **If the console dashboard loads:** Tell the user "Google Cloud Console is loaded. Let's get started!" and continue to Step 2.
-
-## Step 2: Create or Select a Project
-
-**Ask for approval before proceeding.** Use `ui_show` with `surface_type: "confirmation"` and this message:
-
-> **Create a Google Cloud Project**
->
-> I'm about to create a new Google Cloud project called "Vellum Assistant". This is completely free and won't affect any of your existing projects. The project is just a container for the Gmail API credentials.
-
-Wait for the user to approve. If they decline, explain that a project is required for OAuth credentials and offer to try again or cancel the setup.
-
-Once approved, navigate to `https://console.cloud.google.com/projectcreate`.
-
-Take a `browser_snapshot`. Fill in the project name form:
-- Use `browser_type` to set the project name to "Vellum Assistant"
-- Use `browser_click` to submit the "Create" button
-
-Wait a few seconds, then take a `browser_screenshot` to show the user what happened, and a `browser_snapshot` to confirm the project was created. If the project already exists, that's fine — navigate to its dashboard.
-
-Tell the user: "Project created! Now let's enable the Gmail API."
-
-Note the project ID from the URL or page content for subsequent steps.
-
-## Step 3: Enable the Gmail and Calendar APIs
-
-**Ask for approval before proceeding.** Use `ui_show` with `surface_type: "confirmation"` and this message:
-
-> **Enable the Gmail and Calendar APIs**
->
-> I'm about to enable the Gmail API and Google Calendar API in your Google Cloud project. This allows Vellum to access your email and calendar — but only after you explicitly authorize it in a later step. Enabling the APIs alone doesn't grant any access.
-
-Wait for the user to approve. If they decline, explain that the APIs are required for email and calendar integration and offer to try again or cancel.
-
-Once approved, navigate to `https://console.cloud.google.com/apis/library/gmail.googleapis.com?project=PROJECT_ID` (substitute the actual project ID).
-
-Take a `browser_snapshot`:
-- **If the API is already enabled:** You'll see "API enabled" or a "Manage" button. Tell the user "Gmail API is already enabled — great!" and continue to enable Calendar API.
-- **If not enabled:** Use `browser_click` on the "Enable" button.
-
-Wait a moment, then take a `browser_screenshot` to show the result and a `browser_snapshot` to confirm it shows as enabled.
-
-Now navigate to `https://console.cloud.google.com/apis/library/calendar-json.googleapis.com?project=PROJECT_ID` to enable the Google Calendar API.
-
-Take a `browser_snapshot`:
-- **If the API is already enabled:** Tell the user "Google Calendar API is already enabled — great!" and skip to Step 4.
-- **If not enabled:** Use `browser_click` on the "Enable" button.
-
-Wait a moment, then take a `browser_screenshot` to show the result.
-
-Tell the user: "Gmail and Calendar APIs are enabled! Next, we need to set up an OAuth consent screen."
-
-## Step 4: Configure the OAuth Consent Screen
-
-**Ask for approval before proceeding.** Use `ui_show` with `surface_type: "confirmation"` and this message:
-
-> **Configure OAuth Consent Screen**
->
-> I'm about to set up an OAuth consent screen for your project. This is the page Google shows when you authorize an app. I'll configure it with your email and the Gmail permissions Vellum needs (read, modify, and send emails). The app will start in "testing" mode — only you will be able to authorize it.
-
-Wait for the user to approve. If they decline, explain that the consent screen is required for the OAuth flow and offer to try again or cancel.
-
-Once approved, navigate to `https://console.cloud.google.com/apis/credentials/consent?project=PROJECT_ID`.
-
-Take a `browser_snapshot` to check the current state:
-- **If consent screen is already configured:** Tell the user "Consent screen is already set up — skipping ahead!" and go to Step 5.
-- **If a user type selection appears:** Select "External" and click "Create".
-
-Fill in the required fields on the consent screen form:
-1. **App name:** "Vellum Assistant"
-2. **User support email:** Select the user's email from the dropdown
-3. **Developer contact email:** Type the user's email address
-4. Leave other fields as defaults
-
-Use `browser_click` to proceed through each page of the wizard:
-- App information page: Fill fields, click "Save and Continue"
-- Scopes page: Click "Add or Remove Scopes", search for and select:
-  - `https://www.googleapis.com/auth/gmail.readonly`
-  - `https://www.googleapis.com/auth/gmail.modify`
-  - `https://www.googleapis.com/auth/gmail.send`
-  - `https://www.googleapis.com/auth/calendar.readonly`
-  - `https://www.googleapis.com/auth/calendar.events`
-  - `https://www.googleapis.com/auth/userinfo.email`
-  - Click "Update" then "Save and Continue"
-- Test users page: Add the user's email as a test user, click "Save and Continue"
-- Summary page: Click "Back to Dashboard"
-
-Take a `browser_screenshot` after completing the wizard.
-
-Tell the user: "Consent screen is configured! Almost there — just need to create the credentials."
-
-## Step 5: Create OAuth Credentials
-
-**Ask for approval before proceeding.** Use `ui_show` with `surface_type: "confirmation"` and this message:
-
-> **Create OAuth Credentials**
->
-> I'm about to create OAuth Web Application credentials for Vellum Assistant. This generates a client ID that Vellum uses to initiate the authorization flow. The redirect URI will point to the gateway's OAuth callback endpoint.
-
-Wait for the user to approve. If they decline, explain that credentials are the final step needed and offer to try again or cancel.
-
-Once approved, navigate to `https://console.cloud.google.com/apis/credentials?project=PROJECT_ID`.
-
-Use `browser_click` on "+ Create Credentials" at the top, then select "OAuth client ID" from the dropdown.
-
-Take a `browser_snapshot` and fill in:
-1. **Application type:** Select "Web application" from the dropdown
-2. **Name:** "Vellum Assistant"
-3. **Authorized redirect URIs:** Click "Add URI" and enter `${ingress.publicBaseUrl}/webhooks/oauth/callback` (e.g. `https://abc123.ngrok-free.app/webhooks/oauth/callback`). Read the `ingress.publicBaseUrl` value from the assistant's workspace config (Settings > Public Ingress) or the `INGRESS_PUBLIC_BASE_URL` environment variable.
-
-Use `browser_click` on the "Create" button.
-
-## Step 6: Extract and Store the Client ID
-
-After creation, a dialog should appear showing the client ID and client secret.
-
-Use `browser_snapshot` or `browser_extract` to read the **Client ID** value from the dialog. The client ID looks like `NUMBERS-CHARS.apps.googleusercontent.com`.
-
-**Important:** You only need the Client ID, not the client secret (PKCE flow is used).
-
-Tell the user: "Credentials created! Now let's connect your Gmail account using the client ID."
-
-## Step 7: Connect Gmail
-
-Tell the user: "Opening Google sign-in so you can authorize Vellum to access your Gmail. You'll see a Google consent page — just click 'Allow'."
-
-Use the `credential_store` tool to connect Gmail via OAuth2:
-
-```
-action: "oauth2_connect"
-service: "integration:gmail"
-client_id: "<the extracted client ID>"
-auth_url: "https://accounts.google.com/o/oauth2/v2/auth"
-token_url: "https://oauth2.googleapis.com/token"
-scopes: ["https://www.googleapis.com/auth/gmail.readonly", "https://www.googleapis.com/auth/gmail.modify", "https://www.googleapis.com/auth/gmail.send", "https://www.googleapis.com/auth/calendar.readonly", "https://www.googleapis.com/auth/calendar.events", "https://www.googleapis.com/auth/userinfo.email"]
-userinfo_url: "https://www.googleapis.com/oauth2/v2/userinfo"
-extra_params: {"access_type": "offline", "prompt": "consent"}
-```
-
-This will open the Google authorization page in the user's browser. Wait for the flow to complete.
-
-**If the user sees a "This app isn't verified" warning:** Tell them this is normal for apps in testing mode. They should click "Advanced" → "Go to Vellum Assistant (unsafe)" to proceed. This warning appears because the app hasn't gone through Google's verification process, which is only needed for apps used by many people.
-
-## Step 8: Celebrate!
-
-Once connected, tell the user:
-
-"**Gmail and Calendar are connected!** You're all set. You can now read, search, and send emails, plus view and manage your calendar through Vellum. Try asking me to check your inbox or show your upcoming events!"
-
-Summarize what was accomplished:
-- Created a Google Cloud project (or used an existing one)
-- Enabled the Gmail API and Google Calendar API
-- Configured the OAuth consent screen with appropriate scopes (including calendar)
-- Created OAuth Web Application credentials with gateway callback redirect URI
-- Connected your Gmail and Google Calendar accounts
-
-## Error Handling
-
-- **Page load failures:** Retry navigation once. If it still fails, tell the user and ask them to check their internet connection.
-- **Permission errors in GCP:** The user may need billing enabled or organization-level permissions. Explain what's needed clearly and ask them to resolve it.
-- **Consent screen already configured with different settings:** Don't overwrite; skip to credential creation and tell the user you're using their existing configuration.
-- **Element not found for click/type:** Take a fresh `browser_snapshot` to re-assess the page layout. GCP UI may have changed; adapt your selectors. Tell the user what you're looking for if you get stuck.
-- **User declines an approval gate:** Don't push back aggressively. Explain briefly why the step matters, offer to try again, or offer to cancel the whole setup gracefully. Never proceed without approval.
-- **OAuth flow timeout or failure:** Tell the user what happened and offer to retry the connect step. The client ID is already stored, so they can also connect later from Settings.
-- **"This app isn't verified" warning:** Guide the user through clicking "Advanced" → "Go to Vellum Assistant (unsafe)". Reassure them this is expected for personal-use OAuth apps.
-- **Any unexpected state:** Take a `browser_screenshot` and `browser_snapshot`, describe what you see, and ask the user for guidance rather than guessing.