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
Agent console/network diagnostics and controlled CDP access are missing.
Implementation order
Browser backlog item 21 of 29. Phase: Settings and developer features. This is ordered planning, not a claim that Codex implements every item. Items 24–29 are optional additions.
Acceptance criteria
Begin with bounded console/network diagnostic operations and explicit debugging permission.
Define credential redaction, task/tab ownership and interaction with vault availability.
Broader CDP access requires a separate reviewed design; do not expose unrestricted access by default.
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 the first supported #25 slice in 52b4bd463f4fdeab662a84a9f7d8b78b011c0eda (feat(browser): add scoped console diagnostics).
browser_observe_console now counts future Chromium console events by severity for one opted-in task-owned tab over a 250–5,000 ms interval. It requires read permission, separate named Ask approval, and fresh default-cancel native consent. Main binds the exact session, tab, source, access, owner, and task epochs through preparation, approval, observation, and final delivery.
The result contains counts only. Production does not read, retain, log, or return console messages, arguments, source URLs, lines, stacks, request data, credentials, vault data, or network activity. It does not attach CDP. Navigation, revocation, task/window changes, registration replacement, cancellation, deadline, or policy changes fail closed and remove the listener.
Verification on Windows / Electron 42.3.3 / Chromium 148.0.7778.218:
normal push hook: 31/31 typecheck tasks passed (28 cached)
This issue remains open. Network diagnostics are deliberately unsupported because the available Electron navigation events do not truthfully represent fetch/XHR health, and broader CDP remains behind the required separate reviewed design. Physical consent/accessibility, packaged app, macOS/Linux, authenticated-site, localization, and external security assurance are also unverified.
Local-only checkpoint, 2026-09-19: the approved bounded network-counts slice is implemented and verified in the browser-tabs worktree based on 4536d8d. It remains uncommitted and unpushed; no build was deployed or installed process restarted. The separate local #34 vault fix is preserved.
browser_observe_network({tabID, durationMs}) counts HTTP(S) Fetch/XHR terminal events received during an approved 250-5000 ms window (default 3000). It requires ordinary read permission, separate named network approval seeded to Ask, and fresh default-cancel network-specific native consent. Main checks exact session/tab/source/access/owner/task authority through collection and final delivery. Diagnostics neither require nor grant vault access; console consent is not network consent.
Only exact live main-frame/WebContents attribution is eligible. Electron may attribute dedicated-worker traffic to an ancestor, and already-in-flight requests may complete during the window. Cache/service-worker coverage is incomplete; zero counts are not a page-health verdict. The result contains status-class and transport/abort failure counts, not request URLs, referrers, headers, bodies, cookies, credentials or raw errors. There is no request history or CDP attachment. A Session-owned dispatcher preserves overlapping observers and removes native handlers after the last observer; source inspection found no competing registrations for these event slots.
Verification:
Desktop typecheck and full suite: 533 pass, 1 skip, 0 fail; 3691 expectations.
App typecheck and native-i18n tests: 11 pass, 471 expectations.
Earlier cm-browser typecheck, 88 tests and bundle build passed; plugin source was unchanged by the final review fixes.
Focused native diagnostics and then one full native smoke passed sequentially on Windows / Electron 44.3.0 / Chromium 152.0.7977.78.
Native collector fixtures cover Fetch/XHR, HTTP classes, final redirect response, transport failure, abort, tab/child-frame exclusion, shared-Session cancellation, preexisting in-flight completion and changed-source rejection. Consent/router/bridge authority and final-delivery races have synthetic unit coverage, not a new physical network-consent end-to-end demonstration.
Scoped root oxlint: 175 warnings, 0 errors across 24 changed code files. Formatting and git diff --check passed.
Independent Standards review findings were fixed: localized the generic failure without changing English and replaced status-class else branches with early returns; added a translated-error sanitization regression. The independent Spec worker failed to start; parent source review is not an independent security audit.
The full native smoke emitted ERR_EMPTY_RESPONSE from its fixture, a Mojo Widget diagnostic and an ObserverList reentrancy check diagnostic despite completing successfully. This is not warning-free or crash-free assurance.
Updated packages/cm-browser/README.md records the exact scope and evidence. #25 remains open: this checkpoint does not establish publication/build inclusion, physical network-consent usability/accessibility, cross-origin/OOPIF or worker attribution fixtures, packaged/macOS/Linux behavior, authenticated third-party sites, reviewed translations or external security assurance. Dependencies #11 and #14 are not declared closed by this work. Broader CDP still requires a separate reviewed design.
Implemented and published on browser-tabs: c7efee8 (bounded network diagnostics), alongside the existing scoped console implementation. Remote branch verified at d282cc2; worktree clean.
Acceptance check:
Bounded console and HTTP(S) Fetch/XHR terminal-event counts with ordinary read permission, separate named debugging approvals and fresh default-cancel native consent.
Credential redaction by construction: count-only collection/output, no message/request payloads or raw errors. Exact task/tab/source/access/owner authority is checked through final delivery. Diagnostics neither require nor grant vault authority.
No unrestricted CDP access. Broader CDP remains conditional on a separate reviewed design.
Publication checks: desktop typecheck; 181 focused collector/router/bridge/driver/provider tests (1681 expectations); real isolated native console/network diagnostics; cm-browser typecheck, 88 tests (3643 expectations) and bundle build; README formatting and staged whitespace checks all passed. Normal push hooks passed 31/31 typecheck tasks, none cached. Earlier combined-tree verification and review limitations remain recorded in the preceding checkpoint and README; the independent Spec worker did not complete, so no independent security audit is claimed.
Closing the bounded implementation scope against the recorded acceptance criteria, which require synthetic fixtures and documented platform limitations. This supersedes the earlier local-only/open checkpoint, not its evidence limits. Physical network-consent/accessibility, packaged and cross-platform behavior, real authenticated sites and reviewed translations are unverified. OOPIF/worker attribution needs further fixtures; cache/service-worker completeness is explicitly not supported, and zero counts are not a page-health verdict. Platform/authenticated validation remains under #19; password-manager release assurance remains under #34. Dependencies #11 and #14 are not closed by this action.
Source publication and the plugin build are not an installed-app release, deployment or packaged-build validation. No installed app/server/bridge was restarted.
Activity
trmosala commentedon Sep 18, 2026
Published the first supported #25 slice in
52b4bd463f4fdeab662a84a9f7d8b78b011c0eda(feat(browser): add scoped console diagnostics).browser_observe_consolenow counts future Chromium console events by severity for one opted-in task-owned tab over a 250–5,000 ms interval. It requires read permission, separate named Ask approval, and fresh default-cancel native consent. Main binds the exact session, tab, source, access, owner, and task epochs through preparation, approval, observation, and final delivery.The result contains counts only. Production does not read, retain, log, or return console messages, arguments, source URLs, lines, stacks, request data, credentials, vault data, or network activity. It does not attach CDP. Navigation, revocation, task/window changes, registration replacement, cancellation, deadline, or policy changes fail closed and remove the listener.
Verification on Windows / Electron 42.3.3 / Chromium 148.0.7778.218:
--diagnostics, and one serial default native smoke passedThis issue remains open. Network diagnostics are deliberately unsupported because the available Electron navigation events do not truthfully represent fetch/XHR health, and broader CDP remains behind the required separate reviewed design. Physical consent/accessibility, packaged app, macOS/Linux, authenticated-site, localization, and external security assurance are also unverified.
trmosala commentedon Sep 19, 2026
Local-only checkpoint, 2026-09-19: the approved bounded network-counts slice is implemented and verified in the browser-tabs worktree based on 4536d8d. It remains uncommitted and unpushed; no build was deployed or installed process restarted. The separate local #34 vault fix is preserved.
browser_observe_network({tabID, durationMs})counts HTTP(S) Fetch/XHR terminal events received during an approved 250-5000 ms window (default 3000). It requires ordinary read permission, separate named network approval seeded to Ask, and fresh default-cancel network-specific native consent. Main checks exact session/tab/source/access/owner/task authority through collection and final delivery. Diagnostics neither require nor grant vault access; console consent is not network consent.Only exact live main-frame/WebContents attribution is eligible. Electron may attribute dedicated-worker traffic to an ancestor, and already-in-flight requests may complete during the window. Cache/service-worker coverage is incomplete; zero counts are not a page-health verdict. The result contains status-class and transport/abort failure counts, not request URLs, referrers, headers, bodies, cookies, credentials or raw errors. There is no request history or CDP attachment. A Session-owned dispatcher preserves overlapping observers and removes native handlers after the last observer; source inspection found no competing registrations for these event slots.
Verification:
The full native smoke emitted ERR_EMPTY_RESPONSE from its fixture, a Mojo Widget diagnostic and an ObserverList reentrancy check diagnostic despite completing successfully. This is not warning-free or crash-free assurance.
Updated packages/cm-browser/README.md records the exact scope and evidence. #25 remains open: this checkpoint does not establish publication/build inclusion, physical network-consent usability/accessibility, cross-origin/OOPIF or worker attribution fixtures, packaged/macOS/Linux behavior, authenticated third-party sites, reviewed translations or external security assurance. Dependencies #11 and #14 are not declared closed by this work. Broader CDP still requires a separate reviewed design.
feat(browser): add bounded network diagnostics
trmosala commentedon Sep 19, 2026
Implemented and published on browser-tabs: c7efee8 (bounded network diagnostics), alongside the existing scoped console implementation. Remote branch verified at d282cc2; worktree clean.
Acceptance check:
Publication checks: desktop typecheck; 181 focused collector/router/bridge/driver/provider tests (1681 expectations); real isolated native console/network diagnostics; cm-browser typecheck, 88 tests (3643 expectations) and bundle build; README formatting and staged whitespace checks all passed. Normal push hooks passed 31/31 typecheck tasks, none cached. Earlier combined-tree verification and review limitations remain recorded in the preceding checkpoint and README; the independent Spec worker did not complete, so no independent security audit is claimed.
Closing the bounded implementation scope against the recorded acceptance criteria, which require synthetic fixtures and documented platform limitations. This supersedes the earlier local-only/open checkpoint, not its evidence limits. Physical network-consent/accessibility, packaged and cross-platform behavior, real authenticated sites and reviewed translations are unverified. OOPIF/worker attribution needs further fixtures; cache/service-worker completeness is explicitly not supported, and zero counts are not a page-health verdict. Platform/authenticated validation remains under #19; password-manager release assurance remains under #34. Dependencies #11 and #14 are not closed by this action.
Source publication and the plugin build are not an installed-app release, deployment or packaged-build validation. No installed app/server/bridge was restarted.