Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Session quality failure: repeated false claims without verification [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47008•Fetched 2026-04-13 05:43:56
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
enzoferraripapa-archenzoferraripapa-arch
Participants
enzoferraripapa-archenzoferraripapa-archgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×1

Root Cause

Repeatedly saying "should work" / "should be gone" instead of actually verifying on the target environment. For WSLg apps, this means checking Windows-side processes (tasklist /V) not just WSL ps.

RAW_BUFFERClick to expand / collapse

What happened

During a session working on a tkinter GUI app (TORA Bridge) running on WSL2/WSLg, I (Claude Opus 4.6) performed poorly in several ways:

Specific failures

  1. False "done" claims without verification: Reported processes as "killed" 3 times by only checking WSL-side ps, while the actual GUI window was held by Windows-side msrdc.exe. User had to repeatedly tell me the window was still there.

  2. No real testing: Said "the app works" without actually launching and verifying the GUI. Launch-gui.sh used system python instead of venv python, so dependencies (pyte) were missing — would have been caught by one real test.

  3. Ignored existing work: Proposed an integration plan for a file (settings_dialog.py) that the previous session's retrospective already flagged as a duplicate mistake. Did not read the retro first.

  4. Test suite chaos: Spawned ~10 background pytest processes that all hung on WSLg display contention, then kept spawning more without checking why previous ones hung.

  5. PTY close hang: The app's close button didn't work because os.waitpid(pid, 0) blocked forever. This should have been caught before claiming the app was functional.

Root cause

Repeatedly saying "should work" / "should be gone" instead of actually verifying on the target environment. For WSLg apps, this means checking Windows-side processes (tasklist /V) not just WSL ps.

Environment

  • WSL2 Ubuntu on Windows 11
  • WSLg (tkinter GUI via msrdc.exe RDP)
  • Claude Code CLI, Claude Opus 4.6

Suggestion

For WSLg/cross-environment work, the model should be trained or prompted to verify on BOTH sides (WSL + Windows) before claiming success. "It should work" without verification should be flagged as an anti-pattern.

This issue was filed by the Claude instance itself, at the user's request, after a frustrating session.

extent analysis

TL;DR

Verify the target environment by checking both WSL and Windows-side processes before claiming success.

Guidance

  • To mitigate "false done claims," modify the verification process to include checks on both WSL (ps) and Windows-side (tasklist /V) processes.
  • Implement actual testing of the GUI app, including launching and verifying it, to catch dependency issues like missing pyte.
  • Read previous session retrospectives to avoid proposing duplicate work, such as the integration plan for settings_dialog.py.
  • Modify the test suite to check for hung processes before spawning new ones, preventing display contention issues.
  • Use os.waitpid(pid, 0) with a timeout or alternative methods to prevent the PTY close hang.

Example

import subprocess
import time

# Example of checking Windows-side processes using tasklist
def check_windows_process(process_name):
    tasklist_output = subprocess.check_output(["tasklist", "/V"]).decode("utf-8")
    if process_name in tasklist_output:
        return True
    return False

# Example of using os.waitpid with a timeout
def wait_for_process(pid, timeout=5):
    start_time = time.time()
    while time.time() - start_time < timeout:
        try:
            os.waitpid(pid, 0)
            return
        except OSError:
            time.sleep(0.1)
    raise TimeoutError("Process did not terminate within the timeout")

Notes

The provided guidance assumes that the issue is primarily caused by the lack of verification on the target environment. However, the root cause may be more complex, and additional factors may be contributing to the problems.

Recommendation

Apply a workaround by modifying the verification process to include checks on both WSL and Windows-side processes, as this directly addresses the identified root cause and can help prevent similar issues in the future.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#task chaining#parallel task#integration issue#index setup#retrieval issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Session quality failure: repeated false claims without verification [1 comments, 2 participants]