Skip to content

Open-source Python library for AI browser agents, plus Browser Use Cloud: stealth browsers and a hosted agent API.

update docs for profile-use integration and ~/.browser-use/ directory layout

ShawnPana43e007238c99
diff --git a/browser_use/skill_cli/README.md b/browser_use/skill_cli/README.md
index 0c905359f..d3b48040f 100644
--- a/browser_use/skill_cli/README.md
+++ b/browser_use/skill_cli/README.md
@@ -259,11 +259,19 @@ browser-use open https://abc.trycloudflare.com
## Profile Management
-### Local Profiles
+The `profile` subcommand delegates to the [profile-use](https://github.com/browser-use/profile-use) Go binary, which syncs local browser cookies to Browser-Use cloud.
+
+The binary is managed at `~/.browser-use/bin/profile-use` and auto-downloaded on first use.
+
| Command | Description |
|---------|-------------|
-| `profile list` | List Chrome profiles |
-| `profile cookies <name>` | Show cookies by domain |
+| `profile` | Interactive sync wizard |
+| `profile list` | List detected browsers and profiles |
+| `profile sync --all` | Sync all profiles to cloud |
+| `profile sync --browser "Google Chrome" --profile "Default"` | Sync specific profile |
+| `profile auth --apikey <key>` | Set API key (shared with `cloud login`) |
+| `profile inspect --browser "Google Chrome" --profile "Default"` | Inspect cookies locally |
+| `profile update` | Download/update the profile-use binary |
## Session Management
@@ -355,11 +363,28 @@ The CLI uses a multi-session daemon architecture:
1. First command starts a background daemon for that session (browser stays open)
2. Subsequent commands communicate via Unix socket (or TCP on Windows)
3. Browser persists across commands for fast interaction
-4. Each `--session` gets its own daemon, socket, and PID file in `~/.browser-use/run/`
+4. Each `--session` gets its own daemon, socket, and PID file in `~/.browser-use/`
5. Daemon auto-starts when needed, auto-exits when browser dies, or stops with `browser-use close`
This gives you ~50ms command latency instead of waiting for browser startup each time.
+### File Layout
+
+All CLI-managed files live under `~/.browser-use/` (override with `BROWSER_USE_HOME`):
+
+```
+~/.browser-use/
+├── config.json # API key, settings (shared with profile-use)
+├── bin/
+│ └── profile-use # Managed Go binary (auto-downloaded)
+├── tunnels/
+│ ├── {port}.json # Tunnel metadata
+│ └── {port}.log # Tunnel logs
+├── default.sock # Daemon socket (ephemeral)
+├── default.pid # Daemon PID (ephemeral)
+└── cli.log # Daemon log
+```
+
<details>
<summary>Windows Troubleshooting</summary>
diff --git a/skills/browser-use/SKILL.md b/skills/browser-use/SKILL.md
index c15fea537..c1f49299f 100644
--- a/skills/browser-use/SKILL.md
+++ b/skills/browser-use/SKILL.md
@@ -203,11 +203,16 @@ browser-use close # Close browser session
### Profile Management
-#### Local Chrome Profiles
+Manages browser profiles via the profile-use Go binary (auto-downloaded to `~/.browser-use/bin/`).
+
```bash
-browser-use profile list # List local Chrome profiles
-browser-use profile get "Default" # Get profile details
-browser-use profile cookies "Default" # Show cookie domains in profile
+browser-use profile # Interactive sync wizard
+browser-use profile list # List detected browsers and profiles
+browser-use profile sync --all # Sync all profiles to cloud
+browser-use profile sync --browser "Google Chrome" --profile "Default" # Sync specific
+browser-use profile auth --apikey <key> # Set API key (shared with cloud login)
+browser-use profile inspect --browser "Google Chrome" --profile "Default" # Inspect locally
+browser-use profile update # Download/update profile-use binary
```
## Common Workflows
@@ -227,8 +232,8 @@ Use when a task requires browsing a site the user is already logged into (e.g. G
```bash
browser-use profile list
-# → Default: Person 1 ([email protected])
-# → Profile 1: Work ([email protected])
+# → Google Chrome - Person 1 (Default)
+# → Google Chrome - Work (Profile 1)
```
#### Step 2: Browse with the chosen profile
@@ -242,10 +247,8 @@ The user is already authenticated — no login needed.
#### Check what cookies a profile has
```bash
-browser-use profile cookies "Default"
-# → youtube.com: 23
-# → google.com: 18
-# → github.com: 2
+browser-use profile inspect --browser "Google Chrome" --profile "Person 1"
+# Shows cookie domains and counts
```
### Connecting to an Existing Chrome Browser