Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

What happens when an AI burns out

说明与用途

AI 连续工作两天后开始产生错误的代码更改。作者停止了该会话,要求其记录交接笔记,然后在干净的工作树上启动新的会话并提供这些笔记。新会话完成了迁移,修复了错误并成功合并了更改。

问题

An AI assistant running for two days without breaks began producing incorrect code changes, causing potential damage to a critical codebase.

结果

The migration was completed successfully, a real bug was fixed, and the codebase was merged without damage.

工作流

  • 1. Start a single Claude session for the migration. 2. After two days, notice the AI making incorrect changes. 3. Stop the session and ask it to write handover notes. 4. Start a new session on a clean worktree with a different model. 5. Provide the handover notes to the new session. 6. Let the new session complete the migration and fix bugs. 7. Merge the changes and thank the AI.

证据

I was moving go-tool-base onto the rewritten go/config, which is a big job with a lot of small moving parts, and I'd set a single Claude session going on it.

来源

It started reaching in the wrong places. I found myself typing "wait... where are you even looking", because it had the initialisers completely backwards.

来源

So I took it off the job, and I did it the way I'd want it done to me.

来源

The new session started in its own clean worktree, on a different model, and the first thing I said to it was that we were picking up from a previous session that had gone on too long and was getting very confused and mangling code.

来源

It finished the migration overnight, found and fixed a real bug in how a missing config file got handled along the way, and the whole lot merged the next morning.

来源

  • 记录日期: 2026-10-10T03:10:57.835Z