You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Periodic Claude provider refresh accumulates orphaned tasklist.exe/findstr.exe processes on Windows #8575
Repeat the scheduled or manual refresh for two or three capability-probe cycles. For manual refreshes, wait until the capability cache expires, approximately five minutes, before triggering the next check.
Compare the process snapshots and count the tasklist.exe and findstr.exe processes that remain after each refresh.
Expected behavior
Each provider refresh should clean up the complete Claude capability-probe process tree. The tasklist.exe and findstr.exe processes started by Claude's IDE detection should exit when the probe completes, times out, or is aborted. Their number should return to the previous baseline after every refresh.
Actual behavior
The periodic Claude provider refresh starts a capability probe. During the probe, Claude's IDE detection runs a command similar to tasklist | findstr /I "Code.exe Cursor.exe ...". After the refresh finishes or the probe is aborted, tasklist.exe and findstr.exe processes can remain alive. Subsequent refreshes may leave additional instances behind, causing leftover processes to accumulate over time. This is a persistent process-lifecycle problem, not just a transient console-window flash.
Impact
Major degradation or frequent failure
Version or commit
0.0.35
Environment
No response
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
In T3 Code, open Settings → Providers, expand the Claude provider instance, and add the following under Environment variables:
I found another related symptom while investigating this issue. On Windows, starting or refreshing the Claude provider can also launch git ... remote or git ... remote get-url origin. When the capability probe exits, these processes may be left behind as suspended orphan git.exe processes.
The recommended fix is to make the capability probe reliably terminate and reap its entire child-process tree, including Git processes, on completion, timeout, or cancellation.
Activity
HMBSbige commentedon Aug 29, 2026
I found another related symptom while investigating this issue. On Windows, starting or refreshing the Claude provider can also launch
git ... remoteorgit ... remote get-url origin. When the capability probe exits, these processes may be left behind as suspended orphangit.exeprocesses.The recommended fix is to make the capability probe reliably terminate and reap its entire child-process tree, including Git processes, on completion, timeout, or cancellation.
Squashed '.repos/effect-smol/' changes from a43c7e244c..e17ecdbe90