claude-code - 💡(How to fix) Fix [Bug] Plan mode state changes don't emit system reminders, causing agent desynchronization [1 comments, 2 participants]

[{"error":"Error: Request was aborted.\n at makeRequest (/$bunfs/root/src/entrypoints/cli.js:50:3448)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-28T06:32:50.328Z"}]

TL;DR

The agent's failure to receive a "Plan mode is active" system reminder after the user toggles plan mode back on may be due to a desynchronization issue, and a potential fix could involve ensuring that the agent receives an explicit reminder after every plan mode toggle.

Guidance

• Investigate the ExitPlanMode call and the system reminder firing mechanism to ensure that they are correctly handling the plan mode toggle events.
• Verify that the agent's mental model is being updated correctly after each plan mode toggle, and that it is not relying on a cached or outdated state.
• Check the error message "Request was aborted" to see if it is related to the desynchronization issue, and if it can provide any clues about the root cause of the problem.
• Consider adding additional logging or debugging statements to track the agent's state and the system reminders to better understand the issue.

Example

No code snippet is provided as the issue does not contain enough information to create a specific example.

Notes

The issue seems to be related to a desynchronization between the agent's mental model and the actual plan mode state, but the root cause is not entirely clear. Further investigation is needed to determine the exact cause of the problem.

Recommendation

Apply workaround: Implement a mechanism to ensure that the agent receives an explicit "Plan mode is active" system reminder after every plan mode toggle, to prevent the agent from acting as if it is in auto mode when it is actually in plan mode. This can help mitigate the issue until the root cause is identified and fixed.