›_ Codex Issues
Codex Issues / #30393

Feature request: let Codex PR reviews use linked Linear issue context

Open 💬 0 comments Opened Jun 28, 2026 by mdroidian

What feature would you like to see?

Please add first-class support for Codex GitHub PR reviews to use linked Linear issue context when reviewing a pull request.

Today, Codex code review is useful for finding issues in the diff, following repository guidance, and checking high-priority bugs. But in teams that plan work in Linear, a PR often needs to be reviewed against the product/engineering intent of the linked Linear issue, not just against the code diff in isolation.

Problem

When a PR is linked to a Linear issue, the reviewer needs to answer questions like:

  • Does this PR implement what the Linear ticket asked for?
  • Did it satisfy the ticket's acceptance criteria or stated expected behavior?
  • Did it solve the intended user/product problem, rather than only making a plausible code change?
  • Are there important edge cases, constraints, comments, or scope notes in the Linear issue that the PR missed?
  • If the PR intentionally diverges from the ticket, is that divergence visible in the PR description or review summary?

Without Linear context, Codex review can catch code-level problems but may miss intent-level failures: correct-looking code that does not actually complete the requested work.

Proposed behavior

When Codex is asked to review a GitHub PR and the PR is linked to a Linear issue, Codex should optionally fetch and incorporate the Linear issue context into the review. Possible sources of the linked issue could include:

  • GitHub/Linear linkbacks attached to the PR or branch
  • Linear issue IDs in branch names, commit messages, PR title, or PR body
  • GitHub issue sync/linkback metadata created by the Codex for Linear integration
  • an explicit review instruction, e.g. @codex review against LIN-123

The review should then include an intent/requirements pass, separate from ordinary code review findings. For example:

  • summarize the ticket intent and acceptance criteria used for review
  • flag missing or incomplete implementation relative to the ticket
  • flag behavior that appears out of scope or inconsistent with the ticket
  • note when the Linear issue could not be fetched or was ambiguous
  • avoid blocking on this pass unless the configured review guidelines say intent mismatches should be treated as P0/P1

Why this matters

For many teams, Linear is the source of truth for why a change exists. A code review bot that only reviews the diff can produce high-quality code-level feedback while still missing whether the PR actually does the requested job. This becomes more important as coding agents create more PRs from tickets.

Current workaround

Teams can partially work around this by manually copying the Linear issue summary and acceptance criteria into the PR body, or by invoking Codex with a one-off instruction that includes the ticket text. That is brittle and easy to forget, and it does not help automatic reviews.

Acceptance criteria

  • Codex PR review can detect or be given a linked Linear issue for a PR.
  • Codex fetches the relevant Linear issue content when permissions are available.
  • Review output explicitly states whether Linear context was used, unavailable, or ambiguous.
  • Review output can include findings about mismatch between the PR and the ticket intent/acceptance criteria.
  • Repository-level AGENTS.md review guidelines can configure how strongly to treat intent mismatches.
  • Automatic reviews can use this feature without requiring humans to paste the ticket text into each PR.

Related context

This is related to, but more specific than, general workflow/ticket-context requests such as #24721. That issue discusses user-defined workflows that can read tickets, but this request is specifically for Codex's GitHub PR review flow to review the PR against the linked Linear issue's intent and acceptance criteria.

Relevant public docs:

View original on GitHub ↗