录好的自动化用了半个月，今天突然报错「找不到按钮」。先别急着重录——大概率是 App 改版了。
传统脚本为什么一改版就废
录制类脚本记的是「第几步、点哪里」：按坐标或控件路径一步步执行。App 一改版，按钮挪了位置、文案换了说法，脚本还按老地址找，自然扑空。
这就是脚本自动化最大的维护成本：界面稍微一动，整条流程重来。
AI 自动化为什么不怕
AnsClaw 的 AI 执行任务前会先「读屏」：认的是屏幕上的文字、图标和结构，而不是写死的坐标。AI 是怎么看懂你手机屏幕的？这篇里有更细的拆解。
所以按钮挪个位置、图标换个样子，AI 依然能按「要做什么」找到它。改版对它来说，只是换了张地图，路还是那条路。
真卡住了，还能自愈
万一某一步实在找不到（比如功能被合并了），AI 会自动接手：重新看屏、重新规划路径，把任务接着走完，不需要你重新录一遍。和「录一次还是现问 AI」里说的口诀配合起来：录好的流程坏了，AI 补位修复。
你能感知到的区别就是：以前报错要人修，现在大多数时候它自己修。
对你意味着什么
录一次不再是「一次性买卖」。日常任务照常跑，App 小改版基本无感；大改版也只需要说一句话调整，而不是从头再来。
💡 记住这句话：脚本认坐标，AI 认内容——坐标会过时，内容不会。
Your recorded automation ran fine for weeks, then one day it fails with "button not found". Don't rush to re-record — the app probably just got updated.
Why traditional scripts break on updates
Recorded scripts remember "step 3, tap there": they follow fixed coordinates or control paths. When an app updates, buttons move and labels change — the script still knocks on the old door.
That's the biggest maintenance cost of scripting: any UI change means starting over.
Why AI automation doesn't mind
Before acting, AnsClaw's AI "reads the screen": it recognizes the text, icons and layout — not hardcoded coordinates. How does AI "see" your phone screen? breaks this down in detail.
So when a button moves or an icon changes, the AI still finds it by what it's for. An update is just a new map for the same road.
And it can heal itself
If a step truly can't be found (say, a feature was merged), the AI takes over: it re-reads the screen, re-plans the path, and finishes the task — no re-recording needed. Pair this with the rule of thumb from "record it or ask AI?": when a recorded flow breaks, the AI steps in to fix it.
The difference you'll notice: errors used to need you; now it usually fixes itself.
What this means for you
Recording is no longer a one-shot deal. Daily tasks keep running; minor updates go unnoticed; major ones need one sentence from you, not a rebuild from scratch.
💡 Remember: scripts follow coordinates, AI follows content — coordinates expire, content doesn't.
