This repository was archived by the owner on Nov 7, 2026. It is now read-only.
Repository navigation
fix(recording): point tab-capture permission failures at click-free CDP recording - #106
Merged
Merged
Conversation
kitlangton
force-pushed
the
fix/tab-capture-hint
branch
from
October 25, 2026 22:37
c8cfbdb to
80a3001
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
An agent recording a Browser Control-owned preview tab forced
--mode tab-captureand gotExtension has not been invoked for the current page (see activeTab permission)… Click the Browser Control extension icon on this tab once before recording.The hint implied a person had to click before every recording, even though CDP recording works on any debugger-attached tab without a click (and--mode autoalready picks it for relay-owned tabs).What Changes
Before:
…Click the Browser Control extension icon on this tab once before recording.After:
…Chrome only allows tab capture after you click the Browser Control extension icon on this tab. To record without a click, use --mode cdp (the auto default for Browser Control-owned tabs).The skill's Recording section now says the click is a Chrome rule that no extension permission removes, and points agent-run recordings at CDP, noting its encode cost.
Scope
Message and docs only; capture behavior is unchanged.
Verification
The typecheck is clean, and the built
background.jscontains the new message. For the cost figure, I encoded 20s of 15 fps 1440x900 with the CDP pipeline's ffmpeg settings: x264veryfasttook 4.2s user CPU and libvpx 4.7s, about a quarter of one core while recording.