V1.41 ,roo code extension does not work properly

Describe the Bug

The glm-4.5-air model is used in the roo code extension, which is normal in version 1.39. But now the cursor will automatically upgrade to version 1.41, roo code can make a request, but always show the request, can not see the response.

Steps to Reproduce

v1.39:
[subtasks] parent task f4738d85-be4c-4730-ab44-898435825316.419f8644 instantiated
[Task#getCheckpointService] initializing shadow git
[t#create] git = 2.45.2
[t#initShadowGit] creating shadow git repo at c:\Users\xxx\AppData\Roaming\Cursor\User\globalStorage\rooveterinaryinc.roo-cline\tasks\f4738d85-be4c-4730-ab44-898435825316\checkpoints
[t#initShadowGit] initialized shadow repo with base commit d3ae5b7b53016548d4b91e8e3d873c16b9d99b4e in 959ms
[Task#getCheckpointService] service initialized

v1.41:
[subtasks] parent task 24fe7f5a-6a96-405b-a228-d86d3fc68478.9ded5b94 instantiated
[Task#getCheckpointService] initializing shadow git
[t#hasNestedGitRepositories] failed to check for nested git repos: ripgrep not found: undefined
[t#create] git = 2.45.2
[t#initShadowGit] creating shadow git repo at c:\Users\xxx\AppData\Roaming\Cursor\User\globalStorage\rooveterinaryinc.roo-cline\tasks\24fe7f5a-6a96-405b-a228-d86d3fc68478\checkpoints
[t#initShadowGit] initialized shadow repo with base commit baec463011d1d157b024d0004f0989ddee8adeee in 953ms
[Task#getCheckpointService] service initialized

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

1.3.9 (user setup)
1.99.3
54c27320fab08c9f5dd5873f07fca101f7a3e070
Electron: 2025-08-01T20:19:30.453Z
ElectronBuildId: 34.5.1
Chromium: undefined
Node.js: 132.0.6834.210
V8: 20.19.0
OS: 13.2.152.41-electron.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Todo-Tree extension, which also reports errors

Todo-Tree: Failed to find vscode-ripgrep - please install ripgrep manually and set ‘todo-tree.ripgrep’ to point to the executable

Is the cursor editor no longer built in ripgrep in version 1.41?

2 Likes

Hey, we are looking into this. It seems like v1.4 used a new version of “ripgrep”, which may have not been bundled in a way that exposed it to extensions correctly.

The team are aware and should be fixed in the v1.4.2 hotfix!

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.