Benoni Defense — Loss

Tuesday, October 6, 2026 · vs cmji · View game on lichess ↗

Before playing a flashy forcing move like that knight to c7 check, spend a few extra seconds specifically asking 'where does the king go, and do I have a follow-up' — if the answer's no, it's not actually a threat, it's just a piece you're about to lose.

• ›Black had just played queen to c7 instead of the sturdier d6, so the position was begging for you to crack it open. Knight to b5 looks active, eyeing d6 and a7, but black just kicks it with a6 and you've burned a move while they catch up on development. The engine wanted the central break with e5 here instead — way more disruptive, and the queen on c7 has no good way to deal with it.
• ›Pushing to d6 grabs space but it just... hangs there undefended. Black can take it with the bishop for free, and while they actually grabbed a pawn on e4 instead a move later, that was their choice to make, not something you forced. Bishop to c4 instead develops with real pressure on f7 and keeps the pawn structure intact — safer and more useful than the pawn lunge.
• ›Seven seconds for knight to c7 check tells the story — that's not enough time to see the whole idea through. It looks like a fork on the back rank, but the king just steps away and the knight is simply lost for nothing, a near six-point swing in one move. Queen to e2 was sitting right there, keeping you comfortably ahead instead of handing the game its turning point.
• ›A 66-second think here shows you knew the position needed care — you just picked the wrong fix. Rook to c1 looks like normal development, but it's a tempo too slow; queen to d3 was the move that kept you active and in the fight after the earlier damage. Sometimes the long think isn't the problem, it's that the candidate move itself needed to be more central, more forcing.