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

Include Mistral AI #7

Open
nhdez opened this issue Mar 12, 2025 · 4 comments · May be fixed by #43
Open

Include Mistral AI #7

nhdez opened this issue Mar 12, 2025 · 4 comments · May be fixed by #43
Labels
new provider New provider integration

Comments

@nhdez
Copy link

nhdez commented Mar 12, 2025

Hello,

First of, congratulations, this is a really nice addition to the Ruby ecosystem. Thank you!

The included models are very nice, I just thought it would be nice to have Mistral added, since they also have some powerful features and have some really nice tokenomics.

Again, amazing work, thanks for this Gem!

@OriPekelman
Copy link

Started a branch here: https://github.com/OriPekelman/ruby_llm/tree/mistral partially functional. Tool calling is failing and I didn't spend much time on getting the whole multi-modal vibe going.

@crmne
Copy link
Owner

crmne commented Mar 17, 2025

Great to see community interest in Mistral! 🇪🇺 I'm looking forward to seeing that PR come through. Would be a fantastic addition to the library.

@OriPekelman
Copy link

Nice that you have interest in this :)

  1. I'll align the testing strategy with yours (maybe we want to be able to test providers separately, so you don't have to have api keys for all.... We could in
    'claude-3-5-haiku-20241022',
    and similar filter for only "present" API keys and have a single failing test for not all api keys present. Or just a warning .
  2. Figure-out the vision and other APIs, the basics are there.
  3. What else would you have me do? If you are interested I can try to add some functionality. My favorite is fine-tuning:) if interested I'll open a separate issue for that to figure the API

@OriPekelman
Copy link

Pull request opened on PR #43

@crmne crmne added the new provider New provider integration label Mar 23, 2025
@crmne crmne linked a pull request Mar 23, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new provider New provider integration
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants