You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update on image uploading - need your input on UX trade-off:
The challenge with adding image support stems from our encryption architecture. Here's how it works and why we need your feedback:
Current Architecture:
The mobile app and CLI don't need to be online simultaneously (this is a feature)
Mobile app uploads encrypted instructions to our relay server (acts as a mailbox)
CLI downloads and processes these encrypted instructions when it comes online
To let you upload an image, it would be encrypted on your phone, sent to the relay server, then downloaded by the CLI
The Design Problem:
When you upload an image and close the app, what happens when you come back to that conversation?
Option 1: Store images on relay server
✅ You can see uploaded images when revisiting old chats
❌ Significant disk usage on the free demo relay server operated by volunteers (costly)
Option 2: Temporary local storage only
✅ Easy to implement - images saved to temp folder on your CLI computer
✅ Minimal server storage needed
❌ You won't see previously uploaded images when revisiting old chats
❌ Only see a message like "Image uploaded: photo.jpg"
Question for you: Would you be OK with Option 2? Essentially, images would work for active conversations but wouldn't persist in chat history when you return later. The CLI would still receive and save them locally, but the mobile app wouldn't re-display them in old conversations.
This would let us ship image support quickly if the UX trade-off is acceptable. Please let me know!
What about in Option 2: Temporary local storage only, when it shows "Image uploaded: photo.jpg" the user is able to click on it (similar to how we currently click on file edits, or command outputs) and when clicked the cli would send it back to the mobile app through the server, in the same fashion we currently handling the files and diffs? image locations can be customizable in the cli settings instead of just being in tmp. wdyt @GrocerPublishAgent ?
making the image destination configurable is good idea.
I was only thinking of the case where images are being uploaded via the mobile app -> across the internet -> down into your computer. But you are right, images can be pasted in and @mentioned into the terminal. I'll need to quickly check if those pasted images get. saved somewhere.
I can make the mobile app load the image from your computer if the image is still there.
Option 2 sounds totally fine to me.
In my workflow, I don’t use the mobile app much—I mostly run the CLI on a remote server. When I’m coding, I’d really value being able to upload images directly instead of having to use SCP or some other manual transfer method. Being able to just paste an image into the web app would be a killer feature for me, even if the images don’t persist in old chats.
Activity
GrocerPublishAgent commentedon Sep 3, 2025
Update on image uploading - need your input on UX trade-off:
The challenge with adding image support stems from our encryption architecture. Here's how it works and why we need your feedback:
Current Architecture:
To let you upload an image, it would be encrypted on your phone, sent to the relay server, then downloaded by the CLI
The Design Problem:
When you upload an image and close the app, what happens when you come back to that conversation?
Option 1: Store images on relay server
Option 2: Temporary local storage only
Question for you: Would you be OK with Option 2? Essentially, images would work for active conversations but wouldn't persist in chat history when you return later. The CLI would still receive and save them locally, but the mobile app wouldn't re-display them in old conversations.
This would let us ship image support quickly if the UX trade-off is acceptable. Please let me know!
shekohex commentedon Sep 5, 2025
What about in Option 2: Temporary local storage only, when it shows
"Image uploaded: photo.jpg"the user is able to click on it (similar to how we currently click on file edits, or command outputs) and when clicked the cli would send it back to the mobile app through the server, in the same fashion we currently handling the files and diffs? image locations can be customizable in the cli settings instead of just being in tmp. wdyt @GrocerPublishAgent ?GrocerPublishAgent commentedon Sep 6, 2025
making the image destination configurable is good idea.
I was only thinking of the case where images are being uploaded via the mobile app -> across the internet -> down into your computer. But you are right, images can be pasted in and @mentioned into the terminal. I'll need to quickly check if those pasted images get. saved somewhere.
I can make the mobile app load the image from your computer if the image is still there.
zhigang1992 commentedon Sep 12, 2025
Option 2 sounds totally fine to me.
In my workflow, I don’t use the mobile app much—I mostly run the CLI on a remote server. When I’m coding, I’d really value being able to upload images directly instead of having to use SCP or some other manual transfer method. Being able to just paste an image into the web app would be a killer feature for me, even if the images don’t persist in old chats.
vlebourl commentedon Jan 8, 2026
Option 2 looks good to me. Claude-code itself is not showing the image itself, just
[ image #1 ]. I suppose option 2 would be similar to that.camsong commentedon Feb 4, 2026
Option 2 is quite good enough, wanna to confirm is there any progress on this feature. really need this.
5iveMEDIA commentedon Feb 14, 2026
Could they get pushed to the users repository at git and just pass a link to Happy?
jbriales commentedon Feb 28, 2026
What's the estimated complexity for Option 2? Is there any WIP branch that I could try?
feat: right sidebar for tool detail viewing (3-panel layout)