-
Notifications
You must be signed in to change notification settings - Fork 8.6k
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
Better LLM Context for packages and imports #28
Comments
Hey @CodeFromAnywhere ! 👋 Do you mean to show something like which |
no, that's not what I mean. I mean that your ai hallucinates on the contents of packages. it does not use any context of the actual stuff inside of packages. for bigger packages it's totally fine, but what about smaller ones that aren't represented well in your dataset of the model, or packages owned by the user? you need this additional context to have an ai chatbot that does not hallucinate. im creating an api for having this context |
I think there's a misunderstanding. Packages are fetched from the npm registry the same way they're fetched on https://stackblitz.com. They are not generated by bolt. |
Oh thank you so much for the clarification! So sorry, I totally understand what you mean. I think we could definitely improve on that area to help the AI model so that it generates only known versions. For imports it's a bit more tricky but there's a plenty of ideas we want to experiment. I'll add this to our internal tracker and we'll keep you posted. |
Update README.md
Is your feature request related to a problem? Please describe:
Congrats on the launch! Very cool stuff, but one immediate limitation I noticed is you don't have realtime info about packages. like what's inside them...
Describe the solution you'd like:
I'd like the llm to use a tool so it can reason over realtime contents of the package
Describe alternatives you've considered:
The alternative is to just use large packages that it knows, but that's quite a limitation!
Additional context:
I'm building http://swcapi.com and http://npmjz.com let me know if you need help with that!
The text was updated successfully, but these errors were encountered: