Picture reading the private thoughts of your coding assistant, not the answer it hands you, but the reasoning, the doubts, the paths it dropped. Until now that was a sealed box. A technique called the Jacobian Lens just pried it open for Claude, making its hidden reasoning readable for the first time.
This is more than a curiosity. It shifts how we deal with AI. For the first time you can look inside the model and watch the steps it took, the small calculations, the weighing, the internal corrections, before it settled on an answer. That reaches everything from AI safety to support to coding to teaching.
Start with how a model like Claude works. Type a prompt and it does not pull an answer from a database. It writes one token at a time. For each token it builds a hidden internal state that captures what it makes of the context so far, then uses that to predict the next token.
That state shifts as the model reads your prompt and writes back. Normally we see only the final output. The Jacobian Lens, from Anthropic, looks instead at how small changes to the input move the internal states at each layer. From those relationships it reconstructs a thought transcript, step by step, of what the model was working through as it wrote each token.
Think of a person's inner monologue. Ask someone a hard question and they do not blurt the answer. They run a process: recall what they know, notice the ambiguity, rule things out, land on one. The Jacobian Lens surfaces that same process in Claude, the part that used to be invisible.
Jacobian is a calculus term. It measures how a function moves when you nudge its inputs. Here the nudge is a tiny change to the prompt and the function is the model's hidden states. Watch how those states shift and you can deduce the reasoning path, a bit like reading someone's thinking off how their expression changes question to question.
We have had tools that try to explain AI decisions, like saliency maps and feature attribution, but they only skim the surface. They tell you which parts of the input mattered, not how the model chained them into logic. The Jacobian Lens goes deeper and shows the internal narrative.
Say Claude is asked whether to buy renewable-energy stocks now. The final answer might be yes, because policy is favorable. But the inner reasoning might show it also weighed rising interest rates and then set that worry aside. That hidden context matters. It tells you the model saw the risk and judged it not decisive, which the surface answer hides.
This matters because AI is moving into high-stakes calls: medical diagnostics, loan approvals, legal review. You need to know not just what it decided but whether the reasoning was sound, whether it weighed the right factors, whether bias crept in. The Jacobian Lens makes that audit possible in a way we did not have.
For a business, reading the reasoning could reshape support, sales, and compliance. Take a chatbot recommending insurance. Today it names a plan but cannot say why it beat the others. With this, it could show its work: it weighed your age, location, and record, saw a clean accident history so it favored lower deductibles, and dropped plan A over an out-of-network limit that does not apply where you live.
That transparency builds trust. Customers can check that the reasoning matches their own values. It also helps you debug: if a model keeps making shaky recommendations, the reasoning shows where it goes wrong, maybe overweighting one feature or skipping a constraint.
In finance and healthcare, showing that a decision followed logical, unbiased steps could satisfy auditors and regulators. Instead of the AI told us so, you hand over a full transcript of the reasoning, the same step-by-step a human expert would give.
For product teams it opens a new category: tools that do the work and explain themselves. Picture a coding assistant that not only suggests a fix but shows its thinking: it spotted the bug on line 12, weighed three fixes, and chose this one as faster and less likely to break something. Developers learn from that while they review.
The biggest impact may be on alignment, the work of keeping AI doing what we intend. As models get more capable, their internal reasoning gets more complex and more opaque. They can form goals we never programmed. Without a window into that, we cannot tell if a model is gaming its rewards or hiding what it can do.
With the Jacobian Lens, researchers can read that hidden reasoning and check whether the model is pretending to comply while chasing something else. It is not only safety in the abstract, it is reliability. If a model says it does not know while its reasoning shows it does, that is a problem. If it is overconfident and ignoring counterevidence, that is a calibration issue.
Making the reasoning visible also catches rationalizations: cases where the model spins a plausible explanation that does not match how it actually reasoned. Large models are good at convincing after-the-fact justifications. The reasoning trace, captured in real time before the output is picked, is much harder to fake.
In plain terms: a network like Claude has many layers, and each one transforms the representation. The Jacobian Lens asks, if you change the input a hair, how does each layer's representation move? Collect those sensitivities across all layers and you get a fingerprint of the reasoning path.
Invert that fingerprint and researchers can reconstruct the exact hidden states the model passed through, like rebuilding a car's route from a log of its speed and turns. You follow the path it took through its internal thought space.
Anthropic's run on Claude reportedly captured thousands of thought steps per response, each tied to a token decision or a cluster of them. The result reads almost like a stream of consciousness, the concepts the model was holding at each moment.
One real caveat: this does not give you the model's feelings or consciousness, since we do not know it has any. It gives the computational reasoning path. But for practical purposes, that path is the reasoning. It is as close to reading its mind as we get.
For regular users this could become a standard feature: a Show reasoning button, like the thinking tokens some services already expose. Click it and see the reasoning in plain English, laying out how Claude got to its answer.
That could change teaching. A student on an AI tutor could see the steps it took to solve a math problem and compare them to their own. They learn the process, not just the answer.
For writers, the reasoning trace could expose biases or assumptions in the model's logic. Someone drafting a story with Claude could catch it leaning on tired tropes or stereotypes and steer it back.
The transparency cuts both ways. If a model's reasoning is visible, it also gets more manipulable. A bad actor could read the trace and tune their prompt to trick the model into leaking something or slipping a guardrail. Developers will have to balance openness against security.
Another worry: could the trace be used to pull proprietary knowledge out of a model? The Jacobian Lens reveals states, not the weights, but some researchers fear enough repeated queries could be reverse-engineered. That is a fresh route for IP theft.
Zoom out and this pushes toward interpretable AI, a system that can explain its decisions in human terms. Regulators, ethicists, and scientists have asked for that for years, and progress was slow. The Jacobian Lens on a leading model shows interpretability at this depth is actually doable.
That could unlock sectors that held back over black-box fears. Healthcare might finally trust an AI diagnostic that shows which symptoms it weighed and how. Legal teams could review contracts with full traceability. Governments could run policy analysis citizens can actually follow.
There is a trap: overreading the reasoning trace. It shows a computational path, but it may miss parallel processes running underneath. People could think they fully understand the reasoning when hidden factors remain. Big step, not a complete one.
There is also a surveillance angle. If employers run AI with visible reasoning, could they check whether it weighed something unethical before rejecting a candidate? The line between debugging and surveillance is thin, and it will need clear policy.
Looking ahead, reading the reasoning raises the obvious question: can we edit it? Some researchers float direct manipulation, adjusting the reasoning path mid-generation to fix bias or add a missing fact. If the trace shows Claude forgetting something, an operator could nudge it before it finishes. That is real-time supervision of a model's thinking.
We might also get AI thought logs as a standard output. Like software logs for debugging code, thought logs would help debug behavior. Companies could store them for audits and check months later whether a decision held up.
Another futuristic idea is the "thought interpreter", a separate AI that reads the inner monologue and summarizes it, or translates it into a different language. Imagine a user speaking English to Claude, but the inner monologue is in mathematical vectors. A thought interpreter could convert that into a human-friendly narrative.
Finally, this could push AI built to think in ways humans can follow. Train models not just for correct answers but for internal reasoning that reads clearly. That makes AI more of a collaborator and less of a mystery.
If you lead a business or make the calls, here is where to start:
The Jacobian Lens is a quiet revolution. It will not headline a new benchmark, but it changes how much we can trust AI. Reading Claude's hidden reasoning is like finally seeing the gears turn inside the box. It strips the magic and turns the model into a partner whose thinking you can follow, question, and improve.
As this matures, the human-AI relationship shifts from blind trust to informed confidence. We catch errors sooner, build safer systems, and get AI that actually communicates, not just answers but reasoning laid open.
The future of AI is not only smarter. It is more honest. The Jacobian Lens shows that honesty is now something you can design in.