[BUG] [v0.0.7] `/goto` with non-numeric argument: system line reads `Error: Invalid message number: …` — two colons reads awkwardly

[lucaserevo]

Project

cortex

Description

hen /goto receives an invalid argument, the handler formats an inner message like Invalid message number: <token>. The TUI then wraps slash-command errors with a generic Error: {msg} prefix for system messages. Concatenating these produces a line with two colons in close proximity (Error: Invalid message number: …), which reads like a formatting mistake and makes the error harder to scan quickly. The underlying validation may be correct, but the presentation violates basic CLI/TUI copy hygiene and looks unpolished in a high-visibility error path.

Impact: minor UX papercut; reduces trust in error quality; affects readability in dense transcripts.

Error Message

Debug Logs

System Information

OS: Windows 11

Screenshots

https://github.com/springoliver/bounty_challenge_report_image/blob/main/49103.png

Steps to Reproduce

1. Open Cortex TUI (session view with message timeline as appropriate for /goto).
2. Type /goto followed by a negative numeric value or invalid value **
3. Read the red error line — note Error: and number: both use a colon.

Expected Behavior

One clear sentence without stacked colon labels, for example any of:

• Error — Invalid message number (…) with the value in parentheses, or
• Invalid message number on one line and the value on the next, or
• Drop the inner …: and use quotes around the token.

(Product / style guide chooses the exact string.)

Actual Behavior

Error: prefix + message that already ends with …: before the operand → double colon in one line.

Additional Context

No response

[atlas-cortex]

✅ Validation Summary — Issue #53425

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. In `src/cortex-tui/src/commands/executor/navigation.r
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 #53425"] --> 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/springoliver/bounty_challenge_report_image/blob/main/49103.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.5493215671408267,
    "topSimilar": [
      {
        "issueNumber": 53004,
        "title": "[BUG] [v0.0.7] Inconsistent Capitalization in Help Modal: Confirm/select vs Standard Title Case",
        "similarity": 0.5493215671408267
      },
      {
        "issueNumber": 51608,
        "title": "[BUG] [v0.0.7] Go To Message number field lacks clear index/range guidance",
        "similarity": 0.5476841367751052
      },
      {
        "issueNumber": 52057,
        "title": "# [BUG] [v0.0.7] Narrow terminal causes long numeric error tokens to wrap mid-token and lose readability",
        "similarity": 0.5383418260606504
      },
      {
        "issueNumber": 51835,
        "title": "[BUG] [v0.0.7] cortex logs --clear --keep-days <fraction> shows low-level parse error instead of clear integer-only validation message",
        "similarity": 0.5372088603159927
      },
      {
        "issueNumber": 51212,
        "title": "[BUG][0.1.0] /goto failure should scroll view at the bottom so error is visible",
        "similarity": 0.5359361210756599
      }
    ]
  },
  "editHistory": {
    "fraudScore": 0,
    "editCount": 0,
    "details": "No edits detected"
  },
  "codeVerification": {
    "plausible": true,
    "confidence": 1,
    "reasoning": "The code confirms the bug. In `src/cortex-tui/src/commands/executor/navigation.rs`, the `/goto` command returns `CommandResult::Error(format!(\"Invalid message number: {}\", n))` when the argument is not a valid number. Then, in `src/cortex-tui/src/runner/event_loop/commands.rs`, the `handle_command_result` function processes `CommandResult::Error(err)` by prepending `\"Error: \"` to it. This results in the string `\"Error: Invalid message number: <n>\"`, which contains two colons as described in the bug report.",
    "codeEvidence": "src/cortex-tui/src/commands/executor/navigation.rs:29: CommandResult::Error(format!(\"Invalid message number: {}\", n))\nsrc/cortex-tui/src/runner/event_loop/commands.rs:26: CommandResult::Error(err) => { self.add_system_message(&format!(\"Error: {}\", err)); }",
    "screenshotValid": true,
    "screenshotReasoning": "The screenshot shows the Cortex TUI with the error message \"Error: Invalid message number: -1\" displayed in red at the bottom, which matches the described behavior and is a valid user-facing 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-04-24}

[DanielButler1]

Fix submitted upstream: CortexLM/cortex-code#238

Verification:

• rustfmt --edition 2024 --check src/cortex-tui/src/commands/executor/navigation.rs src/cortex-tui/src/commands/executor/tests.rs
• git diff --check
• cargo test -p cortex-tui commands::executor::tests::test_goto_validation
• cargo check -p cortex-tui