zod fix

Author: Kylejeong2

package.json

@@ -36,7 +36,8 @@
     "@browserbasehq/stagehand": "^2.4.0",
     "@modelcontextprotocol/sdk": "^1.13.1",
     "@playwright/test": "^1.49.0",
-    "commander": "^14.0.0"
+    "commander": "^14.0.0",
+    "zod": "^3.25.67"
   },
   "devDependencies": {
     "@eslint/js": "^9.29.0",

pnpm-lock.yaml

@@ -32,7 +32,6 @@ const cookieSchema = z.object({
 });
 
 // Configuration schema for Smithery - matches existing Config interface
-// @ts-expect-error Type instantiation is excessively deep and possibly infinite with complex Zod schemas
 export const configSchema = z.object({
   browserbaseApiKey: z.string().describe("The Browserbase API Key to use"),
   browserbaseProjectId: z

src/index.ts

@@ -72,6 +72,7 @@ BEST PRACTICES:
 - Always close sessions when done to free resources
 - Take screenshots for visual confirmation or debugging
 - Each session maintains independent state and authentication
+- No need to create backup sessions - sessions are reliable and persistent
 
 When using this server, think of it as controlling real browsers in the cloud. You can navigate, click, type, extract data, and capture screenshots just like a human would, but with the precision and scale of automation.`,
           },
@@ -113,6 +114,7 @@ IMPORTANT RULES:
 - Each session maintains independent cookies, authentication, and browser state
 - Always close sessions when finished to free resources
 - Use descriptive session names for easier tracking
+- No need to create backup sessions - sessions are reliable and persistent
 
 SINGLE VS MULTI-SESSION:
 - Single: "browserbase_session_create" → "browserbase_stagehand_navigate"