Plan mode survives as a built-in mod you can override
Thariq's compromise after floating removal, with Matt Pocock arguing planning belongs in userland.
Thariq floated killing plan mode and reusing the shift+tab hotkey for effort levels, and has now landed on a compromise. The plan is to make plan mode into a built-in mod, and to allow mods to add new modes or override shift+tab.
others prefer the UX of entering a mode where Claude is just thinking & brainstorming with you
His reason for the change is the shape of the feedback he got. Many people, he said, are planning themselves and do not need plan mode. Others prefer the UX of entering a mode where Claude is just thinking and brainstorming with them. Neither group is wrong about their own workflow, and no single default serves both.
How it got here
The original pitch was blunter. Thariq said he did not think the models need plan mode anymore, and asked plan mode diehards to explain why they still wanted it. That post is what produced the split, and we covered the earlier round of it.
Matt Pocock's answer was to kill it and let users plan how they want. His argument was that planning is a userland concern, because the way people plan will be custom for the task, the org and the person.
The mod version is close to what Pocock asked for without the breakage. Plan mode still exists for the people who like the mode UX, but it stops being a fixed default that has to be defended against every alternative workflow, and the hotkey stops being reserved for one opinion about how planning should work.
For working engineers
The thing worth copying here is not the feature, it is the resolution. A contested workflow opinion became a removable, overridable mod instead of a hardcoded mode, which means the maintainers do not have to pick a winner and the people with a different process do not have to fight the tool.
It also means the shift+tab slot is now contested surface. If mods can override it, the behaviour you get depends on which mods you have installed, which is a small tax on shared configs and on anybody writing instructions for a team.
Thariq described this as his plan, not as shipped behaviour, so the details of how mods register modes are not public yet. Whether plan mode as a mod ends up being the thing people actually keep enabled is the open question, and nobody knows yet.
Don't mandate a 'mode' and users AND maintainers will be happier
Have the good opinion, not the loud one
One email a day. Under three minutes. What working engineers found out about coding with AI.