# Taking longer for composer **URL:** \ **Category:** Feedback\ **Created:** [January 2, 2025, 8:24pm UTC](https://forum.cursor.com/t/taking-longer-for-composer/38786 "2025-01-02T20:24:15Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![temp-sunsetmango](https://avatars.discourse-cdn.com/v4/letter/t/e19b73/32.png) [@temp-sunsetmango](https://forum.cursor.com/u/temp-sunsetmango)\ **Post date:** [January 2, 2025, 8:24pm UTC](https://forum.cursor.com/t/taking-longer-for-composer/38786/1 "2025-01-02T20:24:15Z")
It takes way longer than 0.43’s composer, it checks for linter errors, which is useless for xcode, and it generally just has a way smaller vision, like it does things that would make no sense to do if you were looking at the entire file. Please stop auto updating it, and please fix this in 0.45, it’s way less usable. ---
**Author:** ![dank](https://avatars.discourse-cdn.com/v4/letter/d/8dc957/32.png) [@dank](https://forum.cursor.com/u/dank)\ **Post date:** [January 5, 2025, 10:19pm UTC](https://forum.cursor.com/t/taking-longer-for-composer/38786/2 "2025-01-05T22:19:21Z")
Yes I agree, this version is bad, specially for Xcode, It still overwriting and deleting current code. It really needs to stop the auto update, let us decide when to update. ---
**Author:** ![SalaciousCarrot](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/salaciouscarrot/32/13049_2.png) [@SalaciousCarrot](https://forum.cursor.com/u/SalaciousCarrot)\ **Post date:** [January 5, 2025, 10:30pm UTC](https://forum.cursor.com/t/taking-longer-for-composer/38786/3 "2025-01-05T22:30:59Z")
I’ve been having a dickens of a time with 0.44.11 with Xcode swiftui projects. It’s been very unreliable, constant “Generating…” stalls, overzealous code edits, if you don’t watch it like a hawk. Reverted to using 0.44.9 with much better reliability it seems but those two problems are always still there to some degree. ---
**Author:** ![danperks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danperks/32/19087_2.png) [@danperks](https://forum.cursor.com/u/danperks)\ **Post date:** [January 7, 2025, 5:35pm UTC](https://forum.cursor.com/t/taking-longer-for-composer/38786/4 "2025-01-07T17:35:38Z")
The composer and our latest version should be as quick as ever. So it’s interesting to me that you say it’s slower. Regarding the linter errors, you can get linter extensions for Swift, which would mean the linter error step would still be useful as the AI could correct any linting errors before you flip over to Xcode. I’m an Xcode user myself, so I’m interested in improving that experience too! ---
**Author:** ![SalaciousCarrot](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/salaciouscarrot/32/13049_2.png) [@SalaciousCarrot](https://forum.cursor.com/u/SalaciousCarrot)\ **Post date:** [January 7, 2025, 10:22pm UTC](https://forum.cursor.com/t/taking-longer-for-composer/38786/5 "2025-01-07T22:22:17Z")
> [@temp-sunsetmango](#): > > It takes way longer than 0.43’s composer, it checks for linter errors, which is useless for xcode Install Swiftlint from the Extensions browser. You can define the rules in the .swiftlint.yaml. > [@danperks](#): > > The composer and our latest version should be as quick as ever. So it’s interesting to me that you say it’s slower. I have to echo this composer does feel slow and sluggish. Especially when doing @ tagging files, I am typing faster than the file filter can keep up and I end up tagging the wrong file so I’m waiting for the filter to catch up before pressing enter. Not to mention the frequent “Generating..” hangs mentioned in the other topics. 0.44.11 ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [June 18, 2026, 10:23am UTC](https://forum.cursor.com/t/taking-longer-for-composer/38786/6 "2026-06-18T10:23:37Z")
Closed on June 18, 2026, 10:23am UTC