Anthropic engineer Osmani warns that the stronger AI becomes, the more easily humans fall into cognitive surrender

Osmani worked at Google for more than 14 years, where he was responsible for Chrome developer experience and Google Cloud AI-related business, and currently works on Claude Code-related work at Anthropic.

Osmani said he is a firm supporter of AI agent workflows and often runs multiple agents simultaneously in his daily work. But he has noticed a worrying change: as AI models keep improving, obvious errors in their output are becoming rarer, making it harder for humans to stay vigilant.

In the past, people usually had to go through information gathering, analysis, and judgment to arrive at an answer, but now this process can be compressed into a few seconds. AI-generated content is often well-structured, fluently expressed, and correct most of the time, which makes it increasingly easy for users to skip independent thinking and verification.

He divides the states of human AI use into three levels: first, "Cognitive Offloading," that is, handing tasks to AI to complete while still being responsible for the results; second, "Deferral," that is, no longer treating AI output as a hypothesis that needs verification but directly using it as the basis for the next step of work; and finally, "cognitive surrender," that is, AI output gradually becomes the user's own judgment, and the user no longer even considers it necessary to check.

Among these, the concept of "cognitive surrender" was first proposed by Wharton School researchers Steven Shaw and Gideon Nave.

Osmani believes that this shift often does not happen suddenly but gradually forms through continuous use of AI. A user may carefully read the first AI report, only skim the second, and by the third even check only the outline. Ultimately, when someone asks about a specific conclusion, the user may find that they cannot explain the logic behind it at all.

He links this phenomenon to "Cognitive Debt." In software development, AI can generate large amounts of code and tests may all pass, but team members' understanding of the system architecture and implementation logic keeps diminishing. Until one day the system needs to be modified, developers discover that no one truly understands how certain features work.

However, Osmani does not believe developers need to memorize every detail of a huge codebase. He points out that the Claude Code team also uses AI when needed to rebuild understanding of specific code modules. What truly matters is not always mastering all knowledge, but knowing what you do not understand and having the ability to understand it again.

As for how to avoid "cognitive surrender," Osmani suggests that before asking AI complex questions, humans should first form their own preliminary hypotheses rather than relying entirely on AI for answers. Even if the initial guess is not accurate, it can help users retain a basis for independent judgment when receiving AI results.

In software development, Osmani believes the bottleneck in the AI era is shifting from writing code to verifying whether code is correct.

At present, AI agents can already autonomously write code, run tests, read error messages, and revise repeatedly until tests pass. But the problem is that the tests themselves may also be written by AI. If the test logic contains the same errors as the code, even if all tests show passing, it cannot prove that the software has no problems.

Therefore, he emphasizes that developers should not only focus on whether tests pass but also clarify what the tests actually prove and which risks they do not cover. For deliverables from AI, the acceptance criteria should be verifiable evidence such as actual test results, run logs, and screenshots, rather than a plausible-looking summary generated by AI.

Osmani also proposes that developers should require agents to explicitly list the decisions they made autonomously during task execution, the assumptions they adopted, and the conditions they ignored, because this content usually does not appear in the final work summary.

As AI becomes able to execute more and more tasks simultaneously, another problem begins to emerge. Osmani calls it the "Orchestration Tax," namely the gap between the speed at which AI generates results and the speed at which humans can carefully review and are willing to take responsibility for them.

When AI-generated work keeps piling up and humans no longer have enough time to review it, continuing to increase the number of agents cannot solve the problem. He believes that in this case, teams should improve automated verification mechanisms or appropriately slow the pace of task generation.

Osmani also warns that the high degree of automation of AI may cause humans to gradually give up practicing their original skills. He suggests that developers try writing some code without AI every week, re-examine the skills they have stopped practicing every month, and judge which abilities are still worth retaining.

He also cites Anthropic's research on internal engineers' and researchers' use of AI, pointing out that there is a "supervision paradox": supervising Claude requires programming ability, but excessive use of AI may cause these abilities to degrade.

Osmani emphasizes that these views do not mean AI use should be reduced. In tasks where the cost of error is low, fully handing them to AI is fine, but when it comes to major decisions involving investment, career choices, product safety, or affecting other people, humans should still retain key judgment authority.

In his view, future AI models may be better than humans at spotting errors, but this cannot eliminate human responsibility. Deciding what product to develop, why it is worth developing, whom it will affect, and what cost one is willing to bear for it still require human choices.