Repository navigation
Image attachment support in chat + pop-out state transfer fix #63
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| ## What's new | ||
|
|
||
| ### Features | ||
|
|
||
| - **Image attachment support in chat**: Users can now paste clipboard images or use the new attachment button in the chat input to include images with their messages. Images are kept inline as base64 data URLs (no persistent file storage on disk) and rendered as inline thumbnails in chat bubbles. The LLM receives images as base64 multi-part content (OpenAI vision API format), enabling vision-capable models to analyse attached images. Supported models: GPT-4o, Claude Sonnet 4.6, Gemini 3.5 Flash, and any OpenAI-compatible vision endpoint. | ||
|
|
||
| ### Fixes | ||
|
|
||
| - **Pop-out window state not transferred**: The `popOut()` IPC call in the preload bridge uses an `invoke()` helper that unwraps `{ data: T }` from every handler return. The chat-popout handlers (`chat:popOut`, `chat:popoutReady`, `chat:popIn`, `chat:requestPopIn`) returned plain objects (`{ ok: true }` / state) directly, so `invoke()` always resolved to `undefined`. The inline chat's pop-out button now awaits a successful `{ ok: true }` response before showing the placeholder — the unwrap mismatch prevented it from ever firing, leaving the main window's chat panel visible alongside the pop-out. All four handlers now return `{ data: ... }` wrapped values matching the `invoke()` contract. | ||
|
|
||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.