๐ First Run Guide
November 30, 2025 ยท View on GitHub
Source of truth lives in README.md and docs/. Make changes via PRs to the repo; CI auto-publishes to the Wiki.
๐ First Run Guide
Get your first AI-powered music recommendations working perfectly. This guide walks through your initial setup, testing, and optimization.
โ Pre-Flight Checklist
Before starting, ensure:
- โ Lidarr Running: Accessible at http://localhost:8686
- โ Plugins Enabled: Settings โ General โ "Enable Plugins" is checked
- โ Brainarr Installed: Visible in Settings โ Import Lists โ Add (+)
- โ AI Provider Ready: At least one provider configured (see Provider Setup)
๐ฏ Step 1: Initial Configuration
Access Brainarr Settings
- Settings โ Import Lists โ Add (+)
- Select "Brainarr" from the list
- You'll see the configuration interface
Essential Settings
Provider Configuration
- Provider: Choose your preferred AI service
- Local: Ollama, LM Studio (no API key needed, runs offline)
- Cloud: OpenAI, Anthropic, Gemini, DeepSeek, Groq, Perplexity, OpenRouter (requires API key)
- Subscription: Claude Code, OpenAI Codex (uses existing CLI credentials, no separate API key)
- API Key/URL: Enter credentials for your chosen provider (not needed for subscription providers)
- Model: Select appropriate model (defaults are recommended)
Recommendation Settings
- Max Recommendations: Start with
10for testing - Discovery Mode: Use
Adjacentfor balanced discovery - Recommendation Mode: Try
Specific Albumsfirst - Sampling Strategy: Use
Balancedfor optimal results (useComprehensivefor powerful models) - Backfill Strategy:
Aggressive(default; strongly hits target)
Basic Settings
- Name:
Brainarr AI Recommendations(or custom name) - Enable Automatic Add: โ (so Lidarr imports recommendations)
- Search for missing albums: โ (trigger downloads)
- Minimum Availability: Match your Lidarr quality settings
๐งช Step 2: Test Your Configuration
Connection Test
- After entering provider details, click "Test"
- Success: "Test was successful" โ
- Failure: Check error message and fix configuration
Common Test Issues:
- "Connection timeout": Check URL and firewall
- "Invalid API key": Verify key format and validity
- "Model not found": Ensure model exists for your provider
- "Rate limited": Wait a moment and retry
Manual Import Test
- Click "Manual Import" button
- Watch for System โ Tasks activity
- Check System โ Logs for detailed progress
- Should complete in 30-60 seconds
Expected Log Messages:
Info: [Brainarr] Starting recommendation generation...
Info: [Brainarr] Analyzing library profile (X albums, Y artists)...
Info: [Brainarr] Requesting recommendations from [Provider]...
Info: [Brainarr] Generated X unique recommendations
Info: [Brainarr] Import completed successfully
๐ต Step 3: Review Your First Recommendations
Check Generated Recommendations
- Activity โ Queue - See albums being processed
- Wanted โ Search All - See albums added for search
- Activity โ History - Track download progress
Quality Assessment
Good Recommendations Look Like:
- โ Relevant Artists: Similar to your existing library
- โ Discoverable: New artists that match your taste
- โ Available: Albums that exist and can be found
- โ Balanced: Mix of familiar and exploratory content
Poor Recommendations Might Be:
- โ Duplicates: Albums you already have (shouldn't happen with proper deduplication)
- โ Hallucinations: Non-existent albums or artists
- โ Off-Target: Completely different genres than your library
- โ Unavailable: Albums that can't be found by your indexers
Recommendation Analysis
Review in Lidarr:
- Wanted โ Manual Import to see what was added
- Music โ Add New to see discovered albums
- Activity โ Queue to track download progress
Check Quality:
- Look for artists similar to your existing collection
- Verify albums actually exist (no AI hallucinations)
- Ensure reasonable genre/style matching
- Confirm release dates are realistic
โ๏ธ Step 4: Optimization
Based on your first results, optimize settings:
If Recommendations Are Too Similar
Discovery Mode: Adjacent โ Exploratory
Sampling Strategy: Balanced โ Comprehensive
Max Recommendations: Increase to 20-30
If Recommendations Are Too Random
Discovery Mode: Exploratory โ Similar
Sampling Strategy: Comprehensive โ Minimal
Consider different AI provider (Claude for reasoning)
If Getting Duplicates
Check library sync in Lidarr
Verify deduplication is working (check logs)
Consider Artist-Only mode instead of Albums
If Low Success Rate
Switch to premium provider (Claude, GPT-4o)
Use subscription providers if you have Claude Code or Codex CLI installed
Increase Max Recommendations (more attempts)
Check indexer connectivity and availability
Large Context Tip (Local Models)
- If your local model supports 32kโ40k context (e.g., Qwen3), set Sampling Strategy to Comprehensive.
- Combine with Backfill Strategy: Standard/Aggressive for better first-pass coverage thanks to initial oversampling.
๐ Understanding Performance Metrics
Key Metrics to Monitor
Provider Performance
- Response Time: How fast your AI provider responds
- Success Rate: Percentage of successful API calls
- Cache Hit Rate: How often cached results are reused
Recommendation Quality
- Uniqueness Rate: Percentage of non-duplicate recommendations
- Discovery Success: How many recommendations lead to actual downloads
- User Acceptance: Manual tracking of recommendations you actually want
Performance Optimization
Cache Settings
Fast Libraries (weekly changes): Cache = 30 minutes
Stable Libraries (monthly changes): Cache = 120 minutes
Testing/Tuning: Cache = 5 minutes
Request Optimization
Small Library (< 500 albums): Max Recs = 10
Medium Library (500-2000 albums): Max Recs = 20
Large Library (2000+ albums): Max Recs = 30-50
๐ง Advanced First Run Settings
Custom Filters
Add custom hallucination filters if needed:
Custom Filter Patterns:
- "AI Version"
- "Director's Cut"
- "Extended Universe"
- "Reimagined"
Debug Logging
For troubleshooting, enable enhanced logging:
- Settings โ General โ Logging
- Log Level:
Debug(temporarily) - Generate recommendations
- System โ Logs for detailed output
- Important: Return to
Infolevel after testing
๐ Step 5: Schedule Automatic Updates
Configure Refresh Interval
- Import Lists โ Brainarr โ Advanced Settings
- Refresh Interval: Recommended values:
- Active Discovery: 6-12 hours
- Passive Discovery: 24-48 hours
- Large Libraries: 48-72 hours
Monitor Performance
- Activity โ Queue: Track download success
- System โ Tasks: Monitor health checks
- System โ Logs: Watch for any issues
๐จ Troubleshooting First Run Issues
No Recommendations Generated
Check:
- Provider Test: Does connection test pass?
- Library Size: Do you have enough music for analysis?
- API Limits: Have you exceeded free tier limits?
- Logs: Any error messages in System โ Logs?
Solutions:
# Check Lidarr logs for errors
tail -f /var/lib/lidarr/.config/Lidarr/logs/lidarr.txt | grep Brainarr
# Common fixes:
- Verify API key format
- Check provider service status
- Ensure sufficient library content (10+ albums minimum)
- Try different provider temporarily
Poor Quality Recommendations
Symptoms:
- All recommendations are duplicates
- Recommendations are completely off-genre
- Getting non-existent albums (hallucinations)
Solutions:
- Try Different Provider: Each AI has different strengths
- Adjust Discovery Mode: Similar vs. Adjacent vs. Exploratory
- Change Sampling Strategy: Minimal vs. Balanced vs. Comprehensive
- Enable Strict Validation: Filters more aggressively
Performance Issues
Slow Response Times:
- Local Providers: Check CPU/GPU resources
- Cloud Providers: Try different region/model
- Network: Check internet connection speed
High Resource Usage:
- Reduce Max Recommendations: Lower batch sizes
- Increase Cache Duration: Reduce API call frequency
- Use Faster Models: Trade quality for speed if needed
๐ฏ Success Criteria
Your first run is successful when:
โ Connection: Provider test passes consistently โ Generation: Recommendations are created without errors โ Quality: Recommendations match your music taste โ Uniqueness: No duplicates with existing library โ Variety: Good mix of familiar and new content โ Performance: Completes within reasonable time (< 2 minutes)
๐ Iterative Improvement
Week 1: Baseline
- Use default settings
- Monitor success rate
- Note preference patterns
Week 2: Optimization
- Adjust discovery mode based on results
- Fine-tune recommendation count
- Experiment with different providers
Week 3: Advanced Tuning
- Configure multi-provider setup
- Optimize cache settings
- Add custom filters if needed
๐ Graduation: You're Ready!
Once you have reliable, quality recommendations, you can:
- Advanced Settings - Explore deeper customization
- Health Monitoring - Set up monitoring and alerting
- Multi-Provider Failover - Configure failover strategies