Documentation Index
Fetch the complete documentation index at: https://mintlify.com/QuantaAlpha/RepoMaster/llms.txt
Use this file to discover all available pages before exploring further.
Overview
RepoMaster supports multiple AI provider APIs with automatic fallback capabilities. Configure your preferred providers in the.env file to enable the multi-agent system.
At least one API provider must be configured for RepoMaster to function. The system automatically falls back to available providers based on priority.
Provider Priority
WhenDEFAULT_API_PROVIDER is not set or the configured provider is unavailable, RepoMaster uses this fallback order:
- OpenAI (gpt-4o, gpt-5)
- Claude (Anthropic)
- DeepSeek (deepseek-v3)
- Basic (OpenAI-compatible)
- Azure OpenAI
Setting Default Provider
Configure your preferred default provider inconfigs/.env:
Supported Providers
OpenAI
OpenAI
Configuration
Add these variables to yourconfigs/.env file:Default Values
- Model:
gpt-4o(ifOPENAI_MODELnot set) - Base URL: Uses OpenAI’s standard endpoint
Getting API Key
Get your OpenAI API key at platform.openai.com
Supported Models
gpt-4o- Recommended for most tasksgpt-5- Latest model (requires temperature=1.0)gpt-4-turbo- Fast and capable- Any OpenAI-compatible model
Special Notes
Anthropic Claude
Anthropic Claude
Configuration
Add these variables to yourconfigs/.env file:Default Values
- Model:
claude-3-5-sonnet-20241022(ifANTHROPIC_MODELnot set) - Base URL: Optional, uses Anthropic’s default endpoint
Getting API Key
Get your Anthropic API key at console.anthropic.com
Supported Models
claude-4-sonnet- Latest Sonnet modelclaude-3-5-sonnet-20241022- Previous stable versionclaude-sonnet-4-20250514- Available viabasic_claude4mode
Usage Example
DeepSeek
DeepSeek
Configuration
Add these variables to yourconfigs/.env file:Default Values
- Model:
deepseek-v3(default) - Base URL:
https://api.deepseek.com/v1
Getting API Key
Get your DeepSeek API key at platform.deepseek.com
Supported Models
deepseek-v3- Latest versiondeepseek-r1-0528- Available viabasic_deepseek_r1mode
Usage Example
Google Gemini
Google Gemini
Configuration
Add these variables to yourconfigs/.env file:Default Values
- Model:
gemini-2.5-pro(as specified in env.example)
Getting API Key
Get your Gemini API key at makersuite.google.com/app/apikey
Supported Models
gemini-2.5-pro- Latest Pro modelgemini-1.5-pro- Previous stable versiongemini-1.5-flash- Faster, lightweight option
Azure OpenAI
Azure OpenAI
Configuration
Azure OpenAI requires additional configuration parameters:Default Values
- Model:
gpt-4o(ifAZURE_OPENAI_MODELnot set) - API Type:
azure - API Version: Uses value from
AZURE_OPENAI_API_VERSION
Getting Started
Azure OpenAI requires an Azure subscription. Set up your resource at portal.azure.com
Configuration Steps
- Create an Azure OpenAI resource in Azure Portal
- Deploy a model (e.g., gpt-4o)
- Copy the endpoint URL and API key
- Set the appropriate API version
Usage Example
Advanced Provider Configurations
Basic Mode
Thebasic mode uses OpenAI configuration by default and is suitable for OpenAI-compatible endpoints:
Service-Specific Configurations
Some internal services use specific configurations defined inoai_config.py:68:
- summary: Uses
basicconfiguration - deepsearch: Uses
basicconfiguration - code_explore: Uses
basicconfiguration
Configuration Validation
RepoMaster automatically validates API configurations on startup:Validation Behavior
- No API Type Specified: Uses provider priority order
- Invalid/Empty API Key: Falls back to next available provider
- No Valid Keys Found: Raises error with helpful message
Skip Configuration Check
Additional Required APIs
Search and Document Processing
These APIs are required for deep search functionality:SERPER_API_KEY and JINA_API_KEY are required for the Deep Search Agent functionality.Troubleshooting
No Valid API Provider Found
Error:"No valid API provider found. Please configure at least one API key."
Solution: Ensure at least one provider is properly configured in configs/.env:
Provider Fallback Warning
Warning:"⚠️ API key for 'openai' is None or empty. Using provider priority fallback..."
This is normal behavior when a requested provider isn’t configured. RepoMaster automatically uses the next available provider.
Configuration File Not Found
Error: Configuration file issues on startup Solution: Copy the example configuration:Next Steps
Environment Setup
Complete environment variable configuration
Advanced Options
CLI flags and advanced configuration