Skip to content

Conversation

@ianwatts22
Copy link

Summary

  • Adds the missing profile field to the launchSchema Zod validation schema in protocol.ts

Problem

The --profile flag was added in PR #68 to support persistent browser profiles, but the profile field was not added to the Zod schema in protocol.ts. This caused the profile option to be stripped during command parsing, making the feature non-functional.

Solution

Added profile: z.string().optional() to the launchSchema, allowing the profile path to be passed through to the browser launch options.

Test plan

  • Verified agent-browser --profile ~/.browser-profiles/test --headed open https://example.com creates profile directory
  • Verified cookies persist across browser restarts when using the same profile

🤖 Generated with Claude Code

The --profile flag was added in PR vercel-labs#68 but the profile field was missing
from the Zod validation schema in protocol.ts. This caused the profile
option to be stripped during command parsing, preventing persistent
browser profiles from working.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@vercel
Copy link
Contributor

vercel bot commented Jan 23, 2026

@ianwatts22 is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant