Context-aware suggestions can trigger Chrome DevTools remote debugging prompt

Summary

Codex Desktop appears to run a hidden/context-aware suggestions task that initializes chrome-devtools-mcp --autoConnect, which can trigger a Chrome remote debugging permission prompt even when the user has not started a visible task that needs Chrome.

This is surprising from a privacy/permission standpoint because the popup appears after the visible user task has ended, and the user cannot tell which Codex task is requesting Chrome access.

Environment

• Codex Desktop: 26.623.31443, build 4441
• macOS: 26.5.1 (25F80)
• Chrome DevTools MCP configured in ~/.codex/config.toml

Relevant MCP config shape:

[mcp_servers.chrome-devtools]
type = "stdio"
command = "npx"
args = ["-y", "chrome-devtools-mcp@latest", "--autoConnect"]

What happened

1. A visible Codex task had already finished.
2. A Chrome remote debugging permission prompt appeared later.
3. Local Codex logs showed a hidden/background thread running at the same time with a prompt beginning:

``text
Generate 0 to 3 hyperpersonalized suggestions for what this user can do with Codex in this local project...
``

1. At the same timestamp, the Codex app server launched:

``text
npm exec chrome-devtools-mcp@latest --autoConnect
``

1. This matched the Chrome remote debugging permission prompt.

Expected behavior

• Context-aware/ambient suggestions should not auto-initialize privacy-sensitive MCP servers such as Chrome DevTools unless the user explicitly starts a task that needs them.
• If Codex does need Chrome access, the permission prompt should identify the requesting Codex feature/task clearly, especially when the requester is a hidden/background task.
• There should be an obvious way in Codex Desktop settings to disable context-aware suggestions or prevent them from initializing MCP servers.

Actual behavior

• A hidden suggestions task initialized Chrome DevTools MCP with --autoConnect.
• The resulting Chrome permission prompt was not clearly attributable to the hidden suggestions task.
• The user could not find the documented "Context-aware suggestions" setting in the current Codex Desktop UI.

Why this matters

Chrome remote debugging can expose sensitive browser state. A background suggestion feature should not surprise users by initiating this access path without a clear, visible user action and attribution.

Suggested fix

• Do not start MCP servers for hidden/context-aware suggestions by default, or at least exclude browser-control MCP servers from background suggestion tasks.
• Show the source task/feature in permission prompts.
• Add a clear Codex Desktop setting for disabling context-aware suggestions and/or background MCP initialization.