[STG-1733] fix: use valid metadata key for browse-cli sessions

[derekmeegan]

Summary

• The browse-cli metadata key (with hyphen) is rejected by the Browserbase API as an invalid metadata key, causing env remote to fail with a 400 Key is not a valid metadata key: browse-cli error.
• Changed the key to browse_cli (underscore) which is a valid metadata key format.

Linear: https://linear.app/browserbase/issue/STG-1733/fix-use-valid-metadata-key-for-browse-cli-sessions

Test plan

• Verified old key (browse-cli) returns 400 from Browserbase API
• Verified new key (browse_cli) returns 201 and session creates successfully

🤖 Generated with Claude Code

[changeset-bot]

🦋 Changeset detected

Latest commit: d2cade9

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[cubic-dev-ai]

1 issue found across 1 file

Confidence score: 5/5

• This PR appears low risk to merge because the only noted item is a low-severity (3/10) request for additional regression-test coverage, not a reported functional break.
• The key follow-up is to add a regression test in packages/cli/src/index.ts to lock in the browse_cli remote-session metadata behavior and protect API compatibility over time.
• Pay close attention to packages/cli/src/index.ts - ensure the browse_cli metadata key behavior is explicitly covered by a regression test.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/cli/src/index.ts">

<violation number="1" location="packages/cli/src/index.ts:702">
P3: Add a regression test for the remote session creation metadata key (`browse_cli`) so this API-compatibility fix is enforced.

(Based on your team's feedback about adding unit tests for new behavior.) [FEEDBACK_USED]</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[shrey150]

@derekmeegan can you add a patch changeset here so it causes a version bump?