Stagehand initialization error: Cannot create proxy with a non-object as target or handler, and uninitialized page object #56
Assignees
Comments
|
Hey @djb4ai, the point of having that try catch block is to check if the session was properly created. Your PR basically voids the try catch checker. Would love to hear more of your thoughts on why this is needed. |
|
I have the same issue. I want to run locally to capture the traffic using burp suite. Any idea how to achieve this @Kylejeong2 ? Its possible to use firefox with LOCAL_CDP_URL? |
|
Hello, the fix for this issue is described here: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
When attempting to use Stagehand MCP with a local Chrome instance (CDP on port 9222), I encountered the following errors:
Cannot create proxy with a non-object as target or handler.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 to Reproduce
--remote-debugging-port=9222Solution
The issue was resolved by ensuring that
await stagehand.init()is called before any reference to thepageobject. In my case, the initialization was either missing or not awaited properly, causing the errors above. After adding and properly awaitingstagehand.init(), the errors were resolved and browser automation worked as expected.Suggestion
Consider adding clearer error messages or documentation to help users ensure proper initialization order, especially when using Stagehand in local mode.
Thank you for your work on this project!
The text was updated successfully, but these errors were encountered: