Problem with cookies injected with storage_state

The problem

Issue browser-use/browser-use#2799 (closed, 23 comments): ### Browser Use Version 0.6.1 ### LLM Model Other (specify in description) ### Screenshots, Description, and task prompt given to Agent I am using gpt-5. prompt: ``` """ 1. Navigate to the station status page: https://poc18.demo.dev.charge.ampeco.tech/admin/resources/evses/4. 2. Wait until the page is fully loaded. 3. Use the function 'clickactionsand_reset' to click the Actions button and the reset option 4. In the form that appears: - Enter "Soft" into the Type field. - Enter "Any" into the Reason field. - Click the "Run Action" button. 5. Wait 5 seconds for the station to restart. 6.

What to do

Inject the cookies through the browser session start event instead of setting them after launch. The confirmed workaround:

1. Hook BrowserStartEvent on your agent.
2. Wait for the CDP connection to be ready.
3. Call cdpset_cookies with your cookie list.
4. Keep the browser session alive across agent steps so the cookies persist.

Users confirmed the agent then runs authenticated. Setting cookies after the page loads does not stick, because the session resets.

In the GitHub issue gh:browser-use/browser-use#2799 (https://github.com/browser-use/browser-use/issues/2799), the problem reported was: Issue browser-use/browser-use#2799 (closed, 23 comments): ### Browser Use Version 0.6.1 ### LLM Model Other (specify in description) ### Screenshots, Description, and task prompt given to Agent I am using gpt-5. prompt: ``` """ 1. Navigate to the station status page: https://poc18.demo.dev.charge.ampeco.tech/admin/resources/evses/4. 2. Wait until the page is fully loaded. 3. Use the function 'clickactionsand_reset' to click the Actions button and the reset option 4. In the form that appears: - Enter "Soft" into the Type field. - Enter "Any" into the Reason field. - Click the "Run Action" button. 5. Wait 5 seconds for the station to restart. 6. The verified resolution was: Inject the cookies through the browser session start event instead of setting them after launch. The confirmed workaround:

1. Hook BrowserStartEvent on your agent.
2. Wait for the CDP connection to be ready.
3. Call cdpset_cookies with your cookie list.
4. Keep the browser session alive across agent steps so the cookies persist.

Users confirmed the agent then runs authenticated. Setting cookies after the page loads does not stick, because the session resets.