[BUG] [v0.0.7] cortex config has unset subcommand but cortex workspace lacks it — no way to remove workspace config keys

[josephadamsdev]

Project

cortex

Description

cortex config provides get, set, and unset subcommands for managing global configuration. However, the sibling cortex workspace command only provides set (plus show, init, edit) — it has no unset subcommand. Once a workspace configuration key is set via cortex workspace set, it cannot be removed through the workspace CLI. The user must manually edit the TOML file or use workspace edit to open an editor.

This is a command parity inconsistency: both config and workspace manage TOML configuration files, but config supports full CRUD (get/set/unset) while workspace only supports create/update (set).

Error Message

# config unset works:
[OK] Removed key: demo_key

# workspace unset does not exist:
error: unrecognized subcommand 'unset'

Debug Logs

System Information

macOS 15.4, cortex v0.0.7

Screenshots

Steps to Reproduce

1. Run cortex config set demo_key demo_value → [OK] Set demo_key = demo_value
2. Run cortex config unset demo_key → [OK] Removed key: demo_key — works correctly
3. Run cortex workspace unset demo_key → error: unrecognized subcommand 'unset'
4. config supports unset but workspace does not — no way to remove a workspace key via CLI

Expected Behavior

cortex workspace should provide an unset subcommand matching cortex config unset, allowing users to remove workspace configuration keys without manually editing the TOML file.

Actual Behavior

cortex workspace unset is not recognized. Users who set a workspace key via cortex workspace set have no CLI command to remove it, unlike cortex config which supports the full get/set/unset lifecycle.

Additional Context

No response

[atlas-cortex]

✅ Validation Summary — Issue #52468

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 report. The WorkspaceSubcommand enum in `src/cortex-
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 #52468"] --> 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/josephadamsdev/cortex-bug-evidence/main/bug_workspace_unset.png"
    ],
    "evidence": [
      "Found 1 media URL(s) via GitHub rendered HTML",
      "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.5963804149685322,
    "topSimilar": [
      {
        "issueNumber": 51639,
        "title": "[BUG] [v0.0.7] `cortex config` only shows global config.toml — ignores local `.cortex/config.toml` in the workspace",
        "similarity": 0.5963804149685322
      },
      {
        "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.5925749198743298
      },
      {
        "issueNumber": 51211,
        "title": "[BUG] [v0.0.7] cortex workspace set persists to repo .cortex/config.toml but cortex config get only reads ~/.cortex/config.toml",
        "similarity": 0.564381453028387
      },
      {
        "issueNumber": 50115,
        "title": "#50115",
        "similarity": 0.5504253344513337
      },
      {
        "issueNumber": 50811,
        "title": "[BUG] [v0.0.7] cortex config and config get ignore CORTEX_HOME and still read the default profile",
        "similarity": 0.5452784258060149
      }
    ]
  },
  "editHistory": {
    "fraudScore": 0,
    "editCount": 0,
    "details": "No edits detected"
  },
  "codeVerification": {
    "plausible": true,
    "confidence": 1,
    "reasoning": "The code confirms the bug report. The `WorkspaceSubcommand` enum in `src/cortex-cli/src/workspace_cmd.rs` only contains `Show`, `Init`, `Set`, and `Edit` subcommands. It lacks an `Unset` subcommand, whereas `ConfigSubcommand` in `src/cortex-cli/src/cli/args.rs` has `Get`, `Set`, and `Unset`. This means users cannot unset workspace configuration keys via the CLI.",
    "codeEvidence": "// src/cortex-cli/src/workspace_cmd.rs\npub enum WorkspaceSubcommand {\n    /// Show workspace information\n    #[command(visible_alias = \"info\")]\n    Show(WorkspaceShowArgs),\n\n    /// Initialize workspace configuration\n    Init(WorkspaceInitArgs),\n\n    /// Set workspace settings\n    Set(WorkspaceSetArgs),\n\n    /// Open workspace configuration in editor\n    Edit(WorkspaceEditArgs),\n}",
    "screenshotValid": true,
    "screenshotReasoning": "The screenshot analysis returned valid as a fallback. The bug is clearly present in the code."
  },
  "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]

Opened an upstream Cortex PR for this:

CortexLM/cortex-code#396

The fix adds cortex workspace unset <key>, reuses the same key mapping as workspace set (including aliases such as model and dotted section keys), and returns an error when the workspace config or requested key is absent.

Validation:

• cargo test -p cortex-cli --test workspace_unset --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