feat(vercel-labs/agent-browser): scaffold vercel-labs/agent-browser

[iwata]

Check List

• Read CONTRIBUTING.md
  • ⚠️ Avoid force push
  • ⚠️ Use argd s command when adding new packages
• Install and execute the package and confirm if the package works well

Summary by CodeRabbit

• Chores
  • Added package registry configuration for vercel-labs/agent-browser supporting multiple versions (v0.21.2, v0.20.1, v0.7.0) with platform-specific asset handling and version-specific download rules.

[coderabbitai]

📝 Walkthrough

Walkthrough

Three new configuration files were added to declare and register the vercel-labs/agent-browser package. The entries define multiple version pins, specify GitHub release asset patterns, and configure version-specific download rules with OS/architecture normalization for different release versions.

Changes

Cohort / File(s)	Summary
Agent Browser Package Configuration pkgs/vercel-labs/agent-browser/pkg.yaml, pkgs/vercel-labs/agent-browser/registry.yaml	Added package manifest with version pins (v0.21.2, v0.20.1, v0.7.0) and registry configuration defining GitHub release asset selection, version-specific overrides, and OS/architecture replacements (amd64→x64, windows→win32).
Root Registry registry.yaml	Added main registry entry for vercel-labs/agent-browser with conditional version overrides specifying asset patterns and a musl-variant override for Linux amd64.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

enhancement

Poem

🐰 Hop along, dear packages new,
Agent Browser, we declare you true—
GitHub releases, versions galore,
With platforms mapped to what we adore,
Registry entries, configured with care!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: scaffolding a new vercel-labs/agent-browser package entry in the registry.
Description check	✅ Passed	The description follows the required template with all checklist items marked complete, indicating the author has read CONTRIBUTING.md and tested the package.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@registry.yaml`:
- Around line 90258-90259: The registry entry currently sets no_asset: true for
the version_constraint semver("<= 0.7.4"), which incorrectly blocks asset
downloads for versions 0.7.2–0.7.4; update that YAML by either removing the
no_asset: true override entirely or tighten the constraint to only match
versions that truly lack assets (for example change version_constraint to
semver("<= 0.7.1") while keeping no_asset: true), ensuring the keys involved are
the version_constraint and no_asset fields in this registry entry.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: bfdf7227-da8d-468b-aa44-841fb6b8d4f0

📥 Commits

Reviewing files that changed from the base of the PR and between 57f9dbc and ed474eb.

📒 Files selected for processing (3)

• pkgs/vercel-labs/agent-browser/pkg.yaml
• pkgs/vercel-labs/agent-browser/registry.yaml
• registry.yaml

[suzuki-shunsuke]

Thank you!