· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Steven Wu v0.4.1
Record Codex Browser flows
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
$codex-browser-recorder:record-browser Check recording setup on this Mac.
Developer declarations; not independently tested. Listing last checked Nov 22, 2026. Package observed Nov 21, 2026.
From the marketplace listing
Check whether your Mac is ready, then record one short, approved Codex In-app Browser test flow as a private local MP4. Pointer actions include a visible cursor and click feedback. The plugin records no audio and does not upload your video.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →· 4 observations
Supporting files updated; open the comparison for details. Skill instructions changed from “Flow: ```js const acquireBrowser = async () => { if (globalThis.agent?.browsers == null) { const { setupBrowserRuntime } = await import("<Browser plugin...” to “Flow. `setupBrowserRuntime()` returns the Browser runtime; keep...
View comparison →Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →---
name: record-browser
description: Check setup or record one explicitly approved Codex In-app Browser flow as a private local MP4; pointer flows add a visible cursor and click feedback. Use only when the user explicitly invokes $codex-browser-recorder:record-browser.
---
# Record Browser
## Build A Local Plan
Collect the request without Browser activity:
- Set `preflightOnly` only for an explicit doctor, diagnose, check, or preflight request.
- For recording, require an HTTPS or approved loopback target plus either one or more concrete actions or an explicit passive duration.
- Treat the normalized target site as the approved origin for the whole recording.
- Set `durationWasExplicit` from the user's words. Use 15 seconds when omitted, but end after the last action and any bounded pointer-feedback tail. Require an explicit 5–60 second duration for passive or wait-only recording.
- Set `recordingMode` to `interactive` by default. Use `unattended` only when the user explicitly requests an unattended, headless-style, background-start, or automated E2E QA recording. Both modes use the Codex In-app Browser; do not describe Unattended Recording as a separate headless Chromium surface.
- Classify every action as `pointer`, `keyboard`, or `programmatic`. Pointer includes click, hover, drag, and pointer-positioned scroll.
- Accept an optional absolute destination and privacy-safe recording name. Otherwise use `~/Downloads/Codex Browser Recordings/` and a timestamp name.
Browser Recorder is content-neutral. Do not classify page content, redact visible
fields, or refuse an otherwise valid request based on authentication, privacy,
or sensitivity. It does not protect, mask, manage, or authenticate credentials
or sensitive content; anything visible in the approved viewport may appear in
the video.
Resolve the installed skill directory from the catalog entry that loaded this file. Never guess a cache path or use a source checkout. Import `checkSetup`, `prepareRecording`, and `recordApproved` from `scripts/record-browser-flow.mjs` in that exact directory with `pathToFileURL` in the persistent Node runtime.
Define each action before preparation. Its `perform({ tab })` function must contain exactly the approved Browser call. Labels must describe the approved action generically; do not copy page text, form values, or full URLs into consent or diagnostics.
```js
const plannedActions = [
// {
// label: "Open the pricing section",
// modality: "pointer",
// perform: ({ tab }) => tab.<exact approved Browser call>,
// },
];
const preparation = await prepareRecording({
actions: plannedActions,
destinationDirectory,
durationMs,
durationWasExplicit,
now: new Date(),
preflightOnly,
recordingMode,
recordingName,
targetUrl,
temporaryRoot,
});
```
`prepareRecording()` performs pure request validation plus local FFmpeg/FFprobe and destination checks. It must not create, navigate, or acquire a Browser tab or CDP capability. Treat the returned preparation as opaque: do not clone, spread, reconstruct, or mutate it.
Technical target restrictions remain content-independent: malformed URLs,
prohibited URL credentials, unsupported schemes, an unapproved origin, an
invalid duration, capture or encoding failure, media validation failure, and
incomplete cleanup remain deterministic Technical Blockers or terminal
failures.
If `status` is `blocked`, report every Technical Blocker in order using only its `code`, `summary`, and `remediation`, then stop. For `preflight_prepared`, continue only with the explicit setup-check path below. For `prepared`, continue to consent. Do not expose raw booleans.
## Complete The Setup Check
For `status: "preflight_prepared"`, follow the installed Browser control skill. Resolve its installed plugin root from its catalog entry, and pass one bounded Codex In-app Browser acquisition callback to the Recording Flow. `setupBrowserRuntime()` returns the Browser runtime; keep it in a local bindPreview of the first 4,000 characters. Read full instructions →
Referenced files: 14 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 21, 2026.
plugins_6a58f693814c8191b576ffaed4af2e78
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.