So I was working on a Next.js project today, and I asked Claude (via Cursor) to help me with something.

What happened next was... something else.

Claude started checking for TypeScript errors. Cool, that's helpful. Then it checked again. And again. And again.

I watched in horror as it kept running the same command over and over:

npx tsc --noEmit 2>&1 | grep -E "(error|Error)" | head -20 || echo "No TypeScript errors found"

Each time it returned OUT 0 (no errors found), but then it would just... run it again. And again. And again.

Six times in a row. The exact same command. The exact same result. Just checking, checking, checking, like it was stuck in some kind of validation purgatory.

It was like watching a robot have an existential crisis about whether TypeScript errors exist or not. Schrödinger's type errors, I guess?

"Are there errors? Let me check... No? But what if I'm wrong? Let me check again... Still no? But what if they appeared in the 0.5 seconds since I last checked? Better check again..."

I finally had to stop it. My thread looked like a TypeScript error checker's fever dream - just the same green "Bash Check for TypeScript errors" block repeating into infinity.

Has anyone else experienced this? Is Claude just really committed to type safety, or did I accidentally create a recursive nightmare?

TL;DR: Asked Claude for help, it got stuck in a Groundhog Day loop running the same TypeScript check command 6+ times. Send help (or coffee).