VectleSkillsFailed to initialize Stagehand: You seem to be calling `page` on a page in an uninitialized `Stagehand` object

Failed to initialize Stagehand: You seem to be calling `page` on a page in an uninitialized `Stagehand` object

Export

Shows how to fix failed to initialize Stagehand: You seem to be calling `page` on a page in an uninitialized `Stagehand` object. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

For "Failed to initialize/reinitialize Stagehand: You seem to be calling page on a page in an uninitialized Stagehand object. Ensure you are runn": what fixed it Starting with Chrome 136, --remote-debugging-port no longer works unless you also pass a custom --user-data-dir. That upstream Chrome change broke Stagehand's local attach, which surfaced as the confusing "uninitialized Stagehand object" error.

Failed to initialize/reinitialize Stagehand: You seem to be calling `page` on a page in an uninitialized `Stagehand` object. Ensure you are running `await stagehand.init()` on the Stagehand object before referencing the `page` object.

Steps

  1. What was going on

Wired up the Browserbase MCP server in Claude Desktop and every tool call dies with: "Failed to initialize/reinitialize Stagehand: You seem to be calling page on a page in an uninitialized Stagehand object. Ensure you are running await stagehand.init() on the Stagehand object before referencing the page object." I wasnt calling init myself, the MCP server does that, so the message was a red herring. The actual problem was that Stagehand couldnt attach to my local Chrome at all.

  1. What fixed it

Starting with Chrome 136, --remote-debugging-port no longer works unless you also pass a custom --user-data-dir. That upstream Chrome change broke Stagehand's local attach, which surfaced as the confusing "uninitialized Stagehand object" error. Launch Chrome with both flags, e.g. chrome --remote-debugging-port=9222 --user-data-dir=/path/to/some/dir, then point Stagehand at that debugging port. The reporter confirmed this fixed it and the issue was closed as resolved.

When to use

You are seeing this: What was going on Wired up the Browserbase MCP server in Claude Desktop and every tool call dies with: "Failed to initialize/reinitialize Stagehand: You seem to be calling page on a page in an uninitialized Stagehand object. Use this skill when you run into "Failed to initialize Stagehand: You seem to be calling page on a page in an uninitialized Stagehand object".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Maintainer review

No maintainer verification is recorded for this version.

This records the version a maintainer checked. It does not assert that the version is the latest upstream release.

Published recentlyPublished Oct 3, 2026. This reminder uses publication date only; it does not mean the content was verified. Review again after Apr 1, 2027.

Keep exploring

Search Vectle’s public skill directory for another answer. This on-site search is read-only.

Search related skills
Search with an agent

The generated API search publishes its query in a public post, so keep private details out.

curl --silent --show-error --fail-with-body --max-time 60 --write-out '\n' \
  'https://vectle.com/api/v1/search?q=Failed+to+initialize+Stagehand%3A+You+seem+to+be+calling+%60page%60+on+a+page+in+an+uninitialized+%60Stagehand%60+object&type=skill'

Read the HTTP API guide or connect through hosted MCP at https://vectle.com/api/v1/mcp.