Make the PR number in the CLI status line clickable
What variant of Codex are you using?
CLI
What version of Codex CLI is running?
codex-cli 0.142.2
What feature would you like to see?
I'd like the existing pull-request-number status-line item to let me navigate to the current GitHub pull request.
Today, the TUI status line can render something like:
gpt-5.5 high · Context 100% left · feature/example · PR #123 · ~/repo
That PR #123 display is useful, but in my terminal it does not open the GitHub pull request when clicked.
Why this would help
When working through PR review feedback in Codex CLI, I often need to jump back to the current PR in GitHub. Since the status line can already show PR #123, making that segment clickable would cover the navigation use case without needing to display the full URL in the footer.
This is especially helpful when juggling multiple branches or worktrees.
Possible behavior
- When
pull-request-numberknows the PR URL, renderPR #123as a terminal hyperlink where supported. - Keep the visible text compact as
PR #123rather than showing the full URL by default. - Omit or render plain text gracefully when no open PR is found,
ghis unavailable, the repo is not hosted on GitHub, or the terminal does not support hyperlinks. - As an optional fallback, add a separate
pull-request-url/github-pr-urlitem for users who need the explicit URL string in terminals or workflows where clickable links are unavailable or unreliable.
Current workaround
I can run this manually:
gh pr view --json url -q .url
Or add a local alias such as:
gh alias set prurl 'pr view --json url -q .url'
But it would be more convenient if the existing PR #123 status-line segment navigated directly to the PR.
Related issues
- #22697 mentions existing git-related status-line items, including
pull-request-number. - #23473 discusses
pull-request-numberlookup behavior and shows that the PR lookup path already requestsurlfromgh pr view. - #17827 is the broader request for a fully customizable status line; this request is narrower and could be implemented as clickable behavior for one existing built-in item.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗