Add details about model providers

[mrubens]

Important

Add detailed documentation for various model providers supported by Roo Code and update the sidebar to include these documents.

• Documentation:
  • Adds detailed documentation for model providers in docs/providers/ including Anthropic, AWS Bedrock, DeepSeek, Google Gemini, Glama, LM Studio, Mistral, Ollama, OpenAI, OpenAI-Compatible, OpenRouter, Requesty, Unbound, Vertex AI, and VS Code Language Model API.
  • Each provider document includes sections on obtaining API keys, supported models, configuration in Roo Code, and tips/notes.
• Sidebar:
  • Updates sidebars.ts to include a new 'Model Providers' category with links to the new provider documentation.

^{This description was created by for 361eaac. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 8606db9 in 1 minute and 26 seconds

More details

• Looked at 903 lines of code in 17 files
• Skipped 0 files when reviewing.
• Skipped posting 21 drafted comments based on config settings.

1. docs/faq.md:35

• Draft comment:
  Provider links updated to use relative paths. Confirm all links point to the correct new provider pages.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is asking the PR author to confirm that all links point to the correct new provider pages. This falls under the rule of not asking the PR author to confirm their intention or to double-check things. Therefore, this comment should be removed.

2. sidebars.ts:47

• Draft comment:
  New 'Model Providers' category added. Verify its placement and that the ordering is optimal.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is asking the PR author to verify the placement and ordering of a new category, which violates the rule against asking the author to confirm or verify things. It doesn't provide a specific suggestion or point out a clear issue.

3. docs/providers/mistral.md:18

• Draft comment:
  Markdown table formatting looks good; ensure consistent column widths for readability.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is purely informative and does not provide a specific code suggestion or request for clarification. It does not align with the rules provided, which discourage purely informative comments.

4. docs/providers/*:1

• Draft comment:
  Ensure each new provider file ends with a newline for consistency.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

5. docs/faq.md:35

• Draft comment:
  Links in FAQs now use absolute paths; verify consistency across docs.
• Reason this comment was not posted:
  Marked as duplicate.

6. docs/providers/anthropic.md:1

• Draft comment:
  Clear layout and structured instructions; formatting is consistent.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

7. docs/providers/bedrock.md:13

• Draft comment:
  Consider adding a language specifier (e.g. 'bash') for the CLI code block.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  This comment is purely informative and does not provide a specific code suggestion or request for clarification. It does not align with the rules provided, which prohibit purely informative comments.

8. docs/providers/deepseek.md:1

• Draft comment:
  Documentation is clear and concise; no issues noted.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

9. docs/providers/gemini.md:1

• Draft comment:
  Instructions are clear; ensure the Google AI links remain up-to-date.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

10. docs/providers/glama.md:1

• Draft comment:
  Well-structured doc; check that sample model IDs (e.g. 'anthropic/claude-3-5-sonnet') are current.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

11. docs/providers/lmstudio.md:1

• Draft comment:
  Clear setup instructions; verify consistency of model file naming conventions.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

12. docs/providers/mistral.md:16

• Draft comment:
  Table formatting looks good; codestral instructions are clear.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

13. docs/providers/ollama.md:1

• Draft comment:
  Documentation is comprehensive; verify default base URL remains correct.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

14. docs/providers/openai-compatible.md:1

• Draft comment:
  Comprehensive guide; instructions are succinct and clear.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

15. docs/providers/openai.md:1

• Draft comment:
  Well-documented steps; consider clarifying scenarios for custom Base URL usage.
• Reason this comment was not posted:
  Confidence changes required: 30% <= threshold 50%
  None

16. docs/providers/openrouter.md:1

• Draft comment:
  Clear guide; links and model selection instructions are consistent.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

17. docs/providers/requesty.md:1

• Draft comment:
  Thorough documentation; ensure pricing and caching details remain updated.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

18. docs/providers/unbound.md:1

• Draft comment:
  Instructions are clear; security emphasis notes add value.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

19. docs/providers/vertex.md:1

• Draft comment:
  Documentation is detailed; confirm ADC instructions are current.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

20. docs/providers/vscode-lm.md:1

• Draft comment:
  Experimental feature noted; troubleshooting guidance is useful.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

21. sidebars.ts:47

• Draft comment:
  New 'Model Providers' category looks well integrated; verify provider order meets UX requirements.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_zeSPciXwquLEXiti

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

👍 Looks good to me! Incremental review on 361eaac in 1 minute and 37 seconds

More details

• Looked at 902 lines of code in 17 files
• Skipped 0 files when reviewing.
• Skipped posting 34 drafted comments based on config settings.

1. docs/faq.md:35

• Draft comment:
  Excellent update: provider links now include proper relative paths. Ensure consistency across all links.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

2. docs/providers/anthropic.md:1

• Draft comment:
  Good documentation for Anthropic setup. All required details are clear.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

3. docs/providers/bedrock.md:12

• Draft comment:
  AWS CLI code block is properly indented. Ensure instructions remain up-to-date with AWS CLI changes.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

4. docs/providers/deepseek.md:1

• Draft comment:
  DeepSeek documentation is concise and clear. All key steps for API key setup are included.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

5. docs/providers/gemini.md:1

• Draft comment:
  Gemini documentation looks good. Ensure that the example models stay updated as API evolves.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

6. docs/providers/glama.md:1

• Draft comment:
  Glama documentation is clear and the instructions for retrieving API key are straightforward.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

7. docs/providers/lmstudio.md:1

• Draft comment:
  LM Studio setup instructions are detailed and easy to follow. The troubleshooting note is a nice touch.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

8. docs/providers/mistral.md:1

• Draft comment:
  Mistral documentation is comprehensive with table details. The separation for Codestral usage is clear.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

9. docs/providers/ollama.md:1

• Draft comment:
  Ollama documentation is well-structured, including download instructions and command usage examples.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

10. docs/providers/openai-compatible.md:1

• Draft comment:
  The OpenAI Compatible guide is clear with step-by-step configuration details and troubleshooting tips.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

11. docs/providers/openai.md:1

• Draft comment:
  OpenAI documentation is concise and clear. Good to see both API key and model selection instructions.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

12. docs/providers/openrouter.md:1

• Draft comment:
  OpenRouter documentation is complete with API key and model selection details, including optional custom base URL.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

13. docs/providers/requesty.md:1

• Draft comment:
  Requesty guide is thorough. It clearly lists supported models and configuration steps with important notes.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

14. docs/providers/unbound.md:1

• Draft comment:
  Unbound documentation is clear, including API key instructions and emphasis on using full model IDs.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

15. docs/providers/vertex.md:1

• Draft comment:
  Vertex AI documentation is detailed with prerequisites and configuration steps. The note on using model IDs is crucial.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

16. docs/providers/vscode-lm.md:1

• Draft comment:
  VS Code LM API documentation is very experimental. Good emphasis on feedback and troubleshooting.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

17. sidebars.ts:46

• Draft comment:
  Sidebar for 'Model Providers' is well organized. Confirm all provider docs are linked correctly.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

18. docs/faq.md:35

• Draft comment:
  Good update using relative links for API providers. Verify all links resolve correctly in production.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

19. docs/providers/anthropic.md:1

• Draft comment:
  Comprehensive Anthropic provider guide. Consider emphasizing secure storage of API keys.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

20. docs/providers/bedrock.md:13

• Draft comment:
  Ensure the AWS CLI command block formatting is consistent; remove extra indentation if possible.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50%
  This is a documentation file and the comment is about pure formatting. While the indentation is slightly inconsistent, it's a very minor issue that doesn't affect functionality or readability. Our rules state not to make comments that are obvious or unimportant. Additionally, this kind of formatting should ideally be handled by automated tools like Prettier.
  The inconsistent formatting could potentially make the documentation look less professional. Code blocks in documentation should maintain consistent formatting.
  While consistency is good, this is an extremely minor formatting issue in a documentation file. The command is still perfectly readable and functional.
  Delete the comment. This is too minor of a formatting issue to warrant a PR comment, and such formatting should be handled by automated tools.

21. docs/providers/deepseek.md:1

• Draft comment:
  DeepSeek documentation is clear and concise.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50%
  None

22. docs/providers/gemini.md:1

• Draft comment:
  Gemini documentation looks good. Optionally, mention any rate limit details if applicable.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

23. docs/providers/glama.md:1

• Draft comment:
  Glama docs are well-structured; ensure the list of supported models stays updated with API changes.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

24. docs/providers/lmstudio.md:1

• Draft comment:
  LM Studio guide is clear. Verify that references to GGUF format remain current with LM Studio updates.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

25. docs/providers/mistral.md:1

• Draft comment:
  Mistral documentation and table are well formatted. Consider clarifying the differences for Codestral models.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

26. docs/providers/ollama.md:1

• Draft comment:
  Ollama documentation is clear. Confirm that the default server URL remains up-to-date.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

27. docs/providers/openai-compatible.md:1

• Draft comment:
  OpenAI Compatible guide is detailed; ensure example settings remain accurate for listed providers.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

28. docs/providers/openai.md:1

• Draft comment:
  OpenAI documentation is comprehensive. Clarify the optional custom base URL for advanced users.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

29. docs/providers/openrouter.md:1

• Draft comment:
  OpenRouter documentation is solid; verify that the fetched list of models is up-to-date.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

30. docs/providers/requesty.md:1

• Draft comment:
  Requesty instructions are detailed and clear. Confirm that pricing and caching notes are current.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

31. docs/providers/unbound.md:1

• Draft comment:
  Unbound documentation is complete. Consider reinforcing best practices for secure API key management.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

32. docs/providers/vertex.md:1

• Draft comment:
  Vertex AI guide is thorough. Ensure ADC and project setup instructions are accurate per the latest GCP practices.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

33. docs/providers/vscode-lm.md:1

• Draft comment:
  VS Code LM API documentation is clear for an experimental integration. Keep troubleshooting steps updated as the API evolves.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

34. sidebars.ts:46

• Draft comment:
  Sidebar configuration properly groups all provider docs. Verify that the order meets navigation requirements.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

Workflow ID: wflow_BWJAsdYrPjJ5zgdm

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.