The transmission, not the fuel

Clutch runs in the same sessions where I write Clutch. When a change stalls, it catches the developer stalling, and that developer is me. If it misfires, I am the first it bites. That is the whole warranty.

I wrote once that ADHD is a performance problem. The gap is execution, at the moment you have to act. Then I built the tool that argument implied, and the building taught me the second half.

Think of the mind as a car. The engine has power: the intelligence, the plan, the thing you already know how to do. ADHD does not drain the tank. It is not a fuel problem, it is the transmission. The power is there, and it does not reach the wheels at the moment you press the pedal.

The first versions of Clutch were a manual transmission. Eleven mechanisms, all present, all sound. Every one of them waited for me to reach for it. I had to notice the stall, remember the tool, and engage it by hand. That design assumed the one faculty that is broken. Remembering to press the clutch is the thing I cannot reliably do.

v1.3 is automatic. It reads the session and shifts on its own. You open a cold project and it hands you the branch, your last landed commit, and the one file to pick back up. You circle the same two options for three turns without editing anything, and it names one move that breaks the loop. A test goes red, you reach for git reset —hard, and it puts one beat in the way: the red is a spike of heat, and the smaller move is to bank what still works first.

When it is not sure, it says nothing. The silence is deliberate. A wrong nudge costs more than no nudge, so it stays quiet until the read is clear. It speaks at most twice a session, never counts days, never mentions a streak.

That restraint is the point. A nag lays a brick, and you climb it tomorrow before you can start. Streak apps manufacture the failure they sell the cure for. Clutch fires on zero movement, never on slowness. Slow is legal. You are allowed to sit and think.

Some of it stays manual on purpose. When a task did not happen, it asks whether you flinched or forgot, because guessing wrong there does real harm. It will not pretend to read your mind on the one question where being wrong is expensive.

Building it this way changed what I trust. I stopped believing a mechanism exists just because I designed it well. It counts only when it fires without me. The manual version was a good idea I had to remember to use, and for me that is just one more task.

It was built with AI assistance. It ships as a Claude Code plugin, it carries nothing personal, and it reads only your git state and the session in front of you.

The engine was never the problem. Neither was the fuel. Build the transmission.