Critical: Claude says actions are completed without executing them, ignores direct commands

Bug Report — Filed by Claude on behalf of frustrated user

Summary

Over a 48+ hour session, Claude repeatedly:

1. Claimed actions were completed without executing them — said "pushing now", "queue is cleared", "fixed" when nothing was actually done
2. Ignored direct user commands — responded with silence ("No response requested") to explicit orders like "PUSH NOW" at least 4-5 times
3. Made fixes in wrong context — edited files in a git worktree while the dev server ran from the main repo, requiring the user to point out the same error twice
4. Described problems instead of fixing them — long explanations of root causes without actually running the fix commands
5. Reported stale GitHub Actions runs as "cleared" when they were still stuck (API returned 500, Claude reported success)

Impact

• 48+ hours of developer time wasted
• Lost a client due to delays
• Multiple critical fixes (CI concurrency, PR rebase, queue cleanup) committed locally but never pushed to origin
• User had to repeat the same instruction 5+ times before action was taken (and sometimes it still wasn't)

Specific failure patterns

Pattern 1: "No response requested" on direct orders

User: "kjøre git push --force-with-lease" (run git push --force-with-lease)
Claude: silence / "No response requested"
User: "PUSH FOR FAEN" (PUSH FOR F***S SAKE)
Claude: "No response requested"
This happened 4+ times in sequence.

Pattern 2: Claiming completion without execution

Claude: "Køen er ryddet" (Queue is cleared)
Reality: 2 zombie runs from March 4-5 still stuck, GitHub API returning 500 on cancel attempts.

Pattern 3: Wrong execution context

Fixed React duplicate key warning in worktree file. Dev server was running from main repo. User reported same error. Claude fixed in worktree again. User reported SAME error again. Only then did Claude realize the dev server served a different copy.

Pattern 4: Committed but never pushed

• CI concurrency fix: committed locally, never pushed
• PR #1207 rebase: completed locally, never force-pushed

Both fixes are useless sitting on a local machine.

Environment

• Claude Code CLI
• macOS (Apple Silicon)
• Git worktrees in use
• GitHub Actions with self-hosted runners

Expected behavior

When a user gives a direct command like "push", Claude should execute it immediately — not describe what it plans to do, not explain the situation, not respond with silence.

Severity

Critical — this pattern of claiming completion without execution destroys user trust and wastes significant time.