[BUG] [v0.0.7] cortex --verbose agent list produces identical output to cortex agent list

[princewillis]

Description

The global --verbose flag has no visible effect on cortex agent list. Running the command with and without --verbose produces the same table, summary, and footer output.

Steps to Reproduce

1. Run cortex agent list.
2. Run cortex --verbose agent list.
3. Compare the terminal output from both commands.

Expected Behavior

Enabling --verbose should add extra diagnostic output or otherwise produce visibly more detail than the default run.

Actual Behavior

cortex --verbose agent list prints the same visible output as cortex agent list.

Evidence

[GreyforgeLabs]

Fix PR opened: https://github.com/CortexLM/cortex/pull/395

Summary:

• cortex --verbose agent list now emits debug diagnostics for active filters and loaded/filtered agent counts.
• Added a binary regression proving normal agent list and verbose agent list have visibly different output.

Validation:

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

[atlas-cortex]

✅ Validation Summary — Issue #51952

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: 20% — no spam signals
Duplicate Detection	✅ Pass	No significant overlap with existing issues
Code Verification	✅ Pass	Bug confirmed in source code (confidence: 100%) — The code confirms that the agent list command does not emit any debug or trace
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 #51952"] --> 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://raw.githubusercontent.com/princewillis/cortex-bounty-evidence/main/2026-04-09-agent-list-verbose-no-effect/01-full-evidence.png",
      "https://raw.githubusercontent.com/princewillis/cortex-bounty-evidence/main/2026-04-09-agent-list-verbose-no-effect/02-close-up.png"
    ],
    "evidence": [
      "Found 2 media URL(s) via GitHub rendered HTML",
      "2 URL(s) accessible"
    ]
  },
  "spam": {
    "overallScore": 0.20132978723404257,
    "details": "template=0.82 (1 recent issues compared); burst=0.25 (2 issues in 2h window); parity=0.00; overall=0.40 (threshold=0.7); llm_spam=0.00 (The issue title is specific and accurately describes the problem. The steps to reproduce are clear, and the expected versus actual behavior is explicitly stated. The issue body contains validly formatted image tags pointing to visual evidence of the terminal output, demonstrating the bug. There are no signs of spam or template farming, and no duplicate issues were flagged.)"
  },
  "duplicate": {
    "isDuplicate": false,
    "similarity": 0.6597384375497725,
    "topSimilar": [
      {
        "issueNumber": 51803,
        "title": "[BUG] [v0.0.7] cortex agent install --verbose produces identical output to the default run",
        "similarity": 0.6597384375497725
      },
      {
        "issueNumber": 51874,
        "title": "[BUG] [v0.0.7] cortex plugin show --verbose produces identical output to the default run",
        "similarity": 0.6249008519930067
      },
      {
        "issueNumber": 51840,
        "title": "[BUG] [v0.0.7] cortex plugin install --verbose produces identical output to the default run",
        "similarity": 0.6095411689695398
      },
      {
        "issueNumber": 51665,
        "title": "[BUG] [v0.0.7] `cortex models list --verbose` produces identical output to default — verbose flag is a no-op",
        "similarity": 0.6046465673722792
      },
      {
        "issueNumber": 50847,
        "title": "[BUG] [v0.0.7] `cortex agent list --json` returns plain array with no metadata — hidden agent count from text output is absent",
        "similarity": 0.5513096417202932
      }
    ]
  },
  "editHistory": {
    "fraudScore": 0,
    "editCount": 0,
    "details": "No edits detected"
  },
  "codeVerification": {
    "plausible": true,
    "confidence": 1,
    "reasoning": "The code confirms that the `agent list` command does not emit any debug or trace logs, nor does it alter its output when the global `--verbose` flag is used. The screenshots show a real user terminal executing the commands and receiving identical output, validating the user-facing bug.",
    "codeEvidence": "The `run_list` function in `src/cortex-cli/src/agent_cmd/handlers/list.rs` implements the `agent list` command. It uses `println!` to output the list of agents but does not use any logging macros (like `debug!`, `info!`, `trace!`) or check for a `verbose` flag to print additional diagnostic information. The `--verbose` flag sets the log level to Debug in `src/cortex-cli/src/main.rs`, but since the `agent list` command and its underlying loader (`src/cortex-cli/src/agent_cmd/loader.rs`) do not emit any debug logs, the output remains identical.",
    "screenshotValid": true,
    "screenshotReasoning": "The screenshots show a real terminal executing `cortex agent list` and `cortex --verbose agent list`, demonstrating that the output is identical. They are valid user-facing evidence."
  },
  "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-05-20}