[BUG] [v0.0.7] cortex workspace show ignores .cortex/config.json and reports no config present

[15Kentucky]

Project

cortex

Description

In a workspace that contains .cortex/config.json, cortex workspace show --json reports that no Cortex config is present. In the same directory, cortex debug config --json finds that exact local config file and reports local_config_exists: true. The two commands disagree about whether the project config exists.

Error Message

None.

Debug Logs

None.

System Information

• OS: Windows 11
• Cortex version: cortex 0.0.7 (ac6398e 2026-02-05)

Screenshots

Steps to Reproduce

1. Create a workspace with .cortex/config.json.
2. Run cortex workspace show --json.
3. Run cortex debug config --json in the same directory.

Expected Behavior

Both commands should agree that the local project config exists.

Actual Behavior

cortex workspace show --json reports has_cortex_config: false and config_path: null, while cortex debug config --json reports the same .cortex/config.json file as local_config_exists: true.

Additional Context

The engine supports .cortex/config.json, but workspace show only checks .cortex/config.toml.

[GreyforgeLabs]

Fix PR opened: CortexLM/cortex-code#391

Summary:

• workspace show now detects .cortex/config.json when .cortex/config.toml is absent.
• TOML remains the preferred workspace config file, with JSON settings parsed when the JSON path is discovered.
• Added a CLI regression test for workspace show --json with only .cortex/config.json.

Validation:

• cargo test -p cortex-cli --test workspace_show --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 #51499

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 the bug. workspace show hardcodes the check for `.cortex/con
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 #51499"] --> 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/15Kentucky/cortex-evidence/upload/cortex/2026-04-09/workspace-show-config-json-missing-20260409.png",
      "https://raw.githubusercontent.com/15Kentucky/cortex-evidence/upload/cortex/2026-04-09/debug-config-sees-config-json-20260409.png"
    ],
    "evidence": [
      "Found 2 media URL(s) via GitHub rendered HTML",
      "2 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.6164702394282786,
    "topSimilar": [
      {
        "issueNumber": 50811,
        "title": "[BUG] [v0.0.7] cortex config and config get ignore CORTEX_HOME and still read the default profile",
        "similarity": 0.6164702394282786
      },
      {
        "issueNumber": 51485,
        "title": "[BUG] [v0.0.7] `cortex workspace show` reports model as null while `cortex debug config` shows the effective model value",
        "similarity": 0.6111545379261385
      },
      {
        "issueNumber": 51208,
        "title": "[BUG] [v0.0.7] cortex workspace set writes to project-local .cortex/config.toml but cortex config get reads only from global ~/.cortex/config.toml — values disappear across commands",
        "similarity": 0.5863272257759634
      },
      {
        "issueNumber": 50727,
        "title": "[BUG] [v0.0.7] `cortex debug skill --json` definition object drops model, allowed_tools, denied_tools, and timeout fields from SKILL.toml",
        "similarity": 0.5703178740806533
      },
      {
        "issueNumber": 51213,
        "title": "[BUG] [v0.0.7] cortex github uninstall treats yes as cancel — only a single-letter y confirms",
        "similarity": 0.5666192151132049
      }
    ]
  },
  "editHistory": {
    "fraudScore": 0,
    "editCount": 0,
    "details": "No edits detected"
  },
  "codeVerification": {
    "plausible": true,
    "confidence": 1,
    "reasoning": "The code confirms the bug. `workspace show` hardcodes the check for `.cortex/config.toml` and ignores `.cortex/config.json`. Meanwhile, `debug config` correctly checks for both `.toml` and `.json` extensions. This causes the two commands to disagree on the existence of the local config file when only `config.json` is present.",
    "codeEvidence": "src/cortex-cli/src/workspace_cmd.rs hardcodes `config.toml` in `run_show`:\n```rust\n    let config_path = cortex_dir.join(\"config.toml\");\n    let has_cortex_config = config_path.exists();\n```\nsrc/cortex-cli/src/debug_cmd/handlers/config.rs checks both `config.toml` and `config.json` in `run_config`:\n```rust\n        let local_toml = d.join(\".cortex/config.toml\");\n        let local_json = d.join(\".cortex/config.json\");\n```",
    "screenshotValid": true,
    "screenshotReasoning": "The screenshots show the actual CLI output demonstrating the discrepancy between `workspace show` and `debug config` as described in the bug report."
  },
  "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}