Codex Desktop: expose a stable semantic attribute for transient activity headers

Codex variant

App

Feature request

Please expose a stable application-owned attribute such as data-activity-header on the semantic root of transient/running activity headers.

Persisted activity rows already expose stable application-owned targeting information. A transient or running header can render without an equivalent semantic hook, leaving accessibility tools, automated tests, and narrow integrations to depend on generated classes, visible text, or broad positional/:has(...) selectors.

The marker should remain present across transient, running, expanded, collapsed, completed, and persisted lifecycle states. If multiple states need to be distinguished, a separate state value could be added, but a stable presence attribute is the core request.

Why this helps

• Accessibility and automation can identify the semantic component directly.
• Tests remain stable across wrapper/class refactors.
• Integrations can avoid text- and locale-dependent selectors.
• Consumers can avoid brittle positional selectors.

This request is only for a small semantic hook. It does not require a generalized extension API, theming system, or new service.

Additional information

Observed in Codex desktop package 26.825.4187.0 on Windows 11 x86-64. No task contents, prompts, account data, identifiers, local paths, tokens, or credentials are included.

The issue does not name files or tests; locate the Codex Desktop component that renders transient or running activity headers and compare it with persisted activity rows. The stable application-owned marker should remain present through transient, running, expanded, collapsed, completed, and persisted states.