[Dani Akash (DaniAkash)]

Why

Four content-changing PRs (#9 repo-rename refs, #10–#12 skill iterations) all shipped under version 0.2.0. Codex caches installed plugins by version (~/.codex/plugins/cache/browserclaw/browserclaw/0.2.0), so an existing 0.2.0 install that runs only codex plugin marketplace upgrade has no version signal to refresh and can keep serving the stale, pre-fix skill (the one that sent Codex to Playwright / reported the MCP "not connected").

A fresh codex plugin add re-fetches source, but per Codex's own installing-and-updating guidance we shouldn't rely on that — a version bump (or cachebuster) is the intended refresh mechanism.

Change

Bump both manifests 0.2.0 → 0.2.1:

• plugins/browserclaw/.codex-plugin/plugin.json
• plugins/browserclaw/package.json

No code change; the wrapper reads its version from package.json at runtime, so dist/wrapper.js is unchanged (verified: a rebuild produces no diff). The release workflow's tag-vs-manifest check covers both files, so a future v0.2.1 tag stays consistent.

After merge

Users refresh with:

codex plugin marketplace upgrade browserclaw
codex plugin add browserclaw@browserclaw

and a new thread.

[greptile-apps]

Greptile Summary

This PR releases BrowserClaw version 0.2.1. The changes are:

• Bump the Codex plugin manifest from 0.2.0 to 0.2.1.
• Bump the package manifest from 0.2.0 to 0.2.1.

Confidence Score: 5/5

This looks safe to merge.

• Both manifests use the same version.
• Runtime version reporting reads package.json directly.
• Release validation checks both manifests against the release tag.
• No blocking issues found in the changed code.

Important Files Changed

Filename	Overview
plugins/browserclaw/.codex-plugin/plugin.json	Updates the Codex plugin manifest version to 0.2.1.
plugins/browserclaw/package.json	Updates the runtime package version to 0.2.1; the wrapper reads this value dynamically.

_{Reviews (1): Last reviewed commit: "chore(release): 0.2.1" | Re-trigger Greptile}