docs: add quick guide for model_list vs providers configuration
This commit is contained in:
parent
009a8d702b
commit
64d6950435
1 changed files with 13 additions and 0 deletions
|
|
@ -39,6 +39,19 @@ This design also enables **multi-agent support** with flexible provider selectio
|
||||||
- **Load balancing**: Distribute requests across multiple endpoints
|
- **Load balancing**: Distribute requests across multiple endpoints
|
||||||
- **Centralized configuration**: Manage all providers in one place
|
- **Centralized configuration**: Manage all providers in one place
|
||||||
|
|
||||||
|
#### Quick Guide: `model_list` vs `providers`
|
||||||
|
|
||||||
|
If you are configuring PicoClaw for the first time, this is the most important distinction:
|
||||||
|
|
||||||
|
- `model_list` is the **recommended** and current configuration format.
|
||||||
|
- `providers` is a **legacy compatibility** format.
|
||||||
|
- Launcher UI writes model entries to `model_list`.
|
||||||
|
|
||||||
|
Use this rule of thumb:
|
||||||
|
|
||||||
|
- Using Launcher (`picoclaw-launcher` / `picoclaw-launcher-tui`): edit via UI, config is saved in `model_list`.
|
||||||
|
- Editing JSON manually: prefer `model_list`; use `providers` only for legacy setups.
|
||||||
|
|
||||||
#### 📋 All Supported Vendors
|
#### 📋 All Supported Vendors
|
||||||
|
|
||||||
| Vendor | `model` Prefix | Default API Base | Protocol | API Key |
|
| Vendor | `model` Prefix | Default API Base | Protocol | API Key |
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue