Quick Configuration
- Via Application Settings
- Via Configuration File
- Import Configuration
Step-by-Step Setup
1
Open RooCode Settings
- Launch RooCode application
- Click the gear icon ⚙️ (bottom-left corner)
- Navigate to:
Settings → API Configuration
2
Select Provider Type
- Provider Type: Select
OpenAI Compatible - This enables custom base URL configuration
- Allows MegaLLM integration
3
Configure API Endpoint
- Base URL:
https://ai.megallm.io/v1 - API Key:
sk-mega-your-api-key-here - Organization: Leave empty (not required)
- Click Save
4
Choose Default Model
- Default Model:
gpt-5 - Fallback Model:
gpt-4o(optional) - Temperature:
0.7(balanced creativity) - Max Tokens:
4096
5
Enable Features
- Code Completion
- Chat Interface
- Code Review
- Refactoring Assistant
- Multi-File Edit
Scenario Examples
Scenario 1: First-Time Installation
Complete setup from downloading to first use:1
Download and Install RooCode
- Visit RooCode.io (example URL)
- Download for your OS (Windows/macOS/Linux)
- Install the application
- Launch RooCode
2
Get MegaLLM API Key
- Visit MegaLLM Dashboard
- Sign up or log in
- Navigate to API Keys section
- Click Create New Key
- Copy the key (starts with
sk-mega-)
3
Configure API Provider
In RooCode:
- Click ⚙️ Settings icon
- Go to API Configuration
- Select Provider:
OpenAI Compatible - Enter Base URL:
https://ai.megallm.io/v1 - Paste API Key:
sk-mega-your-key - Click Test Connection (should show ✓ Success)
- Click Save
4
Choose Your First Model
- In Settings → Model Selection
- Select:
gpt-5(recommended for general use) - Or browse available models
- Set Temperature:
0.7(balanced) - Save settings
5
Test Configuration
- Open a new chat in RooCode
- Type:
Hello! What model are you using? - Should respond with model information
- Try:
Write a hello world function in Python
Scenario 2: Team Setup with Shared Configuration
Set up RooCode for an entire development team: Scenario: Development team of 10 people need consistent RooCode configuration Step 1: Team Lead Creates Base Configteam-roocode-config.json:
ROOCODE_SETUP.md:
- Same AI model (gpt-5)
- Same temperature and settings
- Same custom prompts
- Same coding standards
- Personal API keys (not shared)
Scenario 3: Project-Specific Configurations
Use different RooCode configurations for different project types: Python Data Science Project:roocode-datascience.json:
roocode-webapp.json:
roocode-systems.json:
Scenario 4: Migration from Cursor/Other AI Tools
Switching from another AI coding tool to RooCode with MegaLLM: Current Setup: Using Cursor with OpenAI Why Switch to RooCode + MegaLLM:- Access to multiple models (GPT, Claude, Gemini) with one key
- Standalone app (not tied to specific editor)
- Better pricing and no seat limits
- More customization options
1
Export Current Preferences
From Cursor (if possible):
- Note your preferred models
- Save any custom prompts
- Document keyboard shortcuts you use
2
Install RooCode
Download and install RooCode for your OS
3
Configure MegaLLM
4
Recreate Custom Prompts
Add your frequently used prompts:
5
Test Functionality
Compare side-by-side:
- Open same code in both tools
- Ask same questions
- Compare code generation quality
- Evaluate response speed
| Feature | Cursor | RooCode + MegaLLM |
|---|---|---|
| Editor Integration | VS Code fork | Standalone + Any Editor |
| Models Available | GPT-4, GPT-3.5 | GPT, Claude, Gemini, and more |
| API Key | OpenAI only | One key for all models |
| Pricing | Per-seat subscription | Pay-per-use |
| Customization | Limited | Extensive |
| Offline Mode | No | No |
Scenario 5: Multi-Model Workflow
Use different models for different types of tasks: Configuration with Model Profiles:- Click model dropdown (top bar)
- Select profile: Fast / Balanced / Quality / Creative / Analysis
- Profile applied to current session
Scenario 6: CI/CD Integration
Use RooCode API for automated code reviews in CI/CD: GitHub Actions Example:.github/workflows/roocode-review.yml:
Configuration Options
Complete Reference
Model Selection Guide
| Task | Recommended Model | Why |
|---|---|---|
| Quick Completions | gpt-4o-mini | Fastest, cost-effective |
| Code Review | claude-sonnet-4 | Excellent analysis |
| Complex Logic | claude-opus-4-1-20250805 | Superior reasoning |
| Web Development | gpt-5 | Best for JS/TS/React |
| Documentation | gpt-5 | Clear, engaging writing |
| Data Science | claude-sonnet-4 | Strong with pandas/numpy |
| Systems Code | gemini-2.5-pro | Precise, mathematical |
Verification
Test 1: Chat Functionality
- Open RooCode
- Click New Chat
- Type:
Write a function to sort an array of objects by a property - Should receive working code
Test 2: Code Review
- Paste this code:
- Click Review Code button
- Should identify: Missing zero division check
Test 3: Multi-File Edit
- Open multi-file view
- Request: “Add error handling to all API calls”
- Should show changes across multiple files
- Review and apply changes
Test 4: Connection Status
Check status indicator (top-right):- 🟢 Green = Connected to MegaLLM
- 🟡 Yellow = Connecting…
- 🔴 Red = Connection failed
- Model:
gpt-5 - Endpoint:
https://ai.megallm.io/v1 - Token usage: Current session stats
Troubleshooting
Connection timeout errors
Connection timeout errors
Symptoms:
- “Failed to connect to API”
- Requests timeout after 30s
- Chat messages don’t send
-
Verify base URL is correct:
-
Test connectivity:
-
Check firewall:
- Allow RooCode through firewall
- Check corporate proxy settings
- Verify no VPN blocking
-
Increase timeout:
-
Test API key manually:
API key not recognized
API key not recognized
Symptoms:
- “Invalid API key” error
- 401 Unauthorized
- Authentication failed
-
Verify key format:
- Must start with
sk-mega- - Should be 60+ characters
- No extra spaces or line breaks
- No quotes in config file around the actual key
- Must start with
-
Check key is active:
- Login to Dashboard
- Go to API Keys
- Verify key shows as “Active”
- Check it’s not revoked or expired
-
Re-enter the key:
- Copy key from dashboard
- Delete old key from RooCode settings
- Paste new key
- Save and restart RooCode
-
Test key directly:
Poor quality responses
Poor quality responses
Symptoms:
- Irrelevant code suggestions
- Wrong programming language
- Incomplete responses
-
Provide better context:
- Set project language in settings
- Add framework information
- Use custom prompts
-
Adjust temperature:
-
Try different model:
-
Increase max tokens:
-
Use specific prompts:
Configuration not loading
Configuration not loading
Symptoms:
- Settings revert after restart
- Changes don’t apply
- Using default configuration
-
Check config file location:
-
Validate JSON syntax:
-
Check file permissions:
-
Reset to defaults:
- Backup current config
- Delete config.json
- Restart RooCode (creates new config)
- Reapply settings via UI
Application crashes or freezes
Application crashes or freezes
Symptoms:
- RooCode crashes on startup
- Freezes during long responses
- Unresponsive UI
-
Check system resources:
- Close other applications
- Ensure 4GB+ RAM available
- Check CPU usage
-
Reduce max tokens:
-
Disable streaming:
-
Clear cache:
-
Reinstall RooCode:
- Backup config.json
- Uninstall RooCode
- Download latest version
- Install and restore config
Best Practices
Project Configurations
Create separate configs for different project types
Model Profiles
Set up profiles for different tasks: fast, quality, creative
Custom Prompts
Define reusable prompts for common tasks
Monitor Usage
Check Dashboard regularly for token usage
Backup Configs
Keep backups of working configurations
Security
Use environment variables for API keys in shared configs

