Skip to content
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

Resolving discrepancy when image model is different than base model #1772

Closed
simistern opened this issue Jan 3, 2025 · 6 comments
Closed
Labels
bug Something isn't working

Comments

@simistern
Copy link

Describe the bug

During experimentation, I have found that it was not clear when the image model was not in sync with the base character model. For example, grok image generation API is not publicly available yet, so when asking my character to generate an image, it defaulted to openAI but that code was not set. It is not clear to developers that this is possible (the image gen using a different fallback than the base LLM). In the case where the image model is provided but does not work, it will assume the underlying access token is openAI, and will use groks token. I think this will extend to all other models where the image model API is not aligned with this core/generation file.

I have added some logging and a bit of logic to improve this and will take ownership of integrating grok image gen when it becomes publicly available, I am following along development in the xAI discord.

Currently seeking repo permissions to submit the PR for the enhancement to packages/core/src/generation and to add grok image gen capability when it becomes available.

To Reproduce

Set character model to grok and ask it to generate an image, user will receive error message pointing to openAI env keys not being set.

Expected behavior

User is informed that the image does not exist or will not match the base model, and that it will default to OPENAI

Screenshots
Screenshot 2025-01-03 at 3 01 19 PM
Screenshot 2025-01-03 at 3 01 46 PM

Additional context

@simistern simistern added the bug Something isn't working label Jan 3, 2025
Copy link
Contributor

github-actions bot commented Jan 3, 2025

Hello @simistern! Welcome to the ai16z community. Thank you for opening your first issue; we appreciate your contribution. You are now a ai16z contributor!

@AIFlowML
Copy link
Collaborator

AIFlowML commented Jan 3, 2025

Describe the bug

During experimentation, I have found that it was not clear when the image model was not in sync with the base character model. For example, grok image generation API is not publicly available yet, so when asking my character to generate an image, it defaulted to openAI but that code was not set. It is not clear to developers that this is possible (the image gen using a different fallback than the base LLM). In the case where the image model is provided but does not work, it will assume the underlying access token is openAI, and will use groks token. I think this will extend to all other models where the image model API is not aligned with this core/generation file.

I have added some logging and a bit of logic to improve this and will take ownership of integrating grok image gen when it becomes publicly available, I am following along development in the xAI discord.

Currently seeking repo permissions to submit the PR for the enhancement to packages/core/src/generation and to add grok image gen capability when it becomes available.

To Reproduce

Set character model to grok and ask it to generate an image, user will receive error message pointing to openAI env keys not being set.

Expected behavior

User is informed that the image does not exist or will not match the base model, and that it will default to OPENAI

Screenshots Screenshot 2025-01-03 at 3 01 19 PM Screenshot 2025-01-03 at 3 01 46 PM

Additional context

It has been like this since a bit.
the image related models are called into the pluing too as OAI.
In the next release we wil for sure solve this.

@tcm390
Copy link
Collaborator

tcm390 commented Jan 3, 2025

Hi @simistern, are you working on resolving this issue?

@simistern
Copy link
Author

Hi @tcm390, I have resolved the issue on a local branch but I think I need permissions to submit the PR? Is there a process for being allowed to submit PR's?

@simistern
Copy link
Author

simistern commented Jan 4, 2025

Describe the bug
During experimentation, I have found that it was not clear when the image model was not in sync with the base character model. For example, grok image generation API is not publicly available yet, so when asking my character to generate an image, it defaulted to openAI but that code was not set. It is not clear to developers that this is possible (the image gen using a different fallback than the base LLM). In the case where the image model is provided but does not work, it will assume the underlying access token is openAI, and will use groks token. I think this will extend to all other models where the image model API is not aligned with this core/generation file.
I have added some logging and a bit of logic to improve this and will take ownership of integrating grok image gen when it becomes publicly available, I am following along development in the xAI discord.
Currently seeking repo permissions to submit the PR for the enhancement to packages/core/src/generation and to add grok image gen capability when it becomes available.
To Reproduce
Set character model to grok and ask it to generate an image, user will receive error message pointing to openAI env keys not being set.
Expected behavior
User is informed that the image does not exist or will not match the base model, and that it will default to OPENAI
Screenshots Screenshot 2025-01-03 at 3 01 19 PM Screenshot 2025-01-03 at 3 01 46 PM
Additional context

It has been like this since a bit. the image related models are called into the pluing too as OAI. In the next release we wil for sure solve this.

@AIFlowML I have fixed this locally, happy to submit the PR and become a contributor :)

@AIFlowML
Copy link
Collaborator

AIFlowML commented Jan 6, 2025

The user solved locally the problem and is ready to PR
Yes @simistern send over the PR we will review it.

@AIFlowML AIFlowML closed this as completed Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants