[BUG] [v0.0.7] cortex history: “view” behavior is implicit and not listed; help only shows search/clear

[lucaserevo]

Project

cortex

Description

The cortex history help text describes viewing prompt history and exposes flags such as --limit, --all, and --json that strongly imply a default “list recent entries” mode. However, the subcommand list only enumerates search and clear, and does not document what happens when no subcommand is provided. New users must guess that omitting a subcommand is the intended “view/list” path, which hurts discoverability and makes the CLI feel incomplete or inconsistent. This is primarily a documentation/UX-structure problem: the behavior exists implicitly but is not named or explained alongside the other subcommands.

Impact: confusion about how to use history; extra support burden; users may think their build is broken when the real issue is missing help text.

Error Message

Debug Logs

System Information

Linux 6.14

Screenshots

https://github.com/springoliver/bounty_challenge_report_image/blob/main/49102.png

Steps to Reproduce

1. Run: cortex history -h
2. Note description and Commands (search, clear only).
3. Run: cortex history with no subcommand.
4. Observe behavior is the implicit “view” path but it is not documented under Commands.

Expected Behavior

Help should explicitly document default behavior, for example: “With no subcommand, list recent prompts (respects --limit, --all, --json).” Alternatively add an explicit list or view subcommand so Commands match the described behavior.

Actual Behavior

Help implies viewing via summary copy and options but does not list a view/list command or explain the no-subcommand case.

Additional Context

No response

[atlas-cortex]

✅ Validation Summary — Issue #53424

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: 0% — no spam signals
Duplicate Detection	✅ Pass	No significant overlap with existing issues
Code Verification	✅ Pass	Bug confirmed in source code (confidence: 100%) — The HistoryCommand struct in src/cortex-cli/src/cli/args.rs defines an optio
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 #53424"] --> 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/springoliver/bounty_challenge_report_image/blob/main/49102.png"
    ],
    "evidence": [
      "Found 1 media URL(s) via markdown parsing",
      "1 URL(s) accessible"
    ]
  },
  "spam": {
    "overallScore": 0,
    "details": "template=0.00 (0 recent issues compared); burst=0.00 (1 issues in 2h window); parity=0.00; overall=0.00 (threshold=0.7)"
  },
  "duplicate": {
    "isDuplicate": false,
    "similarity": 0.6233771339748252,
    "topSimilar": [
      {
        "issueNumber": 52366,
        "title": "[BUG] [v0.0.7] cortex history with no subcommand prints a stub — history view is not implemented",
        "similarity": 0.6233771339748252
      },
      {
        "issueNumber": 52222,
        "title": "[BUG] [v0.0.7] /history command is functional but not listed in help panel, reducing discoverability of command recall feature",
        "similarity": 0.6124540113040604
      },
      {
        "issueNumber": 52170,
        "title": "[BUG][v0.0.7] `cortex history` accepts `--json`, `--all`, and `-n` / `--limit` but `run_history` does not implement them",
        "similarity": 0.6108263834433689
      },
      {
        "issueNumber": 52780,
        "title": "[BUG] [v0.0.7] `cortex --help` lists `scrape` as a top-level subcommand while the TUI uses `/scrape` — help vs slash-command discoverability mismatch",
        "similarity": 0.6045875993247213
      },
      {
        "issueNumber": 53004,
        "title": "[BUG] [v0.0.7] Inconsistent Capitalization in Help Modal: Confirm/select vs Standard Title Case",
        "similarity": 0.5910412217780252
      }
    ]
  },
  "editHistory": {
    "fraudScore": 0,
    "editCount": 0,
    "details": "No edits detected"
  },
  "codeVerification": {
    "plausible": true,
    "confidence": 1,
    "reasoning": "The `HistoryCommand` struct in `src/cortex-cli/src/cli/args.rs` defines an optional `action` of type `HistorySubcommand`. The `HistorySubcommand` enum only contains `Search` and `Clear` variants. There is no explicit `List` or `View` subcommand, and the doc comment for `HistoryCommand` does not explicitly state that omitting a subcommand will list recent entries, confirming the UX/documentation issue described in the bug report.",
    "codeEvidence": "/// History command - view past prompts and sessions.\n#[derive(Args)]\npub struct HistoryCommand {\n    #[command(subcommand)]\n    pub action: Option<HistorySubcommand>,\n\n    /// Maximum number of entries to show\n    #[arg(short = 'n', long, default_value = \"20\")]\n    pub limit: usize,\n...\n/// History subcommands.\n#[derive(Subcommand)]\npub enum HistorySubcommand {\n    /// Search history for a pattern\n    Search(HistorySearchArgs),\n    /// Clear history (requires confirmation)\n    Clear(HistoryClearArgs),\n}",
    "screenshotValid": true,
    "screenshotReasoning": "The screenshot analysis returned valid, confirming it shows the actual CLI output of `cortex history -h` demonstrating the missing documentation for the default behavior."
  },
  "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-22}

[DanielButler1]

Fix submitted upstream: CortexLM/cortex-code#239

Verification:

• rustfmt --edition 2024 --check src/cortex-cli/src/cli/args.rs src/cortex-cli/src/agent_cmd/tests.rs
• git diff --check
• cargo test -p cortex-cli cli::args::tests::test_history_help_documents_default_list_behavior
• cargo check -p cortex-cli