Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

And what should I do about it?? #1577

Closed
Habartru opened this issue Nov 5, 2024 · 4 comments
Closed

And what should I do about it?? #1577

Habartru opened this issue Nov 5, 2024 · 4 comments

Comments

@Habartru
Copy link

Habartru commented Nov 5, 2024

Describe the bug

I have been creating a project for a long time and spent tens of millions of tokens on it. Now, when I try to write anything, I get an error about a long prompt (prompt is too long: 200072 tokens > 200000 maximum) and I can't work on my project. I did not find a solution. The creators of BOLT, maybe it's time to think about it? Do you think I should forget that I spent 5 days and $120 on this project, and now I don't have access to edit it, is that okay in your opinion? Can someone answer specifically without sending to some other branches where there are no answers either ?

Link to the Bolt URL that caused the error

https://bolt.new/~/sb1-pesz3g

Steps to reproduce

the chat is blocked for any message.

Expected behavior

the normal operation of the chat and the project

Screen Recording / Screenshot

No response

Platform

Browser name = Chrome
Full version = 132.0.0.0
Major version = 132
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 49722508,
  "usedJSHeapSize": 46700876,
  "jsHeapSizeLimit": 4294705152
}
Username = Habartru
Chat ID = 49fde7ce9c09

Additional context

No response

@heliusmaximus08
Copy link

i have the same problem?! this is really sad

@smartguyio
Copy link

Same

@yasinkocak
Copy link

#1322

@kc0tlh
Copy link
Collaborator

kc0tlh commented Nov 7, 2024

As @yasinkocak mentions, this issue, and the workarounds are being tracked in #1322. Please head over there @smartguyio @heliusmaximus08 🙏🏻

@kc0tlh kc0tlh closed this as completed Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants