Repository navigation
feat(ui): attach images pasted into the composer - #104
Merged
Merged
Conversation
This was referenced Oct 5, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #91. Pasting an image into a chat composer now attaches it through the same path as drag-and-drop and the file picker (
useAttachments().add). Plain-text, URL-link and multiline paste behave as in canary 0.0.11.RichTexttakes an optionalonFiles. When the clipboard holds files and notext/plain, the editor consumes the paste and passes anyimage/*files toonFiles.ChatComposerpassesonFiles={attachable ? addFiles : undefined}, the gate drop already uses.canAttach={false}and edit mode therefore attach nothing.Files+text/plain+text/html, where the file is a rendered image of the cells. These pastes keep the text. Screenshots, Finder copies and Safari "Copy Image" carry notext/plain, so they attach.<img>into the editor DOM, outside the schema. That paste is now consumed and ignored.Validation
Checks ran in Ace-dev built from this branch: WKWebView shell, a disposable source host, and a real macOS pasteboard.
image.png.a.png.canAttach={false}): a PNG paste and a Finder-style paste inserted nothing and showed no image. Text and mixed pastes still worked.apps/appdoesn't passeditingyet. It uses the sameattachablegate.bun typesandbun run cipass.Known limits:
Built in Ace
Ace agents in Ace channels made all repository edits and ran all builds, checks and GitHub operations for this PR. The review was a separate Ace channel, and
dev-paste-validationowned the Ace-dev and host environment. Codex supervised the work by driving the Ace Canary UI with computer use. That was the dogfooding workflow the user asked for; Codex didn't edit the repository, run builds or checks, or use GitHub for this PR.Gaps that forced workarounds:
osascript(Finder, Numbers, Safari), which raised macOS Automation prompts. Whetherdesktop_keycan copy in Finder is untested; the agent skipped the tool's hint.Other dogfooding issues found along the way: