跳到正文
DEV Community· Rulestack·· 8 天前AI 評分27

編碼智能體陷入循環時,該糾正它還是重開工作階段?

When your coding agent starts going in circles, do you correct it or throw the session away?

AI 導讀

編碼智能體長時間工作後若停止進展,用戶要判斷應繼續引導,還是結束工作階段並帶着所學摘要重新開始。Claude Code 等終端智能體中,兩種做法都只需幾下按鍵;討論聚焦於判定工作階段無法挽救的訊號,以及重新開始時要帶上摘要、計劃檔案,還是甚麼也不帶。

正文

Rulestack

A long session with a coding agent often reaches a point where it stops making progress. It tries the same fix twice, undoes its own change, or keeps defending an approach you already said was wrong. At that point there are two options. You can keep steering: explain the problem again, point at the right file, narrow the task. Or you can end the session and start a fresh one with a short summary of what you learned.

Steering keeps everything the agent has already read, including the parts it got right. Starting over drops the wrong assumptions along with the useful context, and the agent has to read the code again. In Claude Code and other terminal agents, both are a few keystrokes away, so the choice comes down to judgment, not effort.

We want to know how you make that call:

  • What signal tells you a session is beyond saving?
  • When you start fresh, what do you carry over: a summary, a plan file, nothing?
  • Do you have a rule of thumb, such as a number of failed attempts before you reset?

Share the signal you trust in the comments below, even if it is just a gut feeling.

來源:DEV Community · dev.to