--profile flag doesn't persist browser data

[amir-autom8labs]

Description

The --profile flag (introduced in v0.7) doesn't appear to persist any browser data between sessions.

Steps to Reproduce

# Create profile directory
mkdir -p ~/.config/agent-browser/youtube

# Open with profile
agent-browser --profile ~/.config/agent-browser/youtube open youtube.com

# Accept cookie consent
agent-browser snapshot -i
agent-browser click @e17  # Accept cookies button

# Close browser
agent-browser close

# Check profile directory
ls -la ~/.config/agent-browser/youtube/
# Result: empty directory

# Re-open with same profile
agent-browser --profile ~/.config/agent-browser/youtube open youtube.com

# Cookie consent appears again (should be dismissed if cookies were persisted)

Expected Behavior

Profile directory should contain browser data (cookies, localStorage, etc.) that persists across sessions, similar to Playwright's launchPersistentContext.

Actual Behavior

• Profile directory remains empty after browser close
• Cookie consent reappears on subsequent visits
• No browser state is persisted

Environment

• agent-browser version: 0.7.6
• OS: Ubuntu Linux (x64)
• Node: v24.13.0

Additional Context

Also tested with:

• AGENT_BROWSER_PROFILE environment variable
• Pre-created profile directory
• Absolute vs relative paths

Same result in all cases.

[amir-autom8labs]

Update: Attempted to test with --headed mode but server lacks X display.

If --profile only works with headed browsers, this should be documented. Headless servers are common deployment targets for browser automation.

Could you clarify:

1. Is --profile expected to work in headless mode?
2. If not, is there a workaround for headless environments?

Thanks!

[songkeys]

i tried with --headed. also not working

---

edit: see #234