You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User screenshot-to-chat exists; the agent plugin has no screenshot operation.
Implementation order
Browser backlog item 11 of 29. Phase: Agent browsing. This is ordered planning, not a claim that Codex implements every item. Items 24–29 are optional additions.
Acceptance criteria
Add bounded screenshots for explicitly opted-in task-owned tabs.
Enforce access and navigation checks at capture/delivery; define output size and sensitive-data semantics.
Verify private tabs cannot be captured and revocation invalidates pending captures.
Reuse existing Chromium/Electron/OS facilities where available. Preserve main-process ownership and permission enforcement, add no placeholder controls, use existing i18n patterns, and test behavior with synthetic fixtures. Document platform limitations. Baseline: browser-tabs at 47fef3e; see packages/cm-browser/README.md and password-security.md.
Published bounded screenshot implementation in 564ccd1 on browser-tabs, based on af5842e. Exactly 18 task files; normal push with hooks, 31/31 typecheck tasks passed (28 cached), remote SHA verified. Excluded work and CM_GPT6_Astra_High unchanged; no installed-process restart, release or deployment.
Separate source/access-bound plugin approval plus default-cancel native consent per capture. Fixed viewport JPEG, quality 60; 4096/edge, 4194304 pixels, 46080 JPEG bytes, 61440 base64 characters, and authoritative 65536-byte complete response limit. Image attachment only; visible passwords/editable values/canvas/cross-origin pixels are deliberately unredacted with explicit disclosure. Original task/registration/owner lifecycle/source/access/policy/cancel/deadline authority is rechecked through synchronous IPC post. Busy/rendering and correlation ownership survive early cancellation until actual native settlement; no retries.
Independent cumulative correctness/spec and standards reviews cleared all 18 files. Review reproduced stale pixels after owner hide/restore; fixed by retaining original owner epoch through delivery. Final focused screenshot fixture passed 22 capture/post rejection cases, real JPEG/pixel/bounds/zoom/DPR checks and real Windows dialog abort. Renderer navigation/crash cases use synthetic events through production hooks, not real crashes. Parent final browser suite: 147 passed / 2140 expectations. cm-browser: 63 passed / 514 expectations. Native i18n: 9 passed. Desktop/app/cm-browser typechecks and final default full native smoke passed. Scoped formatting/whitespace passed; correction lint 21 warnings, zero errors, not warning-free.
Issue remains OPEN for detached-background capture (documented timeout LIMIT; selected-covered capture passes), physical/accessibility, packaged/unmodified occlusion, macOS/Linux and localization/assurance gates. Detached capture can retain busy/rendering until manual reattachment or closure settles it. Raster bounds are postdecode, not a preallocation guarantee. Existing unrelated root lint error was not repaired or rerun. Full evidence: packages/cm-browser/README.md and password-security.md. Next ordered slice: #16.
Completed #15 follow-up and pushed fd8ac9d (fix(browser): reject detached screenshot captures) to browser-tabs. The screenshot feature already existed in 564ccd1; this change closes the known detached-start stall. Dependency #11 is closed.
Main now requires the selected tab and actual native view attachment before consent and through capture/delivery. Detached requests produce zero native prompts/capture calls and release busy state without reattachment. Switching or detaching during held capture/post rejects image delivery. Already-dispatched native work still retains its leases until actual settlement. Tool documentation explains that background tabs must be selected first. Existing task ownership, opt-in, native per-capture consent, navigation/revocation checks and byte/raster bounds remain intact; visible sensitive pixels remain explicitly unredacted.
Validation on macOS arm64 / Electron 44.3.0 / Chromium 152.0.7977.78:
Final focused --screenshots PASS: 26 capture/post rejection cases, zero-consent/capture detached rejection, busy release, real JPEG/pixel/size/zoom/DPR checks.
Both package typechecks PASS; normal push hook 31/31 successful (29 cached).
Formatting/whitespace PASS; scoped lint 71 warnings, zero errors.
Independent standards and correctness/spec reviews found no actionable issues.
The screenshot fixture pins sRGB so synthetic swatches are independent of the host display profile; production color behavior is unchanged. Its hide test now waits for the native event. One intermediate focused rerun exhausted the harness after post owner-crash; the cause remains unestablished. A diagnostic repeat and final focused run passed. Hold setup now reports an operation that completes before the hold rather than waiting indefinitely, with fixture-only cleanup. The default suite retains the previously documented Chromium observer-list diagnostic. No native copy/locale implementation changed; the unrelated pa-PK i18n failure from #17 was not rerun.
Physical/accessibility, packaged/unmodified occlusion, Linux, localization and external assurance remain separate work. Closing the bounded selected-tab screenshot acceptance criteria; this does not claim background capture or recall of already-posted attachments. Evidence and limits are recorded in packages/cm-browser/README.md and password-security.md.
Activity
trmosala commentedon Sep 16, 2026
Published bounded screenshot implementation in 564ccd1 on browser-tabs, based on af5842e. Exactly 18 task files; normal push with hooks, 31/31 typecheck tasks passed (28 cached), remote SHA verified. Excluded work and CM_GPT6_Astra_High unchanged; no installed-process restart, release or deployment.
Separate source/access-bound plugin approval plus default-cancel native consent per capture. Fixed viewport JPEG, quality 60; 4096/edge, 4194304 pixels, 46080 JPEG bytes, 61440 base64 characters, and authoritative 65536-byte complete response limit. Image attachment only; visible passwords/editable values/canvas/cross-origin pixels are deliberately unredacted with explicit disclosure. Original task/registration/owner lifecycle/source/access/policy/cancel/deadline authority is rechecked through synchronous IPC post. Busy/rendering and correlation ownership survive early cancellation until actual native settlement; no retries.
Independent cumulative correctness/spec and standards reviews cleared all 18 files. Review reproduced stale pixels after owner hide/restore; fixed by retaining original owner epoch through delivery. Final focused screenshot fixture passed 22 capture/post rejection cases, real JPEG/pixel/bounds/zoom/DPR checks and real Windows dialog abort. Renderer navigation/crash cases use synthetic events through production hooks, not real crashes. Parent final browser suite: 147 passed / 2140 expectations. cm-browser: 63 passed / 514 expectations. Native i18n: 9 passed. Desktop/app/cm-browser typechecks and final default full native smoke passed. Scoped formatting/whitespace passed; correction lint 21 warnings, zero errors, not warning-free.
Issue remains OPEN for detached-background capture (documented timeout LIMIT; selected-covered capture passes), physical/accessibility, packaged/unmodified occlusion, macOS/Linux and localization/assurance gates. Detached capture can retain busy/rendering until manual reattachment or closure settles it. Raster bounds are postdecode, not a preallocation guarantee. Existing unrelated root lint error was not repaired or rerun. Full evidence: packages/cm-browser/README.md and password-security.md. Next ordered slice: #16.
trmosala commentedon Sep 22, 2026
Completed #15 follow-up and pushed fd8ac9d (fix(browser): reject detached screenshot captures) to browser-tabs. The screenshot feature already existed in 564ccd1; this change closes the known detached-start stall. Dependency #11 is closed.
Main now requires the selected tab and actual native view attachment before consent and through capture/delivery. Detached requests produce zero native prompts/capture calls and release busy state without reattachment. Switching or detaching during held capture/post rejects image delivery. Already-dispatched native work still retains its leases until actual settlement. Tool documentation explains that background tabs must be selected first. Existing task ownership, opt-in, native per-capture consent, navigation/revocation checks and byte/raster bounds remain intact; visible sensitive pixels remain explicitly unredacted.
Validation on macOS arm64 / Electron 44.3.0 / Chromium 152.0.7977.78:
The screenshot fixture pins sRGB so synthetic swatches are independent of the host display profile; production color behavior is unchanged. Its hide test now waits for the native event. One intermediate focused rerun exhausted the harness after post owner-crash; the cause remains unestablished. A diagnostic repeat and final focused run passed. Hold setup now reports an operation that completes before the hold rather than waiting indefinitely, with fixture-only cleanup. The default suite retains the previously documented Chromium observer-list diagnostic. No native copy/locale implementation changed; the unrelated pa-PK i18n failure from #17 was not rerun.
Physical/accessibility, packaged/unmodified occlusion, Linux, localization and external assurance remain separate work. Closing the bounded selected-tab screenshot acceptance criteria; this does not claim background capture or recall of already-posted attachments. Evidence and limits are recorded in packages/cm-browser/README.md and password-security.md.