Composer stuck at Applying... + @codebase issue

At first I had the issue where it was stuck at “Generating…” but then I started a new Composer which seemed to work. However, when I went forward asking to make changes to my code it now seems to be forever stuck on “Applying…”

Also, when I started a new Composer window I was unable to give it @codebase to let it see my entire project. What gives??

Version: 0.43.1
VSCode Version: 1.93.1
Commit: 5ea53fca4187f123b8adc8f4cea37382b97b6880
Date: 2024-11-24T08:57:46.282Z (6 hrs ago)
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.1.0

hey! we’ve removed the @codebase from composer for now in favor of the composer agent. are there any specific use cases for @codebase that you want to use?

I am yet to test the new implementation .Is it more robust in terms of context awareness vs using the @composer.Having docs about these new features would be helpful for devs. Thanks

Ah got it so if I switch to agent I don’t need to give it access to the entire codebase? Also any reason why it’s stuck in “Applying…”?

We want codebase back, especially long context. Agents suck for >10k LOCs projects. Even, when you try to refactor a 600-800 loc file, it’s utterly useless.

1 Like

note taken! will definitely improve that over the coming weeks

we’re also rolling out 0.43 with composer agent that will include relevant context automatically

@codebase will be reenabled before we fully rollout!

1 Like

I’m still unable to use cursor. When I input a request Composer generates but is forever Applying…

Please help!

Could you run "cmd+shift+p > report ai action > click on the bad action > report with comment - then make the comment “aman said to report on the forum”

Make sure privacy mode is disabled when you report.

just sent it in

Any update here?

I’m still getting these errors after 3 days

I then went to click on the file and got this pop-up.