Skip to main content
The providers configuration format is deprecated. Use the new model_list format instead for better flexibility and zero-code provider addition.

Overview

The legacy providers configuration was PicoClaw’s original way to configure LLM providers. It’s still supported for backward compatibility, but new configurations should use model_list.

Legacy Configuration Format

Supported Legacy Providers

  • anthropic - Anthropic Claude
  • openai - OpenAI GPT
  • litellm - LiteLLM Proxy
  • openrouter - OpenRouter
  • groq - Groq
  • zhipu - Zhipu AI (智谱)
  • vllm - vLLM
  • gemini - Google Gemini
  • nvidia - NVIDIA
  • ollama - Ollama (local)
  • moonshot - Moonshot AI
  • shengsuanyun - ShengsuanYun
  • deepseek - DeepSeek
  • cerebras - Cerebras
  • volcengine - Volcengine (火山引擎)
  • github_copilot - GitHub Copilot
  • antigravity - Google Cloud Code Assist
  • qwen - Alibaba Qwen
  • mistral - Mistral AI

Migration to model_list

Example 1: Single Provider

Old format:
New format:

Example 2: Multiple Providers

Old format:
New format:

Automatic Migration

PicoClaw automatically migrates legacy configurations at runtime:
  1. If model_list is empty and providers has configuration
  2. PicoClaw converts providers to model_list internally
  3. Your config file is not modified
  4. You can manually update to the new format at any time

Environment Variables (Legacy)

Legacy provider environment variables still work:

Provider-Specific Options

Request Timeout

Set custom timeout for provider requests (seconds):

Proxy Configuration

Configure HTTP proxy for provider:
Enable web search augmentation for OpenAI:

GitHub Copilot Connect Mode

Values: stdio or grpc

Why Migrate?

The new model_list format provides:
  1. Multiple models per provider - Configure GPT-5.2 and GPT-4o separately
  2. Load balancing - Multiple endpoints for the same model
  3. Better fallbacks - Explicit model fallback chains
  4. Zero-code providers - Add OpenAI-compatible APIs without code changes
  5. Cleaner configuration - Model-centric instead of provider-centric

Next Steps