feat(browser): pass profile_id to Browser Use API for session persistence - #6585
Closed
el-analista wants to merge 1 commit into
Closed
el-analista wants to merge 1 commit into
el-analista wants to merge 1 commit into
Conversation
…ence Read browser_use.profile_id from config.yaml (or BROWSER_USE_PROFILE_ID env var) and include it in the /browsers create payload. This enables persistent sessions with stored cookies/login state via Browser Use cloud profiles.
Contributor
Author
|
This will allow to use browser-use profile feature where you can log in pages so that when agent uses the profile id session persists |
Contributor
Author
|
Closing — superseded by #4419 which implements persistent browser sessions via managed_persistence + stable userId. |
alt-glitch
added
type/feature
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
browser_use.profile_idfromconfig.yaml(orBROWSER_USE_PROFILE_IDenv var) and include it in the/browserscreate payloadContext
The
browser.browser_use.profile_idconfig key was already accepted byhermes setup toolsbut never actually read byBrowserUseProvider. This wires it through so session persistence works as expected.Test plan
browser.browser_use.profile_idin config.yaml, verify it appears in the/browsersPOST payloadBROWSER_USE_PROFILE_IDenv var, verify env var takes precedence