vibesdk icon indicating copy to clipboard operation
vibesdk copied to clipboard

Only first image upload works

Open harryworkbiz opened this issue 5 months ago • 12 comments

Uploading an image with the first chat message works fine, but images uploaded afterward don’t load. The AI either doesn’t detect the image at all, or the entire message containing the image disappears, as shown in the video below.

https://github.com/user-attachments/assets/4c81fb31-6122-4278-a843-f4f99e6c07d9

harryworkbiz avatar Oct 09 '25 18:10 harryworkbiz

Thank you for bringing this up. Images are indeed visible to the chat agent and phase planning/implementation agents for when you upload them, but they aren't stored in the platform itself currently, and hence they might not show up in the chat. But if the chat itself is disappearing (i.e the text), then thats a legitimate bug. Please share your chat id and if its happening too often. This is something I would be finishing up on in the coming week.

AshishKumar4 avatar Oct 09 '25 19:10 AshishKumar4

Yeah this looks like a bug. In the video you can see that when I upload an image and press enter, the text message disappears. I’ll try to reproduce it in another project and let you know if it happens again.

harryworkbiz avatar Oct 09 '25 21:10 harryworkbiz

Hello, I have added support for persisting user messages (although they still won't be visible in the chat) https://github.com/cloudflare/vibesdk/pull/157 can you try again?

AshishKumar4 avatar Oct 12 '25 16:10 AshishKumar4

Just tested it and it’s working now. I can upload multiple images after the first message without any issues.

harryworkbiz avatar Oct 12 '25 20:10 harryworkbiz

Are there any issues/bugs you are facing right now? And how are things going now? I am starting to work on prompt improvements, template improvements and code fixing agent after that. Let me know of any and all feedbacks that I can incorporate in these.

AshishKumar4 avatar Oct 13 '25 07:10 AshishKumar4

I’ll keep you updated on any other issues. There’s one recurring frustration I’ve run into a few times though.

When I start a new chat or continue a project, the agent begins working, but if I hit the daily message limit halfway through, it stops coding mid-process. That’s fine in general, but it leaves the app in a broken state, and a few times I haven’t been able to preview or recover it once the limit resets. It should ideally finish the current code operation before stopping, then apply the limit afterward.

For example, I created a new project, it started the blueprint, went through a few phases, then stopped mid-build. After the limit reset the next day, it couldn’t fix the preview issues or resolve the error since it never completed the first build.

Bolt.new had a similar issue before, and they fixed it by letting the code finish writing before stopping.

harryworkbiz avatar Oct 13 '25 07:10 harryworkbiz

Also in terms of agent feedback, it tends to over-explain and repeat itself instead of giving focused, productive responses.

For example, it often starts with long apologies or statements like “You are absolutely right, I sincerely apologize” and then continues with “I deeply regret…” followed by several paragraphs that don’t add much to the actual solution.

It would be better if the agent:

  • Got straight to the point and focused on solving the problem
  • Avoided unnecessary praise, apologies or repetition
  • Kept responses short, clear and action-oriented

This would make the workflow much faster and reduce noise in longer threads since its responses are often quite long-winded.

harryworkbiz avatar Oct 13 '25 08:10 harryworkbiz

Thank you for these feedbacks. I increased the rate limit to 4x the value around 6-7 hours ago. I am still tuning it to limit platform abuse. Let me know if your experience is better now. Also working on getting byok supported. About it stopping mid coding - rate limits apply on a fresh LLM call, so it should only stop after either a phase generation or a phase implementation or a chat message, and if a phase was being implemented, it should finish completely. An app generation can take lots of phases so having the rate limit after it might cost too much, but let me see.

About the chat - I did make several prompt changes, so it should have helped, particularly on new apps/fresh chats. On Existing apps, the chat agent might keep generating same kind of results as it has in it's history already. Is the experience better or the same/worse on new chats for you? By new I mean since the last 1-2 days.

AshishKumar4 avatar Oct 13 '25 14:10 AshishKumar4

Yes, just been testing and the new agent in the chat is much better. It's much more compact and less verbose.

harryworkbiz avatar Oct 13 '25 17:10 harryworkbiz

Thank you! Closing the issue as the original problem seems to have been resolved

AshishKumar4 avatar Oct 16 '25 23:10 AshishKumar4

This image issue has come back again. I can’t upload any images after the first one.

When I upload an image and send it, that chat disappears. See the video below. It automatically scrolls the page as well.

Image

harryworkbiz avatar Oct 21 '25 14:10 harryworkbiz

This seems like a new bug. Let me reopen the issue and try address it by this weekend's release

AshishKumar4 avatar Oct 21 '25 16:10 AshishKumar4