Linux Desktop: add “Open link in external browser” to link right-click context menu
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- linux, rust
- Domain
- desktop-dev
Research direction
Search the Rust codebase for chat message rendering and link context menu handling. Locate where hyperlink right-click options are defined and add the 'Open in external browser' menu item. Implement the action to launch the system default browser with the selected URL, then verify the behavior on Linux desktop.
Written by the indexing model from the issue text.
Description
What variant of Codex are you using?
App
What feature would you like to see?
Requested behavior
Add “Open in external browser” to the right-click context menu
for hyperlinks in chat messages. It should open the selected URL
in the system’s default browser.
Current behavior
On Fedora 44 KDE/Wayland, right-clicking a hyperlink in a chat
does not offer this option.
Why this helps
My normal browser contains my signed-in accounts, extensions,
and existing tabs. A direct context-menu action would let me
use that browser without manually copying and pasting URLs.
Additional information
- App version: ChatGPT/Codex Linux desktop 26.1002.52244
- OS: Fedora Linux 44, KDE Plasma, Wayland session
- Related: #36601
- Dominant language
- Rust
- Stars
- 129k
- Forks
- 20.3k
- Avg merge
- 1m
- Merged PRs (30d)
- 998
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
bug CLI
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openai/codex#55122 · 2 comments ·
Maintainers usually reply within 1 day
-
Python SDK: CodexClient.close() leaves the app-server's stdout/stderr pipes open (and never waits after kill)Possibly taken @akhil9tiet claimed this 2 days ago. Openapp-server bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openai/codex#54908 · 2 comments ·
Maintainers usually reply within 1 day
-
bug CLI tool-calls windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug tool-calls
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Clarification about NODE_REPL_TRUSTED_BROWSER_CLIENT_SHA256S in the VS Code extension environmentOpendocumentation extension windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
openai/codex#54780 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
chipsalliance/caliptra-sw#4311 ·
Maintainers usually reply within 2 days
-
`image_generation`: `max_retries` is ignored for OpenAI-compatible providers (always 2 retries)Possibly taken @ericz7900 claimed this today. Openllm translation
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Help-Wanted Needs-Triage Package-Request
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
microsoft/winget-pkgs#456324 ·
Maintainers usually reply within 1 day
-
ai_p2
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ClickHouse/ClickHouse#126833 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day