fix: vapi listen disclaimer

Author: goosewin

fern/cli/overview.mdx

@@ -12,7 +12,7 @@ The Vapi CLI is the official command-line interface that brings world-class deve
 - Install and authenticate with the Vapi CLI
 - Initialize Vapi in existing projects
 - Manage assistants, phone numbers, and workflows from your terminal
-- Test webhooks locally without external tunnels
+- Forward webhooks to your local development server
 - Turn your IDE into a Vapi expert with MCP integration
 
 ## Installation
@@ -94,13 +94,17 @@ Your IDE's AI assistant (Cursor, Windsurf, VSCode) gains complete, accurate know
 
 ### 🔗 Local webhook testing
 
-Debug webhooks instantly without ngrok:
+Forward webhooks to your local server for debugging:
 
 ```bash
 vapi listen --forward-to localhost:3000/webhook
 ```
 
-All webhook events get forwarded to your local server in real-time with helpful debugging information.
+The CLI provides a public endpoint that forwards events to your local server. You'll need to update your webhook URLs in Vapi to point to this endpoint.
+
+<Note>
+Automatic webhook URL configuration (like Stripe CLI) is coming soon. For now, manually update your webhook URLs in the Vapi dashboard.
+</Note>
 
 ### 🔐 Multi-account management
 

fern/cli/webhook-testing.mdx

@@ -1,42 +1,65 @@
 ---
 title: Local webhook testing
-description: Test webhooks locally without ngrok using vapi listen
+description: Forward webhooks to your local development server with vapi listen
 slug: cli/webhook
 ---
 
 ## Overview
 
-The `vapi listen` command enables real-time webhook testing on your local development server without external tunneling services like ngrok. This dramatically speeds up development by letting you test webhook integrations instantly.
+The `vapi listen` command provides a webhook forwarding service that receives events from Vapi and forwards them to your local development server. This helps you debug webhook integrations without deploying your code.
 
 **In this guide, you'll learn to:**
 - Set up local webhook forwarding
 - Debug webhook events in real-time
 - Configure advanced forwarding options
 - Handle different webhook types
 
+<Info>
+**Note on tunneling:** Currently, `vapi listen` requires you to manually update your webhook URLs in Vapi. Automatic tunnel creation (like Stripe CLI) is coming in a future update.
+</Info>
+
 ## Quick start
 
-Forward Vapi webhooks to your local server:
+<Steps>
+  <Step title="Start the webhook listener">
+    ```bash
+    vapi listen --forward-to localhost:3000/webhook
+    ```
+    
+    Note the public URL provided in the output (e.g., `https://webhook-proxy.vapi.ai/wh_abc123def456`)
+  </Step>
+  
+  <Step title="Update your webhook URLs">
+    Go to your Vapi Dashboard and update your webhook URLs to point to the URL from step 1:
+    - Assistant webhook URL
+    - Phone number webhook URL  
+    - Or any other webhook configuration
+  </Step>
+  
+  <Step title="Test your webhooks">
+    Trigger webhook events (make calls, etc.) and see them forwarded to your local server in real-time
+  </Step>
+</Steps>
 
-```bash
-vapi listen --forward-to localhost:3000/webhook
-```
+## How it works
 
-That's it! All webhook events from Vapi will be forwarded to your local endpoint in real-time.
+<Note>
+**Current implementation:** The `vapi listen` command currently acts as a local webhook forwarder. Unlike tools like Stripe CLI, it doesn't yet create an automatic tunnel to update your Vapi webhook URLs. You'll need to manually configure your webhook URL in Vapi to point to the CLI's endpoint.
 
-## How it works
+**Coming soon:** Automatic tunneling that updates your Vapi webhook configuration is planned for a future release.
+</Note>
 
 <Steps>
   <Step title="Local server starts">
     The CLI starts a webhook server on port 4242 (configurable)
   </Step>
 
-  <Step title="Secure tunnel created">
-    A secure tunnel is established between Vapi and your local server
+  <Step title="Configure webhook URL">
+    Update your Vapi webhook URL to point to the CLI's public endpoint (provided when you start the listener)
   </Step>
 
   <Step title="Events forwarded">
-    All webhook events are forwarded to your specified endpoint
+    All webhook events are forwarded to your specified local endpoint
   </Step>
 
   <Step title="Real-time logging">
@@ -87,10 +110,11 @@ When you run `vapi listen`, you'll see:
 $ vapi listen --forward-to localhost:3000/webhook
 
 🎧 Vapi Webhook Listener
-📡 Listening on: https://vapi-webhooks.ngrok.io/abc123
+📡 Listening on: https://webhook-proxy.vapi.ai/wh_abc123def456
 📍 Forwarding to: http://localhost:3000/webhook
 
-✓ Webhook URL configured in your Vapi account
+⚠️  Please update your webhook URL in Vapi to:
+   https://webhook-proxy.vapi.ai/wh_abc123def456
 
 Waiting for webhook events...
 
@@ -150,6 +174,18 @@ X-Webhook-Timestamp: 1705331445
 
 Your server receives the exact webhook payload from Vapi with these additional headers for debugging.
 
+### Manual webhook configuration
+
+Since automatic tunneling isn't available yet, you'll need to:
+
+1. Start the webhook listener and note the public URL
+2. Go to your Vapi Dashboard or use the API to update webhook URLs
+3. Set the webhook URL to the one provided by `vapi listen`
+
+<Tip>
+**Future enhancement:** We're working on automatic webhook URL updates, similar to how Stripe CLI works. This will eliminate the manual configuration step.
+</Tip>
+
 ### Filtering events
 
 Filter specific event types (coming soon):

fern/debugging.mdx

@@ -125,13 +125,13 @@ Navigate to `Observe > Webhook Logs` to:
 <Tip>
 **Local webhook debugging with Vapi CLI:**
 
-Test webhooks instantly without deploying:
+Forward webhooks to your local server:
 
 ```bash
 vapi listen --forward-to localhost:3000/webhook
 ```
 
-This eliminates the need for ngrok and shows real-time event data in your terminal. [Learn more →](/cli/webhook)
+The CLI provides a public endpoint that forwards events to your local server. You'll need to update your webhook URLs in Vapi to use this endpoint. Automatic configuration is coming soon. [Learn more →](/cli/webhook)
 </Tip>
 
 ### Voice Test Suites

fern/quickstart/introduction.mdx

@@ -142,7 +142,7 @@ The Vapi CLI brings the full power of the platform to your terminal:
     iconType="solid"
   >
     - **Project Integration:** Auto-detect and set up Vapi in any codebase
-    - **Local Testing:** Debug webhooks without ngrok
+    - **Webhook Forwarding:** Test webhooks on your local server
     - **MCP Support:** Turn your IDE into a Vapi expert
     - **Multi-account:** Switch between environments seamlessly
   </Card>

fern/quickstart/web.mdx

@@ -21,7 +21,7 @@ Build powerful voice applications that work across web browsers, mobile apps, an
 # Initialize Vapi in your project
 vapi init
 
-# Test webhooks without ngrok
+# Forward webhooks to local server
 vapi listen --forward-to localhost:3000/webhook
 ```
 

fern/server-url.mdx

@@ -58,7 +58,7 @@ To get started using server URLs, read our guides:
     iconType="solid"
     href="/cli/webhook"
   >
-    Test webhooks instantly with the Vapi CLI - no ngrok required.
+    Forward webhooks to your local server with the Vapi CLI.
   </Card>
 </CardGroup>
 

fern/server-url/developing-locally.mdx

@@ -11,17 +11,23 @@ slug: server-url/developing-locally
 
 ## Quick solution: Vapi CLI
 
-The easiest way to test webhooks locally is with the Vapi CLI:
+Test webhooks locally with the Vapi CLI webhook forwarder:
 
 ```bash
 # Install Vapi CLI
 curl -sSL https://vapi.ai/install.sh | bash
 
-# Forward webhooks to your local server
+# Start webhook forwarding
 vapi listen --forward-to localhost:3000/webhook
 ```
 
-This eliminates the need for ngrok or other tunneling services. [Learn more about the Vapi CLI →](/cli/webhook)
+The CLI provides a public endpoint that forwards events to your local server. You'll need to manually update your webhook URLs in Vapi to use this endpoint.
+
+<Note>
+Unlike tools like Stripe CLI, automatic webhook URL configuration isn't available yet. This feature is coming in a future update. For now, the CLI works similarly to ngrok - providing a public URL that you configure manually.
+</Note>
+
+[Learn more about the Vapi CLI →](/cli/webhook)
 
 ## Manual setup with ngrok
 

fern/tools/custom-tools.mdx

@@ -106,13 +106,13 @@ vapi tool delete <tool-id>
 ```
 
 <Tip>
-**Local development tip:** When developing custom tools, use the Vapi CLI to test webhooks locally:
+**Local development tip:** When developing custom tools, use the Vapi CLI to forward webhooks to your local server:
 
 ```bash
 vapi listen --forward-to localhost:3000/tools/webhook
 ```
 
-This forwards all tool execution requests to your local server for real-time debugging. [Learn more →](/cli/webhook)
+The CLI provides a public endpoint that you can configure as your tool's server URL for testing. Automatic URL configuration is coming soon. [Learn more →](/cli/webhook)
 </Tip>
 
 ## Alternative: API Configuration