[BUG] [alpha] `cortex logs --clear --level` ignores level filter and clears all log files

[lucife-R-0014]

Project

cortex

Description

When users run cortex logs --clear --level <level>, the --level argument is not applied during clear operations. Instead of deleting only the selected level (for example error), the command removes every log file matching the age rule, which can unexpectedly wipe unrelated logs.

Root cause (this repo)

The command dispatch enters clear-mode early and executes run_clear() before level-based selection is considered. The clear path does not read self.level, so deletion proceeds without level filtering.

Fix direction (suggested)

• Thread --level into run_clear() filtering logic.
• If a level is provided, restrict deletion to matching filenames/categories only.
• Emit explicit output showing which levels/files were targeted before deletion.

Code snapshot

• src/cortex-cli/src/logs_cmd.rs — run() early return into run_clear()
• src/cortex-cli/src/logs_cmd.rs — run_clear() deletion loop without level filter checks

Error Message

Cleared 3 log file(s) older than 0 days.

Debug Logs

System Information

Platform: Windows 11
Component: cortex-cli (release build)
Reproducible: Yes (consistent)

Screenshots / Media

https://github.com/ultrahighsuper/111/blob/main/2026-04-09_10h51_49.png

Steps to Reproduce

1. Verify multiple log-level files exist (for example debug/error/info).
2. Run cortex logs --clear --level error --keep-days 0.
3. Observe the clear summary count.
4. Run cortex logs --paths again.
5. Confirm non-error files were also deleted.

Expected Behavior

--level error should clear only error-level log files and preserve other levels.

Actual Behavior

The clear operation removes all eligible log files regardless of level, effectively ignoring --level.

Additional Context

• Impact includes unintended loss of logs users expected to keep.
• Command output currently does not warn that the provided level filter was not honored.

[atlas-cortex]

✅ Validation Summary — Issue #51573

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 code confirms that the --level argument is ignored when --clear is used.
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 #51573"] --> 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/ultrahighsuper/111/blob/main/2026-04-09_10h51_49.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.5146528653020641,
    "topSimilar": [
      {
        "issueNumber": 51536,
        "title": "[BUG] [v0.0.7] Log level filtering uses substring matching, causing false positives",
        "similarity": 0.5146528653020641
      },
      {
        "issueNumber": 50837,
        "title": "[BUG] [v0.0.7] `/logs` picker says **Warn = “Warnings only”**, but warn level still includes errors",
        "similarity": 0.4982019226408868
      },
      {
        "issueNumber": 51232,
        "title": "[BUG] [v0.0.7] cortex logs --session / -s is accepted but ignored — always tails/shows newest log file",
        "similarity": 0.48056821914136494
      },
      {
        "issueNumber": 51347,
        "title": "[BUG] [v0.0.7] Temporary cleanup can delete unrelated files if they start with \\`cortex-\\`",
        "similarity": 0.4708290170214185
      },
      {
        "issueNumber": 51079,
        "title": "[BUG] [v0.0.7] cortex cache clear treats yes as abort — only a single-letter y counts as confirmation",
        "similarity": 0.4629559984251887
      }
    ]
  },
  "editHistory": {
    "fraudScore": 0,
    "editCount": 0,
    "details": "No edits detected"
  },
  "codeVerification": {
    "plausible": true,
    "confidence": 1,
    "reasoning": "The code confirms that the `--level` argument is ignored when `--clear` is used. The `run_clear` function deletes all log files older than the specified number of days regardless of their log level.",
    "codeEvidence": "In `src/cortex-cli/src/logs_cmd.rs`, the `run` method calls `run_clear` early if `self.clear` is true. The `run_clear` method iterates over all files in the logs directory and deletes them if they are older than `keep_days`, without checking `self.level`.",
    "screenshotValid": true,
    "screenshotReasoning": "The screenshot analysis tool returned valid: true, indicating the screenshot shows a real user-facing bug."
  },
  "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-09}

[GreyforgeLabs]

Implemented in CortexLM/cortex-code#403

Validation run:

• cargo test -p cortex-cli --test logs_clear_level --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
• git diff --cached --check