What thinking actually means
Not consciousness. Something far more boring, and far more useful to know.
Same question, same machine. The difference is what happens before it starts talking.
You have heard someone say it. The AI is thinking about it. Chances are you have said it yourself, in a meeting, without anyone stopping to ask what it means.
It is worth knowing, because the answer changes how much you should trust what comes back. And it is not the is it conscious, is it alive question. That is a genuinely interesting conversation and it is a completely different one. This is the mechanical version: when the screen says thinking, what is the thing actually doing?
Short answer: it is writing. Longer answer below.
It did not used to do this
For most of the time these tools have existed, you asked a question and it just started typing. It worked out the most likely next word, then the most likely one after that, and kept going until it stopped. No pause, no working out, nothing resembling a second thought.
That is why the early ones felt confident and thin at the same time. They were answering the way you do when someone catches you in a corridor and you do not want to look like you do not know.
What happens now
The closest human version is your internal monologue. Someone asks you something and you do not answer instantly, you have a little conversation with yourself first. Why are they asking me this. What do I already know here. Hang on, that bit is not quite right. Then you answer. The model does that, except its internal monologue is literally written out as text.
It writes a rough draft
Before it says anything to you, it writes, sometimes hundreds of words. This is the bit nobody sees, and it is the bit people are calling thinking.
It reads its own draft back
It reasons over what it just wrote, picks holes in it, and changes the parts it is not confident about. Same as you rereading an email before you send it.
It can go and check something
The newer models notice a gap mid-thought, go and search for it or open a document you gave them, and then carry on with the answer in hand.
What this will not do
Thinking is checking, in the sense that the model really is reasoning over whether what it just said holds up. But it is checking its own work with the same brain that produced the work. If it set off down a slightly wrong path, the review is happening from inside that same wrong path.
So a model that thinks for longer is more likely to give you a good answer. It is not guaranteed to give you a true one. Those are different claims, and the gap between them is where people get caught out.
Underneath, nothing has changed about the basic trick. It is still predicting the most likely next word. It just gets to do that on a rough draft first, which turns out to matter enormously, and does not turn it into a fact checker.
What to do with this
Let it think when
The answer needs reasoning rather than recall. Comparisons, trade offs, poking holes in a plan, anything you would have taken to a colleague. Accept that it is slower.
Do not bother when
You already know the shape of the answer. Rewrites, summaries, tidying notes. Thinking is overkill and you are only buying yourself a wait.
Most tools now let you choose which one you get, including the one your employer probably gave you. In Copilot it is the Auto button in the top left; in Claude Code it is the effort dial. And whichever you pick, the honest bit above still stands, so the single most useful habit is giving it permission to say it does not know. Thinking longer does not stop a model inventing something. Being allowed to admit the gap does.
The one minute version
It used to answer straight off the top of its head, one word at a time. Now it writes itself a rough draft first, reads it back, changes the bits it is not sure about, sometimes goes and looks something up, and then answers you. That is what thinking means. It makes the answer better. It does not make it right, because it is checking its own work with the same brain that wrote it.