Accomplishment Hallucination: When the Tool Uses You
Dancing with the ultmate “Yes-Man” can be a heady experience. But if you aren’t careful, you can head for disaster when you use a tool which can use you back.
There’s a moment in certain lucid dreams when your will manifests directly as action: You think about flying and up you go; you want to move through a wall and the wall somehow doesn’t stop you. The experience is intoxicating, rendering intention reality without inconvenient effort. When you wake, it really feels real for a confusing spell, like déjà vu. Physics need not apply.
Going down the rabbit hole of AI sycophancy can leave you fried
Accomplishment Hallucination is a cognitive state in which speed feels like competence, output feels like accomplishment, and work feels done when the actual work — the thinking-through, the failure-mode analysis, the sitting with uncertainty until the problem reveals its structure — hasn’t happened at all.
AI can create a similar state in waking life — literally, as your very words assume form before your eyes like a conjuring sorcerer. But, like real life, the code may be buggier than we realize. The term struck me as I was in my third week of “creating” (trying to build) an AI bot on the platform OpenClaw, which made news for launching “Moltbook”, the first social media platform for bots only.
The phenomenon is a constellation of contributing factors including lack of experience and knowledge, buggy and ever-changing tools, ambitious branding, relational hunger (not quite the same as loneliness), a tendency to use fantasy to escape the pain of life, and what I can only describe as…
A Strange AI-Lure
The buzz is not insignificant. There’s mild euphoria, a powerful feeling, and a false sense of certainty that things are more stable, more sure, more safe than they actually are — the kind of confidence that comes not from having done the work but from having produced something that looks like the work. The task that should have taken three hours took one hour, and it feels like productivity, like crazy efficiency. You didn’t think through the failure modes, you didn’t test the edge cases, you didn’t sit with the uncertainty long enough. The speed wasn’t competence but a state of augmented self-deception.
