Cut off chats because too long

Discussion
1

I really enjoy learning to use Cursor, but a couple of things annoys a lot. You are in the middle of a creative process and then the chat/composer chokes because the log is too long.
It’s ok there is a cap on the length but maybe:

  1. Place a usage percentage in the top.
  2. Make it possible to keep our logs locally and ad a save chat/composer log.

A cap-meter make it possible to predict when to prepare for a new instance.
Saving chat log make it possible for the next composer/chat to pick up where we are and what was done - fast. In reality one would maybe only use parts of the chat log but I really like to have the option.

I know I can go to former chats and copy from them, but we deal in automation and AI coorporation so that is a big step back in my opinion.

Keep up the good work Cursor team.

2

Hey, we plan to fix this to make it easier to transfer to a new chat. We also plan to fix the “conversation too long” error, which might already be resolved. Stay tuned for updates.

3

Sounds very good, but I still would like to be able to save my chat to files as a tool for further AI work in other VSC projects.

4

For exporting chat history, you can try this solution suggested by a user:

5

THANKS a whole lot. SpecStory is just what I needed, :woozy_face::+1:

1 Like
6

Glad it’s helpful! Let me know if you have any feedback or questions.