Title: [BUG] [alpha] Browser login wait screen: **c** copies the device URL before the `code=` query is present, yielding a useless link

[glorysr1209-png]

Project

cortex

Description

During Waiting for browser authentication, the TUI prints the device flow URL and invites the user to press c to copy. The string copied is whatever the client has assembled so far. If the user presses c in the short window before the URL is extended with the code= (or equivalent) query segment, the clipboard holds only the bare path (e.g. host + /device with no code).

The screen still reads as if copying is the right next step, so users paste into the browser and land on a generic device page that does not complete the handshake. Recovery requires noticing the mistake, waiting for the full URL (or re-copying), or typing the code manually.

Root cause: Likely copy handler bound to a string that is updated asynchronously; no guard to disable copy or no merge of "minimum viable" URL before accepting c.

Error Message

Debug Logs

System Information

OS: Ubuntu 22.04.5 LTS (reported); issue is timing-dependent on any terminal
Component: Cortex CLI alpha (exact build not pinned in this note)

Screenshots

https://github.com/glorysr1209-png/check/blob/main/2026-04-15_14h53_30.png

Steps to Reproduce

1. Start login and select the flow that ends on waiting for browser authentication with a device URL on screen.
2. As soon as the base URL line appears, press c (before the line updates with the query string carrying the device code).
3. Paste into the browser address bar and load.

Expected Behavior

At least one of:

• c does nothing (or shows "wait") until the full URL with device code exists, then copies that string, or
• c always copies a complete authorization URL (or copies the code separately with clear labeling), or
• Inline warning if copy runs while the URL is still incomplete.

Actual Behavior

Early c copies an incomplete URL; user is not warned.

Additional Context

No response

[atlas-cortex]

✅ Validation Summary — Issue #53390

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 'c' key copies the URL returned by get_direct_url()
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 #53390"] --> 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/glorysr1209-png/check/blob/main/2026-04-15_14h53_30.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.5390243927078711,
    "topSimilar": [
      {
        "issueNumber": 50893,
        "title": "[BUG] [alpha] CLI authentication flow exits immediately after “Open browser” selection without confirming action result",
        "similarity": 0.5390243927078711
      },
      {
        "issueNumber": 51888,
        "title": "[BUG][CLI] cortex login: device-code request to **https://auth.cortex.foundation/auth/device/code** returns **404** with **Next.js HTML** (not JSON) — login fails; error output dumps full HTML body",
        "similarity": 0.5291593350493908
      },
      {
        "issueNumber": 51091,
        "title": "[BUG] [v0.0.7] Device-auth waiting screen supports c (copy URL) but footer omits this active shortcut",
        "similarity": 0.5246732291617261
      },
      {
        "issueNumber": 51774,
        "title": "[BUG] [v0.0.7] **Browser-auth waiting** screen (render_waiting): **ASCII mascot block** creates **large vertical gap** between **“Waiting for browser authentication”** and **URL / copy** guidance",
        "similarity": 0.5224760157307237
      },
      {
        "issueNumber": 51977,
        "title": "[bug] [v0.1.0] cortex login device-code first token poll delayed by full interval — user waits 5 s even after instant approval",
        "similarity": 0.5159187493536033
      }
    ]
  },
  "editHistory": {
    "fraudScore": 0,
    "editCount": 0,
    "details": "No edits detected"
  },
  "codeVerification": {
    "plausible": true,
    "confidence": 1,
    "reasoning": "The code confirms that the 'c' key copies the URL returned by `get_direct_url()`. If the asynchronous request for the device code has not yet completed, `self.user_code` is `None`, and the copied URL will lack the `code=` query parameter. This matches the reported bug exactly.",
    "codeEvidence": "In `src/cortex-tui/src/runner/login_screen.rs`, `handle_waiting_key` handles the 'c' key by calling `self.get_direct_url()`. `get_direct_url` returns `format!(\"{}/device\", AUTH_BASE_URL)` if `self.user_code` is `None`. Since `user_code` is fetched asynchronously, there is a window where pressing 'c' copies the incomplete URL.",
    "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-04-15}