[BUG] [v0.0.7] [CLI] `cortex pr <n> --comments` falls back to recommending `gh` or the browser instead of listing comments in-terminal

[kiannidev]

Project

cortex

Description

cortex pr <number> --comments is documented as a way to view PR comments, but unless the separate GitHub CLI (gh) is installed and working, the command does not print comment threads in the terminal. After the usual PR metadata block, it prints Fetching PR comments… and then a Note telling the user to install gh for “full” viewing, plus an Alternative: link to open the PR in a web browser.

For users who rely on Cortex alone (or who have a GitHub token configured for Cortex but not gh), this feels like a missing feature: the flag suggests in-terminal reading, yet the tool delegates to other programs instead of using the GitHub API (or existing client code) to fetch and render issue/PR comments itself.

Error Message

Debug Logs

System Information

OS:windows

Screenshots

https://github.com/kiannidev/screens/blob/main/32b0d2f9ad972437a3c8fbef901a56a8.png

Steps to Reproduce

1. Ensure gh is not available (or fails), while cortex can still reach GitHub for other PR commands if applicable.
2. Run cortex pr <n> --comments for a PR that has comments on GitHub.
3. Observe that only the fallback message and URL appear—not the comments.

Expected Behavior

--comments should list PR comments in the terminal using Cortex’s own GitHub integration (token / API), similar to how PR metadata is fetched—without requiring gh or a browser for basic reading.

Actual Behavior

If gh pr view --comments does not succeed, Cortex does not fetch comments itself; it only recommends installing gh or visiting the PR URL.

Additional Context

No response

[atlas-cortex]

🔁 Validation Summary — Issue #53274

Issue is a duplicate of #53011 (similarity: 0.71)

Duplicate of #53011 — the original issue takes precedence.

Confidence Score: 5/5

• High confidence — this issue substantially overlaps with [CLI][v0.0.7] cortex pr <n> --comments falls back to recommending gh or the browser instead of listing comments in-terminal #53011.

Validation Checks

Check	Status	Detail
Media Evidence	✅ Pass	Evidence found and accessible
Spam Detection	✅ Pass	Score: 68% — borderline, consulted LLM
Duplicate Detection	❌ Duplicate	Matches existing issue #53011
Code Verification	✅ Pass	Bug confirmed in source code (confidence: 100%) — The code in src/cortex-cli/src/pr_cmd.rs confirms the bug report. When the `--
Edit History	✅ Pass	No suspicious edits
LLM Evaluation	❌ Fail	Issue is a duplicate of #53011 (similarity: 0.71)

Validation Pipeline

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Issue #53274"] --> B{"Media Check"}
    B -->|"✅ Found"| C{"Spam Check"}
    C -->|"✅ Clean"| D{"Duplicate Check"}
    D -->|"Matches #53011"| Z["🔁 Duplicate"]
    style Z fill:#ffa94d,color:#fff

Loading

Raw Evidence

{
  "media": {
    "hasMedia": true,
    "accessible": true,
    "urls": [
      "https://github.com/kiannidev/screens/blob/main/32b0d2f9ad972437a3c8fbef901a56a8.png"
    ],
    "evidence": [
      "Found 1 media URL(s) via markdown parsing",
      "1 URL(s) accessible"
    ]
  },
  "spam": {
    "overallScore": 0.6772522522522522,
    "details": "template=0.26 (12 recent issues compared); burst=1.00 (13 issues in 2h window); parity=0.00; overall=0.40 (threshold=0.7); llm_spam=0.95 (The issue describes the intended behavior of the application as a bug. The CLI tool explicitly outputs a fallback message recommending the installation of `gh` or using a web browser, which indicates that this is the designed behavior when the GitHub CLI is not present. The reporter even acknowledges that this feels like a \"missing feature\" rather than a defect. Furthermore, the provided screenshot link is a GitHub blob page rather than a direct media URL.)"
  },
  "duplicate": {
    "isDuplicate": true,
    "originalIssue": 53011,
    "similarity": 0.713316315841366,
    "topSimilar": [
      {
        "issueNumber": 53011,
        "title": "[CLI][v0.0.7] `cortex pr <n> --comments` falls back to recommending `gh` or the browser instead of listing comments in-terminal",
        "similarity": 0.713316315841366
      },
      {
        "issueNumber": 52514,
        "title": "[BUG] [v0.0.7] `cortex pr <n> --comments`: prints “Fetching…” then runs **`gh`** with no upfront dependency check",
        "similarity": 0.6027423766487168
      },
      {
        "issueNumber": 51668,
        "title": "[BUG] [v0.0.7] `cortex pr --info` omits file change statistics — no files changed, additions, or deletions count shown",
        "similarity": 0.5896112903990569
      },
      {
        "issueNumber": 51818,
        "title": "[BUG] [v0.0.7] cortex pr --info --diff silently drops --diff when combined with --info",
        "similarity": 0.589048044100938
      },
      {
        "issueNumber": 52549,
        "title": "[BUG] [v0.0.7] `cortex pr <n> --comments`: no **`--json`** (or other structured mode)—Clap rejects **`--json`**; output is human text only",
        "similarity": 0.5641014754476066
      }
    ]
  },
  "editHistory": {
    "fraudScore": 0,
    "editCount": 0,
    "details": "No edits detected"
  },
  "codeVerification": {
    "plausible": true,
    "confidence": 1,
    "reasoning": "The code in `src/cortex-cli/src/pr_cmd.rs` confirms the bug report. When the `--comments` flag is used, Cortex attempts to run the external `gh` CLI tool to fetch comments. If `gh` is not installed or fails, it falls back to printing a note recommending the installation of `gh` and providing a URL to view the comments in a browser, rather than using its own GitHub API client to fetch and display the comments.",
    "codeEvidence": "    // If --comments flag, show PR comments\n    if args.comments {\n        println!(\"Fetching PR comments...\");\n        println!();\n\n        // Use gh CLI to get comments if available, otherwise show message\n        let gh_output = Command::new(\"gh\")\n            .args([\n                \"pr\",\n                \"view\",\n                &pr_number.to_string(),\n                \"--repo\",\n                &repository,\n                \"--comments\",\n            ])\n            .output();\n\n        match gh_output {\n            Ok(output) if output.status.success() => {\n                let comments = String::from_utf8_lossy(&output.stdout);\n                if comments.trim().is_empty() {\n                    println!(\"No comments on this PR.\");\n                } else {\n                    println!(\"{}\", comments);\n                }\n            }\n            _ => {\n                println!(\"Note: Install GitHub CLI (gh) for full comment viewing.\");\n                println!();\n                println!(\"Alternative: View comments at:\");\n                println!(\"  https://github.com/{}/pull/{}\", repository, pr_number);\n            }\n        }\n        return Ok(());\n    }",
    "screenshotValid": true,
    "screenshotReasoning": "The screenshot shows a terminal window where the user runs `cortex pr 123 --comments`. The output displays the PR metadata, followed by \"Fetching PR comments...\", and then the fallback message: \"Note: Install GitHub CLI (gh) for full comment viewing.\" and \"Alternative: View comments at: https://github.com/...\". This perfectly matches the described bug and the code implementation, and it is a valid user-facing screenshot."
  }
}

_{Validated by Atlas • 2026-04-10}