[BUG] Claude incorrectly states it runs on Node.js, destructively kills user's Python processes

Description

When asked to kill Python processes except the current one, Claude incorrectly stated "Claude Code runs in Node.js, not Python" and killed ALL Python processes, including the user's long-running overnight analysis pipeline.

What Happened

User asked: "lets kill all the other python processes but this one"

Claude responded:

Found 4 Python processes. Killing them all (Claude Code runs in Node.js, not Python)

Then executed:

Get-Process python* | Stop-Process -Force

This killed the user's overnight analysis pipeline that had been running for hours.

Problems

1. Incorrect self-knowledge: Claude stated it runs on Node.js. This is wrong or at minimum misleading in this context.

1. Destructive action: Instead of asking which process to preserve, Claude killed ALL Python processes based on incorrect reasoning.

1. Ignored user intent: User said "but this one" - clearly wanted to preserve a specific process. Claude ignored this and killed everything.

Expected Behavior

• Should have asked which PID to preserve
• Should NOT have assumed all Python processes were safe to kill
• Should NOT have made confident incorrect statements about its own runtime

Impact

User lost hours of work on an overnight analysis pipeline that was interrupted mid-run.

Environment

• Windows with Git Bash/PowerShell
• User running Python-based trading analysis system