Trae stuck Thinking: check for a crash before restarting

There is no verified general fix for Trae stuck on Thinking in the sources checked on October 9, 2026. Preserve unsaved work and local changes first, then distinguish a stalled chat from an agent crash. The reports below describe different Windows and macOS failures; neither proves that waiting, restarting or clearing a cache repairs every case.

Updated and sources checked: October 9, 2026.

Windows: look for the reported agent crash

An April 11, 2025 user report describes Thinking after scanning code, with ai-agent.exe crashing in Windows Event Viewer. It names Trae 1.2.7, VS Code 1.98.2 and Windows build 10.0.26100. The reported exception is 0xc0000409 (STATUS_STACK_BUFFER_OVERRUN). See Trae Thinking and agent-crash report 858.

The faulting application path in that report ends in resources\app\modules\ai-agent\ai-agent.exe. That is a reported executable location, not a current installation requirement or a file to delete. Record the actual exception and time if the local failure matches. A Thinking label alone does not establish this crash.

ai-agent.exe
0xc0000409 (STATUS_STACK_BUFFER_OVERRUN)

macOS: a persistent Analyzing report is separate

A June 17, 2025 macOS user report describes new and existing chats staying on Analyzing for hours. Restarting Trae, rebooting the Mac, and signing out and back in did not resolve that reported case. See Trae persistent Analyzing report 1118.

This does not demonstrate the Windows crash above or a shared root cause. The report being closed is not proof of a released fix. The reviewed reports provide no verified clear-cache command or directory-removal procedure for this symptom.

Preserve work before a diagnostic restart

Save open files if the editor still responds. Preserve the local diff and note which changes are already on disk. Copy the visible status, last completed action and any actual error before closing the application. These are preservation steps, not a vendor-documented fix.

Record whether only chat is stuck or the whole editor is unresponsive. For a reproducible test after saving work, use the same small request and note whether a fresh chat fails too. Avoid deleting application data or reinstalling as an assumed repair: no such fix was verified in the reviewed sources.

If the editor cannot save, do not treat a forced restart as lossless. Keep any recoverable file copies and describe the unsaved-work uncertainty in the report.

Use the current official feedback channel

The official repository notice says GitHub feedback handling is paused and directs questions, bug reports and suggestions to forum.trae.cn. Keep the historical GitHub reports as symptom references; send a new report through that named community channel. See Trae official feedback-channel notice.

Include the installed version, operating system, Thinking or Analyzing text, reproduction steps, last completed action, and a matching crash entry if present. Remove secrets and private source content. Say which attempted actions failed, rather than presenting them as proven remedies.

How ShardStitch helps

ShardStitch keeps task state and failed attempts available for resuming work with another tool. It cannot restart Trae, recover unsaved editor buffers or repair its agent process. ShardStitch pricing.