let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: finalize model config decisions

Browse Source
This commit is contained in:
Peter Steinberger
2026-01-05 19:28:06 +00:00
parent cd12f34eba
commit 2f9d85f4c7
1 changed files with 5 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
docs/proposals/model-config.md
View File

@@ -138,17 +138,9 @@ Outputs
Auto-run Auto-run
- Gateway start detects legacy keys and runs doctor migration. - Gateway start detects legacy keys and runs doctor migration.
## Open questions ## Decisions
1) Per-provider vs per-model auth order - Auth order is per-provider (`auth.order`).
- Proposed: per-provider only (`auth.order`). - Doctor migration is required; gateway will auto-run on startup when legacy keys detected.
- Alternative: allow `agent.models[...].authOrder` override. - `/model Opus@profile` is explicit session override only.
- Image routing override only when `agent.imageModel` is explicitly configured.
2) /model auth pinning
- Keep `/model Opus@profile` for explicit session override only.
3) Image routing
- Only apply image routing override when `agent.imageModel` is explicitly configured.
4) Legacy compatibility
- Keep reading old keys if migration fails, or hard-break?