docs(integrations): add v4 integration guides - #2698
Conversation
|
There was a problem hiding this comment.
All reported issues were addressed across 8 files
Architecture diagram
sequenceDiagram
participant Dev as Developer
participant Docs as Mintlify Docs
participant Nav as Docs Navigation
participant Guide as Integration Guide Pages
participant MCP as MCP Guide Page
Note over Dev,Guide: NEW: V4 Integrations Documentation Flow
Dev->>Docs: Browse V4 docs site
Docs->>Nav: Load docs.json config
Nav->>Nav: NEW: Render Integrations group
alt Dev selects framework guide
Nav-->>Guide: CrewAI / Deep Agents / Eve / Mastra / Vercel AI SDK
Guide->>Guide: Display quickstart + config tables
Guide-->>Dev: Setup instructions
else Dev views MCP guide
Nav-->>MCP: v4/best-practices/mcp-integrations
MCP->>Guide: Link to Code Mode integrations overview
Guide-->>Dev: Integration options
end
Note over Guide,Dev: Developer Follows Quickstart
Dev->>Guide: Clone Stagehand repository
Dev->>Dev: Install deps & build (Node.js 24+, pnpm 11.10.0)
alt Framework with MCP/stdio (CrewAI, Mastra, Vercel AI SDK)
Dev->>Dev: Configure agent model (OPENAI_API_KEY, FRAMEWORK_STAGEHAND_MODEL)
Dev->>Dev: Choose browser (local Chrome or Browserbase via STAGEHAND_BROWSER)
Dev->>Dev: Start persistent MCP client session
Dev-->>Dev: Run browser task
else Framework with native tools (Eve)
Dev->>Dev: Configure Eve model
Dev->>Dev: Start Eve in-process (no MCP bridge)
Dev-->>Dev: Run browser task
end
Note over Dev,Guide: Session Lifecycle & Security
Guide->>Dev: Warning: keep one browser session
Guide->>Dev: Note: snapshot IDs valid for latest snapshot only
Guide->>Dev: Security: run executes model-authored JS in browser context
Guide->>Dev: Advise: use Browserbase for untrusted tasks
rect rgb(245, 245, 245)
Note over Guide,Dev: Configuration Variables
Guide-->>Dev: STAGEHAND_BROWSER (local/browserbase)
Guide-->>Dev: BROWSERBASE_API_KEY / BROWSERBASE_PROJECT_ID
Guide-->>Dev: STAGEHAND_MODEL_NAME / STAGEHAND_MODEL_API_KEY
Guide-->>Dev: Framework-specific vars (CREWAI_MODEL, MASTRA_STAGEHAND_MODEL, etc.)
end
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
5458a0d to
5d5be70
Compare
ae952f6 to
8ef6a79
Compare
8ef6a79 to
f7b5d29
Compare
|
@mintlify can I get a preview build |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
There was a problem hiding this comment.
All reported issues were addressed across 7 files (changes from recent commits).
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
Addresses feedback from cubic-dev-ai[bot]
There was a problem hiding this comment.
All reported issues were addressed across 1 file (changes from recent commits).
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
Addresses feedback from cubic-dev-ai.
There was a problem hiding this comment.
All reported issues were addressed across 6 files (changes from recent commits).
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
Addresses feedback from cubic-dev-ai.
Summary
run/snapshot/screenshotcontract, persistent-session requirements, browser configuration, framework-specific behavior, and security boundaryWhy
The integrations under
packages/integrationsare implemented and documented in package READMEs, but the Stagehand docs site does not yet have a discoverable path for choosing or using them. This makes the examples difficult to find and leaves the existing MCP guidance contradictory.Impact
Developers can now choose the right integration from the V4 navigation and follow a source-based quickstart tailored to their framework. The overview also documents the shared core package and the session-lifetime rule that keeps browser state and snapshot IDs valid across tool calls.
Validation
corepack pnpm@11.10.0 install --frozen-lockfilecorepack pnpm@11.10.0 --filter @browserbasehq/stagehand-docs test:unit— 27/27 tests passedcorepack pnpm@11.10.0 --filter @browserbasehq/stagehand-docs typecheck— Mintlify build validation, anchor-aware broken-link checks, and accessibility checks passed across 137 MDX files