Feature request: in-app fallback actions when source reference opening fails

What variant of Codex are you using?

App (Windows desktop)

What feature would you like to see?

Add built-in fallback actions when a source reference cannot be resolved/opened.

Requested UX:

1. If opening a referenced file fails, show a compact action bar with:

• Open by absolute path
• Open with line (code -g <path>:<line>)
• Copy absolute path
• Copy code -g command

1. Display the exact normalized path Codex attempted to open (for debugging).
2. Offer one-click "Retry with Windows normalization" when path contains suspicious patterns (e.g., duplicated drive prefix).
3. Keep these actions in the same chat message so users don’t need manual command crafting.

Additional information

Related issues:

• Windows invalid path (c:\C:\...) bug: https://github.com/openai/codex/issues/13548
• Diff-like line focus/collapsible context request: https://github.com/openai/codex/issues/13550

This issue focuses only on failure recovery UX and operational fallbacks.

Why this matters:

• When navigation fails, users lose flow and must manually reconstruct paths/commands.
• Explicit fallback actions would turn a hard failure into a quick recovery step.