claude-code - 💡(How to fix) Fix [Bug] UI mode indicator desynchronizes with agent mode after ExitPlanMode approval [1 comments, 2 participants]

[{"error":"AxiosError: Request failed with status code 404\n at zd (/$bunfs/root/src/entrypoints/cli.js:110:1194)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:115:12712)\n at emit (node:events:92:22)\n at endReadableNT (internal:streams/readable:865:50)\n at processTicksAndRejections (native:7:39)\n at request (/$bunfs/root/src/entrypoints/cli.js:117:2467)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-21T18:31:10.618Z"}]

TL;DR

The issue can be mitigated by documenting the expected behavior of the UI indicator after ExitPlanMode approval and potentially exposing a programmatic mode-query mechanism.

Guidance

• Review the permission-modes documentation to clarify whether ExitPlanMode approval should automatically clear the UI indicator or if a separate Shift+Tab is required.
• Consider implementing a programmatic mode-query mechanism to allow the agent to verify the current session mode, reducing reliance on the reminder stream.
• Investigate the AxiosError and its relation to the mode switching issue, as it may indicate a separate problem.
• Verify that the issue is not specific to the darwin platform or iTerm.app terminal by testing on other environments.

Example

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

Notes

The provided error message appears to be unrelated to the primary issue, but it should still be investigated to ensure it does not contribute to the problem. The solution may require changes to the documentation, the programmatic mode-query mechanism, or both.

Recommendation

Apply workaround: Document the expected behavior of the UI indicator after ExitPlanMode approval and consider exposing a programmatic mode-query mechanism to mitigate the silent divergence between the agent's system reminders and the user-facing UI indicator.