Skip to content

Add Mistral embedding provider for improved codebase indexing performance and cost efficiency #5932

@shariqriazz

Description

@shariqriazz

What specific problem does this solve?

Who is affected: All users who use codebase indexing features in Roo Code

When this happens: When users enable codebase indexing to improve AI context and code understanding

Current behavior: Users are limited to existing embedding providers, which may have suboptimal performance or cost considerations for embedding generation

Expected behavior: Users should have access to Mistral's codestral-embed model as an embedding provider option, which offers superior benchmark performance and is available at no cost

Impact:

  • Performance: Mistral's codestral-embed model shows significantly higher performance in embedding benchmarks compared to current options
  • Cost efficiency: The model is free to use, reducing operational costs for users and the platform
  • Quality: Better embeddings lead to more accurate code context and improved AI responses for code-related tasks
  • Competitive advantage: Keeping up with state-of-the-art embedding models ensures Roo Code remains competitive

Additional context (optional)

  • API Endpoint: Mistral provides an OpenAI-compatible API at https://api.mistral.ai/v1
  • Model: codestral-embed
  • Implementation reference: Similar to how Gemini was implemented for codebase indexing
  • Benchmark data: Mistral's codestral-embed shows superior performance metrics in code understanding tasks
  • Cost benefit: Free tier availability makes this an attractive option for users

This enhancement would provide users with a high-performance, cost-effective embedding option that could significantly improve their codebase indexing experience while reducing costs.

Roo Code Task Links (Optional)

No response

Request checklist

  • I've searched existing Issues and Discussions for duplicates
  • This describes a specific problem with clear impact and context

Interested in implementing this?

  • Yes, I'd like to help implement this feature

Implementation requirements

  • I understand this needs approval before implementation begins

How should this be solved? (REQUIRED if contributing, optional otherwise)

No response

How will we know it works? (Acceptance Criteria - REQUIRED if contributing, optional otherwise)

No response

Technical considerations (REQUIRED if contributing, optional otherwise)

No response

Trade-offs and risks (REQUIRED if contributing, optional otherwise)

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions