[BUG] [v0.0.7] cortex debug ripgrep install hint shows "apt install ripgrep" without sudo, but --install uses "sudo apt install -y ripgrep"

[kiannidev]

Project

cortex

Description

When ripgrep is not installed, cortex debug ripgrep displays manual install hints. The Linux hint says apt install ripgrep (without sudo). However, the actual --install implementation runs sudo apt install -y ripgrep (with sudo and -y). A user who copies the displayed hint will get a permission error. Conversely, the --install flag silently escalates to sudo without informing the user.

Error Message

Debug Logs

System Information

Ubuntu 24.04

Screenshots

https://github.com/kiannidev/screens/blob/main/53e226a658e22031a734cdbc2cd1787d.png

Steps to Reproduce

When ripgrep is not installed:
Run cortex debug ripgrep

Expected Behavior

The install hint should match the actual install command, e.g. sudo apt install ripgrep.

Actual Behavior

To install ripgrep:
macOS: brew install ripgrep
Linux: apt install ripgrep / dnf install ripgrep
Windows: winget install BurntSushi.ripgrep.MSVC

The hint says apt install ripgrep (no sudo), but the --install code runs sudo apt install -y ripgrep.

Additional Context

Code Location:
src/cortex-cli/src/debug_cmd/handlers/ripgrep.rs:

• Line 130 (hint): println!(" Linux: apt install ripgrep / dnf install ripgrep");
• Lines 179–180 (actual): Command::new("sudo").args(["apt", "install", "-y", "ripgrep"])

[atlas-cortex]

✅ Validation Summary — Issue #53124

All validation checks passed. 1/17 code rules failed | 1 PENALIZE | 14 LLM instructions active

Confidence Score: 4/5

• All validation checks passed. This submission meets the bounty requirements.

Validation Checks

Check	Status	Detail
Media Evidence	✅ Pass	Evidence found and accessible
Spam Detection	✅ Pass	Score: 22% — no spam signals
Duplicate Detection	✅ Pass	No significant overlap with existing issues
Code Verification	✅ Pass	Bug confirmed in source code (confidence: 100%) — The code in src/cortex-cli/src/debug_cmd/handlers/ripgrep.rs prints the hint `
Edit History	✅ Pass	No suspicious edits
LLM Evaluation	✅ Pass	All validation checks passed. 1/17 code rules failed

Validation Pipeline

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Issue #53124"] --> B{"Media Check"}
    B -->|"✅ Found"| C{"Spam Check"}
    C -->|"✅ Clean"| D{"Duplicate Check"}
    D -->|"✅ Unique"| CV{"Code Verify"}
    CV -->|"✅ Confirmed"| E{"Edit History"}
    E -->|"✅ Normal"| F{"LLM Evaluation"}
    F -->|"✅ Valid"| G["✅ Approved"]
    style G fill:#51cf66,color:#fff

Loading

Raw Evidence

{
  "media": {
    "hasMedia": true,
    "accessible": true,
    "urls": [
      "https://github.com/kiannidev/screens/blob/main/53e226a658e22031a734cdbc2cd1787d.png"
    ],
    "evidence": [
      "Found 1 media URL(s) via markdown parsing",
      "1 URL(s) accessible"
    ]
  },
  "spam": {
    "overallScore": 0.22218045112781953,
    "details": "template=0.36 (8 recent issues compared); burst=1.00 (9 issues in 2h window); parity=0.00; overall=0.44 (threshold=0.7); llm_spam=0.00 (The issue provides a highly specific and clear title describing a mismatch between the CLI installation hint and the actual command executed by the `--install` flag. The steps to reproduce are straightforward and easy to follow. The expected and actual behaviors are well-documented, and the reporter has identified the exact lines of code causing the discrepancy. A screenshot link is provided in the issue body as visual evidence. The report is detailed, factual, and represents a genuine bug.)"
  },
  "duplicate": {
    "isDuplicate": false,
    "similarity": 0.6451288426103138,
    "topSimilar": [
      {
        "issueNumber": 52345,
        "title": "[BUG] [v0.1.0] cortex debug ripgrep --install help says \"Offer to install\" but runs package manager immediately without any confirmation prompt",
        "similarity": 0.6451288426103138
      },
      {
        "issueNumber": 52447,
        "title": "[BUG] [v0.1.0] cortex debug ripgrep --install help says \"Offer to install\" but runs package manager immediately without any confirmation prompt",
        "similarity": 0.6449735193815244
      },
      {
        "issueNumber": 51555,
        "title": "[BUG] [v0.0.7] `cortex debug ripgrep --install` has no visible effect when `rg` is already available",
        "similarity": 0.579097602675384
      },
      {
        "issueNumber": 51506,
        "title": "[BUG] [v0.0.7] `cortex upgrade --check 0.0.6` hint says \"Run \\`cortex upgrade\\`\" — omits version number, would install latest instead of 0.0.6",
        "similarity": 0.5453721368594415
      },
      {
        "issueNumber": 52118,
        "title": "[BUG] [v0.0.7] cortex upgrade redundant description for --pre flag",
        "similarity": 0.5285678102643232
      }
    ]
  },
  "editHistory": {
    "fraudScore": 0,
    "editCount": 0,
    "details": "No edits detected"
  },
  "codeVerification": {
    "plausible": true,
    "confidence": 1,
    "reasoning": "The code in `src/cortex-cli/src/debug_cmd/handlers/ripgrep.rs` prints the hint `apt install ripgrep` without `sudo`, but the actual installation logic for Linux uses `sudo apt install -y ripgrep`. This confirms the discrepancy reported in the bug.",
    "codeEvidence": "println!(\"  Linux:   apt install ripgrep / dnf install ripgrep\");\n// ...\nlet output = tokio::process::Command::new(\"sudo\")\n    .args([\"apt\", \"install\", \"-y\", \"ripgrep\"])",
    "screenshotValid": true,
    "screenshotReasoning": "The screenshot analysis tool returned valid=true, indicating it shows the CLI output demonstrating the issue."
  },
  "rules": {
    "codeResults": {
      "passed": [
        {
          "ruleId": "content.no-profanity",
          "category": "content",
          "severity": "flag",
          "passed": true,
          "message": "Issue should not contain excessive profanity or abusive language",
          "weight": 1
        },
        {
          "ruleId": "content.reasonable-length",
          "category": "content",
          "severity": "flag",
          "passed": true,
          "message": "Issue body should not exceed 15000 characters (possible spam dump)",
          "weight": 1
        },
        {
          "ruleId": "content.has-context",
          "category": "content",
          "severity": "penalize",
          "passed": true,
          "message": "Issue should mention the affected page, component, or URL",
          "weight": 0.2
        },
        {
          "ruleId": "media.require-evidence",
          "category": "media",
          "severity": "require",
          "passed": true,
          "message": "Issue must include at least one screenshot or video URL",
          "weight": 1
        },
        {
          "ruleId": "media.must-be-accessible",
          "category": "media",
          "severity": "require",
          "passed": true,
          "message": "All media URLs must be publicly accessible (HTTP 200)",
          "weight": 1
        },
        {
          "ruleId": "media.no-placeholder-urls",
          "category": "media",
          "severity": "reject",
          "passed": true,
          "message": "Media URLs should not be placeholder or example URLs",
          "weight": 1
        },
        {
          "ruleId": "scoring.suspicious-edits",
          "category": "scoring",
          "severity": "penalize",
          "passed": true,
          "message": "Penalize issues with concerning edit history (fraud score > 0.3)",
          "weight": 0.25
        },
        {
          "ruleId": "spam.high-score-reject",
          "category": "spam",
          "severity": "reject",
          "passed": true,
          "message": "Reject issues with spam score above 0.85",
          "weight": 1
        },
        {
          "ruleId": "spam.generic-title",
          "category": "spam",
          "severity": "penalize",
          "passed": true,
          "message": "Title should not be a generic/template title",
          "weight": 0.4
        },
        {
          "ruleId": "spam.body-is-title-repeat",
          "category": "spam",
          "severity": "penalize",
          "passed": true,
          "message": "Body should not be a simple repetition of the title",
          "weight": 0.5
        },
        {
          "ruleId": "spam.no-ai-filler",
          "category": "spam",
          "severity": "flag",
          "passed": true,
          "message": "Body should not contain obvious AI-generated filler phrases",
          "weight": 1
        },
        {
          "ruleId": "validity.min-body-length",
          "category": "validity",
          "severity": "reject",
          "passed": true,
          "message": "Issue body must be at least 50 characters",
          "weight": 1
        },
        {
          "ruleId": "validity.min-title-length",
          "category": "validity",
          "severity": "reject",
          "passed": true,
          "message": "Issue title must be at least 10 characters",
          "weight": 1
        },
        {
          "ruleId": "validity.no-empty-body",
          "category": "validity",
          "severity": "reject",
          "passed": true,
          "message": "Issue body must not be empty or only whitespace",
          "weight": 1
        },
        {
          "ruleId": "validity.has-steps-or-description",
          "category": "validity",
          "severity": "penalize",
          "passed": true,
          "message": "Issue body should contain structured content (steps, expected/actual behavior)",
          "weight": 0.3
        },
        {
          "ruleId": "validity.not-a-feature-request",
          "category": "validity",
          "severity": "flag",
          "passed": true,
          "message": "Issue should describe a bug, not a feature request",
          "weight": 1
        }
      ],
      "failed": [
        {
          "ruleId": "scoring.duplicate-threshold",
          "category": "scoring",
          "severity": "penalize",
          "passed": false,
          "message": "Issue has moderate similarity to existing issues, suggesting partial overlap.",
          "weight": 0.3
        }
      ]
    },
    "llmInstructions": [
      "Always prioritize concrete evidence (screenshots, videos, URLs) over the quality of the written description. A poorly written report with clear visual proof of a bug is VALID. A beautifully written report with no evidence is INVALID.",
      "A valid bug report must contain enough information for an engineer to reproduce the issue. If the steps to reproduce are missing or impossibly vague (\"it just broke\"), the issue is INVALID.",
      "You MUST call the deliver_verdict function exactly once. Do not output a JSON object manually. Do not output your verdict in plain text. Use the tool.",
      "Be highly suspicious of submissions that follow a rigid template: same structure, same phrasing, with only the page name or URL swapped. These are template-farmed and should be INVALID. Look for: identical sentence structure, placeholder-like descriptions, formulaic \"Steps to Reproduce\".",
      "When similar issues exist, the OLDER issue (lower issue number) always takes precedence. The newer submission is the duplicate, never the other way around.",
      "Confidence scores must be calibrated: use 0.9+ only when evidence is unambiguous and complete. Use 0.5-0.7 when the issue is borderline. Use below 0.5 when you are genuinely uncertain. Never default to 0.5 — commit to a direction.",
      "Do not give the benefit of the doubt. Missing evidence means INVALID. Unclear reproduction steps means INVALID. Inaccessible media means INVALID. The burden of proof is on the submitter.",
      "In the reasoning field, explain your step-by-step analysis BEFORE stating your conclusion. Cover: evidence quality, clarity, spam signals, and duplicate overlap in that order.",
      "Never mention internal scoring thresholds, rule IDs, detection heuristics, or system architecture in the recap field. The recap is public-facing. Keep reasoning technical but recap user-friendly.",
      "If the issue body reads like AI-generated boilerplate (phrases like \"It is important to note\", \"Furthermore\", \"In conclusion\", excessive politeness, no specific technical details), treat it as strong evidence of spam. AI-generated issues with no real bug details are INVALID.",
      "If the pre-computed media check says media URLs exist, verify the description matches what a screenshot would show. If the description talks about a login page but the context suggests the screenshot is of something unrelated, flag this as suspicious.",
      "Never soften a verdict out of sympathy. \"I can see you tried hard but...\" is not acceptable. If the submission does not meet criteria, it is INVALID regardless of apparent effort.",
      "Write your reasoning and recap in a professional, neutral tone. Do not be sarcastic, condescending, or emotional. State facts.",
      "The recap field must be 2-3 sentences maximum. It will be posted as a public comment. No bullet points in recap — use flowing prose."
    ],
    "totalCodeRules": 17,
    "totalLLMRules": 14,
    "hasReject": false,
    "hasFailed": true,
    "penaltyScore": 0.3,
    "summary": "1/17 code rules failed | 1 PENALIZE | 14 LLM instructions active"
  }
}

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

[GreyforgeLabs]

Opened upstream fix: CortexLM/cortex-code#377

Change:

• The Linux ripgrep install hint now matches the package-manager commands used by cortex debug ripgrep --install, including sudo and -y for apt/dnf.

Validation:

• cargo fmt --package cortex-cli --check
• git diff --check
• cargo check -p cortex-cli --no-default-features --features cortex-tui