First working version of Flux Plugin. #5410
Conversation
Display of images in agent chat directly ill require some fixing, like with dallE before
…e calls. in order to render multiple images from one call (possible on BFL/FLUX side) a change on librechat tool handling is required
…and possible future introduction of a separate image generation credit inside librechat. currently only working for flux but could be abstracted for any image generation.
…nvironments where there is a default key for everyone but a user wants to use an own key. This could also be changed with UI but I find this also quite explicit. Ofcourse keys are then in the chats which is ugly. However I don't have a better solution right now
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
There was a problem hiding this comment.
ESLint found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.
|
Agent image handling is now improved and working like with dallE. |
|
@leondape Thanks for picking up the work on this |
bugfix: fetching flux finetune models works now
Fixed generation of finetune models
…netuned image generation support - Introduced new 'generate_finetuned' action in schema - Implemented generateFinetunedImage method with robust error handling - Added validation for finetuned generation endpoints - Enhanced logging and transaction tracking for finetuned image generation - Improved payload construction for finetuned image requests
|
this would be really cool if it could make it to the repo |
|
Thanks, the image transaction stuff should really be part of a separate PR, I may just fork this and do so... |
|
I refactored flux without image transaction logic using the new Agent format, which was not used originally. The new format allows the LLM to actually see the image initially after the generation run for greater understanding of what was generated.
The new format can effectively make any tool an image tool without needing to edit The motivation to remove image transactions is that this can be done centrally with a standardized format, since with the new format, all images are being processed in one place, so there's no longer a need to pass |
This is a well working implementation of a BFL Flux tool to be used by agents.
It includes a variety of parameters and best practices for image prompts.
Credits also go to @jmaddington and his work on his fork.
Images are properly handled like with DallE
introduced an option image transaction collection in the DB to track image generation usage for flux.
Option to provide own API key via chat while default API key is provided via .env
New feature (non-breaking change which adds functionality)
This change requires a documentation update
Testing
Tools don't have test coverage.
Checklist