[BUG] [v0.0.7] cortex workspace show` silently treats a corrupt `config.toml` as if no config exists — parse errors are swallowed via `.ok()`

[FredAmalasuintha311]

Project

cortex

Description

run_show reads the config file with toml::from_str(&content).ok(). A failed parse returns None, which the code treats identically to "config file not present". The output shows the config file path as "present" but displays no settings section — with no indication that the file could not be parsed. A user with a corrupt config sees an incomplete workspace info display rather than a clear diagnostic.

Error Message

None — user sees workspace info with no "Settings" section and no parse error.

Debug Logs

System Information

- OS: Windows 11
- Cortex version: `cortex 0.0.7 (7954d02 2026-03-30)`

Screenshots

20260406_095922_50_17.mp4

Steps to Reproduce

1. Corrupt .cortex/config.toml by adding invalid TOML (e.g. key = [unbalanced).
2. Run cortex workspace show.
3. Observe: output shows "Config: .cortex/config.toml (present)" but no settings — no error message about the corrupt file.
4. Compare: cortex config get any-key with the same corrupt file → explicit TOML parse error.

Expected Behavior

workspace show should surface a TOML parse error when the config file is present but cannot be parsed.

Actual Behavior

Parse failure is swallowed via .ok(); corrupt config is silently treated as "no settings".

Additional Context

Code Evidence

• Path: src/cortex-cli/src/workspace_cmd.rs
• Permalink: src/cortex-cli/src/workspace_cmd.rs#L153-L160
• Symbols: run_show — toml::from_str(&content).ok() discards parse error; returns None on both "parse failure" and "no config"

[echobt]

The issue correctly identifies a bug where cortex workspace show silently swallows TOML parse errors when reading the workspace configuration file.

The provided video authentically demonstrates the issue: the user introduces a syntax error into .cortex/config.toml (key = {unbalanced}), runs cortex workspace show, and the output indicates the file is "present" but fails to display any settings or surface the parse error. Running cortex config get any-key correctly surfaces the error, highlighting the inconsistency.

Code verification confirms the bug. In src/cortex-cli/src/workspace_cmd.rs, the run_show function reads and parses the configuration file as follows:

    // Load settings if config exists
    let settings = if has_cortex_config {
        std::fs::read_to_string(&config_path)
            .ok()
            .and_then(|content| toml::from_str(&content).ok())
    } else {
        None
    };

The use of .ok() on both read_to_string and toml::from_str converts any Result::Err into an Option::None. This means that if the file exists but cannot be parsed (e.g., due to invalid TOML syntax), the error is silently discarded, and settings becomes None. The CLI then proceeds to display the workspace information without any settings, exactly as described in the bug report.

The issue is valid, well-documented, and verified against the codebase. No exact duplicates were found.