Repository navigation
Send images to InvokeAI's image or video generation tab - #424
Merged
Merged
Conversation
The drawer's Send / Append Image row gains "as a reference for
<image generation | video generation>". With video chosen, the image is
uploaded and placed through InvokeAI's new
/api/v1/recall/video/{queue_id}/image route. The Video panel's model
decides where it lands: reference images for Ref2VA, first/last frame
for frame models. The pulldown only appears when the backend's OpenAPI
schema has that route (video_image capability). The choice is a
server-backed per-device preference (invokeRefTarget).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
The metadata drawer's InvokeAI section now lets you choose which InvokeAI tab Send Image and Append Image feed:
POST /api/v1/recall/video/{queue_id}/imageroute (feat(video): place a gallery image in the Video panel from the recall API invoke-ai/InvokeAI#9693). The Video panel's model decides where it lands:Details
/invokeai/capabilitiesreports a newvideo_imageflag, probed from the backend's/openapi.json. The pulldown is hidden, and Send/Append always go to image generation, until the configured InvokeAI has the route.append.invokeRefTargetinPERSISTED_SETTINGS,invoke_ref_targetinUserPreferences). It therefore survives iOS storage purges and is cleared by Reset to Defaults.invoke-ref-target.jsowns the pulldown. Both drawer renderers (swiper and grid) re-apply it after each re-render./use_ref_imagestill refuses them.docs/user-guide/invokeai-integration.mddocuments the choice and the per-model placement rules.Testing
use_ref_imagewithtarget="video": upload, then the/imageroute withimage_name/appendand an empty body; an upstream refusal returns 502; an unknown target returns 422.video_imagecapability flag.invoke-ref-target.test.jsinvoke-recall.test.js, including a remembered "video" being ignored on an unsupported backendruff,eslintandprettierare clean.🤖 Generated with Claude Code