Desktop activity card misattributes Codex Security tools to Linear integration

What issue are you seeing?

In the macOS Codex desktop app, Codex Security tool calls are displayed in the task activity UI as “Used Linear integration.” Expanding the activity card shows Codex Security operations rather than Linear operations.

Observed operation names:

• get_codex_security_scan_context
• get_codex_security_completed_scan
• get_codex_security_scan_context

The local session transcript attributes these calls to the codex-security MCP server and contains no linear_* tool call for the affected turn. A separate direct audit of the connected Linear workspace found no security-scan issue, comment, attachment, or other unexpected mutation.

This appears to be an activity-summary/provenance labeling problem. The label is concerning because it implies that an external Linear connection was accessed when the task only read Codex Security scan state.

What steps can reproduce the bug?

1. Use the macOS Codex desktop app with both the Codex Security and Linear plugins/integrations available.
2. In a Codex task, retrieve a completed Codex Security scan using the Security plugin’s scan-context/completed-scan tools.
3. Inspect the task’s activity cards.
4. Observe that the card says “Used Linear integration.”
5. Expand the card and observe that the listed operations are get_codex_security_scan_context and/or get_codex_security_completed_scan, not Linear operations.

The exact task/session identifier is available privately to OpenAI staff if needed. No screenshot or transcript is attached because the transcript may contain private project context.

What is the expected behavior?

Activity cards should attribute these calls to Codex Security (or to the exact MCP server/tool namespace), not Linear. The UI should not imply that Linear data was read or changed when no Linear tool was called.

Additional information

• Platform: macOS 27.0, Apple Silicon
• Surface: Codex in the desktop app
• Direct destination audit: no unexpected Linear changes found
• Public duplicate search performed before filing; no matching issue found

Start by reproducing the macOS desktop activity card with the Codex Security scan-context/completed-scan tools while Linear is also available. Trace how the activity summary maps MCP server and tool names to integration labels; done means Codex Security calls are labeled Codex Security or by their exact MCP namespace, with no Linear attribution when no linear_* tool ran.