Completed
Credits Information Leak
When you view the public project you can view all the user information like the credits he has used and the credits remaining
Isamaza Sylvain 18 days ago
Bug Hunting
Completed
Credits Information Leak
When you view the public project you can view all the user information like the credits he has used and the credits remaining
Isamaza Sylvain 18 days ago
Bug Hunting
Chat Scroll Bug π¬ππ
The scroll position in the chat resets to the very beginning of the project requiring the user to scroll all the way down to the most current part of the legendary conversation with the lovable agent. This only happens sometimes after an update / reloading the page in chrome. I have not tested in safari or other browsers. It is a rather cursed and frustrating bug making the experience less⦠lovable.
Rei Trace 21 days ago
Bug Hunting
Chat Scroll Bug π¬ππ
The scroll position in the chat resets to the very beginning of the project requiring the user to scroll all the way down to the most current part of the legendary conversation with the lovable agent. This only happens sometimes after an update / reloading the page in chrome. I have not tested in safari or other browsers. It is a rather cursed and frustrating bug making the experience less⦠lovable.
Rei Trace 21 days ago
Bug Hunting
Completed
Try to Fix Button Using Credits Despite Docs
According to the docs: βMessages triggered by βAsk the AI to fixβ donβt count toward your usage limits only if pressed on the button. If you are trying to fix errors with an additional prompt, that counts as message credit.β However, as of late it is using credits. Please advise and restore if possible.
User 22 days ago
Bug Hunting
Completed
Try to Fix Button Using Credits Despite Docs
According to the docs: βMessages triggered by βAsk the AI to fixβ donβt count toward your usage limits only if pressed on the button. If you are trying to fix errors with an additional prompt, that counts as message credit.β However, as of late it is using credits. Please advise and restore if possible.
User 22 days ago
Bug Hunting
Wordpress Backend integration front-end loveble ai
i need to create full application that will be backend WordPress, front-end will be react lovable we donβt want to supabase database
Rayhan Chowdury 24 days ago
Integrations
Wordpress Backend integration front-end loveble ai
i need to create full application that will be backend WordPress, front-end will be react lovable we donβt want to supabase database
Rayhan Chowdury 24 days ago
Integrations
Appwrite Integration
Hi lovable team, I would like to suggest the integration of appwrite as alternative to supabase. Thanks in advance, Regards,
Francisco Santos Belmonte 25 days ago
Integrations
Appwrite Integration
Hi lovable team, I would like to suggest the integration of appwrite as alternative to supabase. Thanks in advance, Regards,
Francisco Santos Belmonte 25 days ago
Integrations
Token Limits and Processing Capacity Per Account
Hello I used Lovable for free for a few days and was really happy that your system handled my large requests. I sometimes sent in 100 lines of text, and neural network processed over 60 of them. I can imagine how many tokens were burned, and yet there were hardly any bugs. Much respect and gratitude to you for that. But today, in every request of 100 lines, only about 5β10 lines get processed at best. Can you explain β is this reduction related to account status? Do new accounts get some kind of welcome token bonus? Or is this a platform-wide change affecting all users? How many lines of text are processed with a paid plan? What are Lovable's plans for the future? Does Lovable have the economic sustainability to keep handling large requests β does the token spending model work out? Is there a reason to expect more power and greater processing capacity per request in the future, or will the platform focus more on optimization instead?
User 25 days ago
Questions
Token Limits and Processing Capacity Per Account
Hello I used Lovable for free for a few days and was really happy that your system handled my large requests. I sometimes sent in 100 lines of text, and neural network processed over 60 of them. I can imagine how many tokens were burned, and yet there were hardly any bugs. Much respect and gratitude to you for that. But today, in every request of 100 lines, only about 5β10 lines get processed at best. Can you explain β is this reduction related to account status? Do new accounts get some kind of welcome token bonus? Or is this a platform-wide change affecting all users? How many lines of text are processed with a paid plan? What are Lovable's plans for the future? Does Lovable have the economic sustainability to keep handling large requests β does the token spending model work out? Is there a reason to expect more power and greater processing capacity per request in the future, or will the platform focus more on optimization instead?
User 25 days ago
Questions
Inability to Build a Real Project
Youβve created a tool that only generates a template with some text, and none of the code actually works. It just looks decent but doesnβt deliver a functional tool. And once the project gets a bit larger, it becomes clear that you have no idea what youβre doing anymore.
mohammad kia 26 days ago
Lovable Project
Inability to Build a Real Project
Youβve created a tool that only generates a template with some text, and none of the code actually works. It just looks decent but doesnβt deliver a functional tool. And once the project gets a bit larger, it becomes clear that you have no idea what youβre doing anymore.
mohammad kia 26 days ago
Lovable Project
Cant revert to previous version of my project
Hi, team. I am having trouble reverting to a previous version. It doesnβt revert and gives that: External Commit Reverted to edit edt-9b814055-cb1a-4208-8b81-62d2b49c0360: "Fix: AgentScriptSection type errors Fixes type errors in AgentScriptSection.tsx related to the 'first_message' property. Replaced 'first_message' with 'firstMessage' to match the VapiAgent type definition." Is it a bug or a temporary problem?
Kaan Senol 27 days ago
Bug Hunting
Cant revert to previous version of my project
Hi, team. I am having trouble reverting to a previous version. It doesnβt revert and gives that: External Commit Reverted to edit edt-9b814055-cb1a-4208-8b81-62d2b49c0360: "Fix: AgentScriptSection type errors Fixes type errors in AgentScriptSection.tsx related to the 'first_message' property. Replaced 'first_message' with 'firstMessage' to match the VapiAgent type definition." Is it a bug or a temporary problem?
Kaan Senol 27 days ago
Bug Hunting
Give feedback when something isn't possible in the environment
I was trying to create a UPNP/DLNA audio player, and Lovable was able to identify my devices, but kept finding ways not display the content from the server, instead finding multiple ways to create mock content while claiming it was working on it. Until I finally asked why it was avoiding doing the work. It added to my library page: βNo content found on UPNP servers. A backend service is required for actual UPNP communication. UPNP/DLNA protocol requires direct network access which browsers cannot do for security reasons. A real implementation would need: A backend service that can use SSDP for device discovery SOAP communication for content browsing DLNA protocol implementation for streaming This could be implemented as a Node.js server, Electron app, or browser extension with appropriate permissions.β OK, this is logical. But I wouldnβt have spent nearly so long chasing my tail, if it had told me this up front.
Jason Perez 28 days ago
Bug Hunting
Give feedback when something isn't possible in the environment
I was trying to create a UPNP/DLNA audio player, and Lovable was able to identify my devices, but kept finding ways not display the content from the server, instead finding multiple ways to create mock content while claiming it was working on it. Until I finally asked why it was avoiding doing the work. It added to my library page: βNo content found on UPNP servers. A backend service is required for actual UPNP communication. UPNP/DLNA protocol requires direct network access which browsers cannot do for security reasons. A real implementation would need: A backend service that can use SSDP for device discovery SOAP communication for content browsing DLNA protocol implementation for streaming This could be implemented as a Node.js server, Electron app, or browser extension with appropriate permissions.β OK, this is logical. But I wouldnβt have spent nearly so long chasing my tail, if it had told me this up front.
Jason Perez 28 days ago
Bug Hunting
How to build custom (verified) integration?
I offer a service where users can finetune custom LLMs through conversation (just telling how they want it to act, and really updating the weights behind the scenes!). I want to seamlessly integrate this into lovable; I am willing to do all the legwork, but want to understand what steps I would need to follow to accomplish this and make it super easy for users of Lovable. The API works basically the same as the standard OpenAI-style inference API, with special endpoints for model creation and teaching.
Cameron Witkowski 28 days ago
Integrations
How to build custom (verified) integration?
I offer a service where users can finetune custom LLMs through conversation (just telling how they want it to act, and really updating the weights behind the scenes!). I want to seamlessly integrate this into lovable; I am willing to do all the legwork, but want to understand what steps I would need to follow to accomplish this and make it super easy for users of Lovable. The API works basically the same as the standard OpenAI-style inference API, with special endpoints for model creation and teaching.
Cameron Witkowski 28 days ago
Integrations
Stuck with a project
I have project that is almost done but suddenly Im getting βAn internal error occurredβ and not able to update or to run project anymore, no more errors so I cant debug properly.
Branislav BrujiΔ 28 days ago
Bug Hunting
Stuck with a project
I have project that is almost done but suddenly Im getting βAn internal error occurredβ and not able to update or to run project anymore, no more errors so I cant debug properly.
Branislav BrujiΔ 28 days ago
Bug Hunting
Should: Automatic Cache Clearing for Version Control Operations
Problem Statement Currently, when switching branches in Git or reverting to previous versions in Lovable, the TypeScript and build caches are not automatically cleared. This leads to: Stale type definitions causing false TypeScript errors Build artifacts from different versions conflicting Developer time wasted manually clearing caches Confusing error messages that don't match the current codebase Examples of Issues TypeScript errors about missing properties (e.g., 'is_overflow') that should exist Build cache conflicts between different versions of the same component Persistent type errors even after reverting to known-working versions Proposed Solution Implement automatic cache clearing triggers for: Git branch switching operations Version revert operations in Lovable Code restoration from previous edits Technical Implementation Details The system should: Clear the TypeScript compilation cache Remove build artifacts Clear Vite's build cache Regenerate type definitions Trigger a fresh build Key Folders/Files to Clear .tsbuildinfo files node_modules/.vite node_modules/.cache Temporary build directories Success Criteria No TypeScript errors when switching branches Clean builds after version changes Automatic type regeneration No manual cache clearing needed Additional Benefits Improved developer experience Reduced debugging time More reliable builds Consistent type checking Priority Blocking - This is blocking my development Related Issues TypeScript errors when switching branches Build inconsistencies after version changes Manual cache clearing requirements
AndrΓ© Brunetta 28 days ago
Bug Hunting
Should: Automatic Cache Clearing for Version Control Operations
Problem Statement Currently, when switching branches in Git or reverting to previous versions in Lovable, the TypeScript and build caches are not automatically cleared. This leads to: Stale type definitions causing false TypeScript errors Build artifacts from different versions conflicting Developer time wasted manually clearing caches Confusing error messages that don't match the current codebase Examples of Issues TypeScript errors about missing properties (e.g., 'is_overflow') that should exist Build cache conflicts between different versions of the same component Persistent type errors even after reverting to known-working versions Proposed Solution Implement automatic cache clearing triggers for: Git branch switching operations Version revert operations in Lovable Code restoration from previous edits Technical Implementation Details The system should: Clear the TypeScript compilation cache Remove build artifacts Clear Vite's build cache Regenerate type definitions Trigger a fresh build Key Folders/Files to Clear .tsbuildinfo files node_modules/.vite node_modules/.cache Temporary build directories Success Criteria No TypeScript errors when switching branches Clean builds after version changes Automatic type regeneration No manual cache clearing needed Additional Benefits Improved developer experience Reduced debugging time More reliable builds Consistent type checking Priority Blocking - This is blocking my development Related Issues TypeScript errors when switching branches Build inconsistencies after version changes Manual cache clearing requirements
AndrΓ© Brunetta 28 days ago
Bug Hunting
Sitemap Problems
Everyone is building products, but none of them can be appropriately indexed. You have unnecessary spacing on the XML sitemap, which means they canβt be read. The error occurs again every time I make a new deployment. Iβm trying to create complex here-flang websites with custom localised content. Iβm using ALL my credits to fix this error. Thank you.
Alex Lawford 29 days ago
Bug Hunting
Sitemap Problems
Everyone is building products, but none of them can be appropriately indexed. You have unnecessary spacing on the XML sitemap, which means they canβt be read. The error occurs again every time I make a new deployment. Iβm trying to create complex here-flang websites with custom localised content. Iβm using ALL my credits to fix this error. Thank you.
Alex Lawford 29 days ago
Bug Hunting
Xero Integration
Hi Team, Could you please provide instructions on how to integrate Xero on Lovable? Thank you Eleanor
Eleanor Fullarton 30 days ago
Integrations
Xero Integration
Hi Team, Could you please provide instructions on how to integrate Xero on Lovable? Thank you Eleanor
Eleanor Fullarton 30 days ago
Integrations