[BUG] [v0.0.7] `cortex cache show --json` exposes `"cache_dir"` as a flat string while `cortex debug paths --json` exposes `"cache_dir"` as a nested object with `"path"` and `"exists"` — same field name, incompatible types

[tryeverything24]

Project

cortex

Description

Two commands both expose a "cache_dir" field but with entirely different types:

• cache show --json → "cache_dir": "/home/ubuntu/.cache/cortex" (flat string)
• debug paths --json → "cache_dir": {"path": "/home/ubuntu/.cortex/cache", "exists": false} (nested object)

A script reading "cache_dir" from either command gets a different type and must use different access patterns.

Error Message

Debug Logs

System Information

Cortex CLI v0.0.7
OS: Linux (Ubuntu)

Screenshots

https://github.com/tryeverything24/rawimagespublic/blob/main/23.png

Steps to Reproduce

Step 1: Check cache_dir in cache show JSON

cortex cache show --json | python3 -c "import json,sys; d=json.load(sys.stdin); print('cache show cache_dir:', d['cache_dir'], '| type:', type(d['cache_dir']).name)"

Output:

cache show cache_dir: /home/ubuntu/.cache/cortex | type: str

Step 2: Check cache_dir in debug paths JSON

cortex debug paths --json | python3 -c "import json,sys; d=json.load(sys.stdin); print('debug paths cache_dir:', d['cache_dir'], '| type:', type(d['cache_dir']).name)"

Output:

debug paths cache_dir: {'path': '/home/ubuntu/.cortex/cache', 'exists': False} | type: dict

Expected Behavior

Both commands should use the same type for "cache_dir". The richer nested object ({"path": "...", "exists": ...}) from debug paths is more informative and should be used consistently.

Actual Behavior

cache show cache_dir: /home/ubuntu/.cache/cortex | type: str
debug paths cache_dir: {'path': '/home/ubuntu/.cortex/cache', 'exists': False} | type: dict

cache show exposes "cache_dir" as a plain string while debug paths exposes it as a nested object. Accessing d["cache_dir"] returns incompatible types across the two commands.

Additional Context

Relevant source code:

• cache show --json (src/cortex-cli/src/cache_cmd.rs): CacheStats struct has cache_dir: String — serializes as a plain string.

• debug paths --json (src/cortex-cli/src/debug_cmd/types.rs): PathEntry struct has path: PathBuf and exists: bool — serializes as a nested object {"path": "...", "exists": ...}.

Both commands expose the cache directory but as different types. Note also that the actual paths differ (/home/ubuntu/.cache/cortex vs /home/ubuntu/.cortex/cache), pointing to a deeper inconsistency in which cache directory each command reports.

[atlas-cortex]

✅ Validation Summary — Issue #53519

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 two commands expose cache_dir with different types.
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 #53519"] --> 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/tryeverything24/rawimagespublic/blob/main/23.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.6825785169125437,
    "topSimilar": [
      {
        "issueNumber": 52038,
        "title": "[BUG] [v0.0.7] `cortex compact status --json` exposes directories as flat string fields while `cortex debug paths --json` exposes the same directories as nested objects with `path`, `exists`, and `size_bytes`",
        "similarity": 0.6825785169125437
      },
      {
        "issueNumber": 52109,
        "title": "[BUG] [v0.0.7] `cortex cache size --json` uses `\"size_bytes\"` while `cortex cache show --json` uses `\"total_size_bytes\"` for the total cache size — inconsistent field name across sibling commands",
        "similarity": 0.6678533018195816
      },
      {
        "issueNumber": 52022,
        "title": "[BUG] [v0.0.7] `cortex debug snapshot --json` uses `\"snapshots_dir_exists\": true` (compound boolean key) while `cortex debug paths --json` uses a nested object `{\"exists\": true}` for the same concept",
        "similarity": 0.6661570030997939
      },
      {
        "issueNumber": 52048,
        "title": "[BUG] [v0.0.7] `cortex debug system --json` uses `\"current_dir\"` while `cortex debug config --json` uses `\"cwd\"` for the same working directory path — inconsistent field name across sibling `debug` subcommands",
        "similarity": 0.6580189843913575
      },
      {
        "issueNumber": 52924,
        "title": "[BUG] [v0.0.7] `cortex compact status --json` represents directories as plain string fields whereas `cortex debug paths --json` represents them as nested objects with `path`, `exists`, and `size_bytes`",
        "similarity": 0.6521361367815469
      }
    ]
  },
  "editHistory": {
    "fraudScore": 0,
    "editCount": 0,
    "details": "No edits detected"
  },
  "codeVerification": {
    "plausible": true,
    "confidence": 1,
    "reasoning": "The code confirms that the two commands expose `cache_dir` with different types. `cache show --json` serializes a `PathBuf` directly to a string, while `debug paths --json` serializes a `PathInfo` struct to a nested object.",
    "codeEvidence": "In `src/cortex-cli/src/cache_cmd.rs`, `CacheStats` defines `cache_dir: PathBuf` which serializes to a string. In `src/cortex-cli/src/debug_cmd/types.rs`, `PathsDebugOutput` defines `cache_dir: PathInfo` which serializes to an object with `path` and `exists` fields.",
    "screenshotValid": true,
    "screenshotReasoning": "The screenshot analysis tool returned valid: true."
  },
  "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-06}