feat(detection): Add support for Mistral Vibe agent#24
Closed
damienalexandre wants to merge 1 commit into
Closed
Conversation
Member
|
I think just checking for a Mistral API key feels too broad. |
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
2 participants
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.
Add support for Mistral Vibe CLI.
Mistral Vibe is an open source agent built by Mistral. There is no "clear" env var when running bash tools with it, but the API KEY is always pushed in the context as you can see here:
https://github.com/mistralai/mistral-vibe/blob/cafb6d4147479c3ab50e0a0fc88de553a48df69b/vibe/setup/auth/api_key_persistence.py#L54
So it's a "good enough" test in my opinion and it works on my setup.
Warning: It will not work for users who changed the
api_key_env_varsetting (it allow to change the name of the env var).