# Composer stopped working (Pro)

**URL:** <https://forum.cursor.com/t/composer-stopped-working-pro/7684>\
**Category:** Bug Reports\
**Created:** [August 17, 2024, 7:44am UTC](https://forum.cursor.com/t/composer-stopped-working-pro/7684 "2024-08-17T07:44:07Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![litecode](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/litecode/32/2966_2.png) [@litecode](https://forum.cursor.com/u/litecode)\
**Post date:** [August 17, 2024, 7:51am UTC](https://forum.cursor.com/t/composer-stopped-working-pro/7684/2 "2024-08-17T07:51:15Z")

</div>

Hi @alex235 ,

Just to get some more troubleshooting information, if you:

- Bring up developer tools console via:

`Cursor` \> `Help` \> `Toggle Developer Tools` and then click the `Console` tab

- And then perform the action that is causing the undesired behaviour

Do you see any error messages?

You could also copy/paste additional system info from:

`Cursor` \> `Help` \> `About`

For topic reference, similar behavior has been reported in posts like these:

> [@Composer stops writing files](https://forum.cursor.com/t/composer-stops-writing-files/7009/3):
>
> I observed the same behaviour in this thread: And another user observed similar behaviour here: And another here: A more extreme example of no response being returned is here: My conclusion is that when the chat gets to a certain size or complexity it can’t output responses any more. That made me think that it would be good to display the token size or ‘context window’ of the chat so we could see how large the chat had gotten etc. Hopefully, like most bugs, after a bit of thought…

And there has been some general comments about the nature of Composer as beta functionality and that some undesired behaviour occurs occasionally and is rectified in subsequent releases etc:

> [@Composer stops writing files](https://forum.cursor.com/t/composer-stops-writing-files/7009/6):
>
> composer is an alpha feature and we are quickly iterating and fixing bugs. we really really appreciate the bugs found and we will fix as many of the bugs as quickly as possible in ti.

Again, just for reference, if any actual crashes occur, you can follow the steps here to provide a crash report:

> [@Why Is Cursor Crashing?](https://forum.cursor.com/t/why-is-cursor-crashing/7334/2):
>
> Please copy details “About Cursor” Run cmd+shift+p \> Developer \> Open Logs Folder. Go to the parent of the folder shown and zip it. If reproduce-able, please take a screen recording of the steps taken before the crash. Please send all of these alongside a description of the crash to [hi@cursor.com](mailto:hi@cursor.com) with the subject “CRASH REPORT”.

---

_[View the full topic](https://forum.cursor.com/t/composer-stopped-working-pro/7684)._