Troubleshooting

Solve common issues with CodinIT AI IDE, LLM providers, code generation errors, and AI-powered development environment problems.

Get AI coding help now

Can’t find your AI issue? Contact our support team for personalized assistance with LLM troubleshooting.

LLM provider issues for AI coding

Invalid AI model API key errors

Problem: Getting “Invalid API key” or “Authentication failed” errors with LLM providers for AI code generation.

Solutions:

1. Check LLM API key format: Ensure you’re copying the complete key from your AI provider dashboard
2. Verify AI key permissions: Some LLM providers require specific permissions for code generation API access
3. Check key expiration: Some AI API keys have expiration dates or usage limits
4. Test in provider dashboard: Verify your LLM key works directly with the AI provider

AI provider-specific tips:

• OpenAI GPT models: Keys start with sk- and are found in API Keys section
• Anthropic Claude: Keys start with sk-ant- and require console access for AI coding
• Google Gemini: Keys are 39 characters and need Gemini API enabled for code generation

Never share your API keys publicly or commit them to version control.

Rate limit exceeded

Problem: Hitting API rate limits or quota exceeded errors.

Solutions:

1. Check your usage: Monitor your account usage in the provider dashboard
2. Upgrade your plan: Consider a higher-tier plan for more usage
3. Implement retry logic: Add delays between API calls
4. Switch providers: Use alternative providers when one hits limits
5. Use local models: Consider Ollama for unlimited local inference

Set up multiple providers as fallbacks to avoid workflow interruption.

Provider connection failures

Problem: Unable to connect to AI providers or getting timeout errors.

Solutions:

1. Check internet connection: Ensure stable internet connectivity
2. Verify provider status: Check provider status pages for outages
3. Test different providers: Confirm if issue is specific to one provider
4. Check firewall settings: Corporate networks may block certain providers
5. Try different regions: Some providers offer regional endpoints

Network issues typically resolve themselves - try again in a few minutes.

Ollama models not appearing

Problem: Ollama models don’t show up in the model selector dropdown.

Solutions:

1. Install models first: Ensure you’ve installed Ollama models on your device before using them
2. Configure base URL: Go to Settings → Local Providers and set the Ollama base URL (e.g., http://127.0.0.1:11434)
3. Enable Ollama: Make sure Ollama provider is enabled in settings
4. Check Ollama service: Verify Ollama is running on your system
5. Refresh model list: Return to chat and open the provider/model dropdown to see available models

Docker users:

• Use host.docker.internal instead of localhost or 127.0.0.1 for the base URL
• Ensure Docker has network access to your host machine

After configuring Ollama settings, models should appear automatically in the provider dropdown.

MacOS Specific Issues

App won't open

Problem: Application fails to launch or shows security warning.

Solutions:

1. After moving the app to your Applications folder (or another location of your choice), open Terminal.
2. Enter the following command to remove the security quarantine:

xattr -cr /path/to/your/codinit...

This happens because the app is not notarized by Apple. We are working on getting it notarized for future releases.

Development Environment Issues

CodinIT won't launch

Problem: Application fails to start or gets stuck on loading screen.

Solutions:

1. Check system requirements: Ensure your system meets minimum requirements
2. Clear cache and restart: Reset application data and try again
3. Check for updates: Ensure you’re running the latest version
4. Firewall/antivirus: Temporarily disable security software
5. Port conflicts: Ensure required ports (3000, 5173) are available

Desktop-specific:

• Windows: Run as administrator or check Windows Security settings
• macOS: Allow through Gatekeeper and check accessibility permissions
• Linux: Check for missing dependencies or permission issues

Web version not loading

Problem: Web application won’t load or shows blank screen.

Solutions:

1. Browser compatibility: Use Chrome, Firefox, Safari, or Edge (latest versions)
2. Clear browser data: Clear cookies, cache, and local storage for CodinIT domain
3. Disable extensions: Try incognito mode or disable browser extensions
4. Check JavaScript: Ensure JavaScript is enabled in browser settings
5. Network restrictions: Verify no corporate proxies blocking the connection

The web version requires modern browser features - update if experiencing issues.

Terminal & File System Issues

Terminal not working

Problem: Built-in terminal fails to start or execute commands.

Solutions:

1. Check permissions: Ensure terminal has necessary file system permissions
2. Shell compatibility: Verify your default shell is supported (/bin/bash or /bin/zsh)
3. Docker issues: If using Docker, ensure Docker Desktop is running
4. Path issues: Check if commands are in your system PATH
5. Resource limits: Terminal may fail if system resources are exhausted

Use an external terminal if the built-in terminal continues to have issues.

File operations failing

Problem: Can’t create, edit, or delete files in the workspace.

Solutions:

1. Check file permissions: Ensure write permissions for the workspace directory
2. Disk space: Verify sufficient disk space is available
3. File locking: Other applications may have files locked
4. Antivirus interference: Security software may block file operations
5. Network drives: Some operations may not work on network-mounted drives

Large files or many simultaneous operations can cause performance issues.

Performance & Optimization

Application running slowly

Problem: CodinIT feels sluggish or unresponsive.

Solutions:

1. Close unused workspaces: Multiple open workspaces consume resources
2. Clear cache: Remove temporary files and cached data
3. Reduce AI provider load: Limit concurrent AI requests
4. Check system resources: Monitor CPU, memory, and disk usage
5. Update hardware: Consider SSD storage and sufficient RAM (8GB+ recommended)

Optimization tips:

• Use local models (Ollama) for faster inference
• Enable caching for frequently used responses
• Close unused browser tabs when using web version

AI responses are slow

Problem: AI completions and chat responses take too long.

Solutions:

1. Choose faster providers: Use Groq or GPT-5o-mini for quick responses
2. Optimize prompts: Shorter, more focused prompts get faster responses
3. Enable streaming: Use streaming responses for better perceived performance
4. Check network speed: Slow internet affects response times
5. Use local models: Ollama provides instant responses for supported models

Provider speed varies - test different providers to find the fastest for your needs.

Memory & Resource Issues

High memory usage

Problem: CodinIT using too much RAM or causing system slowdown.

Solutions:

1. Monitor usage: Check memory usage in system monitor/task manager
2. Close workspaces: Each workspace consumes memory
3. Clear caches: Remove temporary files and cached data regularly
4. Restart application: Fresh start often resolves memory issues
5. Check for leaks: Monitor if memory usage continuously grows

For desktop app:

• Check Activity Monitor (macOS) or Task Manager (Windows)
• Look for memory leaks over time
• Consider restarting if usage seems excessive

High CPU usage

Problem: CodinIT causing high CPU usage or fan noise.

Solutions:

1. Check AI requests: Multiple simultaneous AI requests increase CPU usage
2. Background processing: Some features process data in background
3. Docker containers: WebContainer or Docker processes may use CPU
4. Browser rendering: Web version may use more CPU for rendering
5. System load: Close other applications if system is overloaded

High CPU usage is normal during intensive AI operations or when running Docker containers.

Integration Issues

Git operations failing

Problem: Can’t clone, push, pull, or perform other Git operations.

Solutions:

1. Check credentials: Verify GitHub/GitLab authentication is working
2. Repository permissions: Ensure you have access to the repository
3. Network connectivity: Git operations require internet connection
4. SSH vs HTTPS: Try switching authentication methods
5. Repository size: Large repositories may timeout - try shallow clone

Authentication help:

• GitHub: Use personal access tokens or SSH keys
• GitLab: Generate access tokens in user settings
• SSH setup: Ensure SSH keys are properly configured

Sync issues with remote

Problem: Conflicts or sync problems with remote repositories.

Solutions:

1. Pull latest changes: Always pull before pushing your changes
2. Resolve conflicts: Use merge tools to resolve conflicting files
3. Check branch: Ensure you’re working on the correct branch
4. Force push carefully: Only use force push when necessary and with caution
5. Backup work: Create backups before resolving complex conflicts

Force pushing can overwrite others’ work - use with extreme caution.

Deployment Issues

Deployment failures

Problem: Can’t deploy to Vercel, Netlify, or other platforms.

Solutions:

1. Check build logs: Review deployment logs for specific error messages
2. Environment variables: Ensure all required environment variables are set
3. Build configuration: Verify build settings and package.json scripts
4. Platform limits: Check file size, build time, and other platform limits
5. Dependency issues: Ensure all dependencies are properly installed

Platform-specific:

• Vercel: Check functions config and API routes
• Netlify: Verify build command and publish directory
• GitHub Pages: Ensure correct branch and Jekyll configuration

Supabase connection issues

Problem: Can’t connect to or query Supabase database.

Solutions:

1. Check connection string: Verify project URL and anon key
2. RLS policies: Ensure Row Level Security allows your operations
3. API keys: Confirm you’re using the correct keys (anon vs service_role)
4. Network restrictions: Check if Supabase is blocked by firewall
5. Project status: Verify your Supabase project is active

Use Supabase dashboard to test queries directly if connection fails in CodinIT.

Getting Additional Help

Documentation

Browse our complete documentation for detailed guides and references.

GitHub Issues

Check existing issues or create new ones for bugs and features.

Contact Support

1. Gather information

   Before contacting support, collect:

   • Your CodinIT version
   • Operating system and browser (if using web version)
   • Steps to reproduce the issue
   • Any error messages or screenshots
   • Recent actions that may have caused the problem
2. Check existing solutions

   Search our documentation and community resources for similar issues before contacting support.

3. Contact us

   Reach out through:

   • Email: [e-mail]
   • In-app feedback: Use the feedback button in settings
   • GitHub: Create an issue for technical problems

Still having trouble? Don’t hesitate to reach out - our support team is here to help you succeed with CodinIT!