From 2f9d85f4c734c386a766f391c584490734c381ed Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Mon, 5 Jan 2026 19:28:06 +0000 Subject: [PATCH] docs: finalize model config decisions --- docs/proposals/model-config.md | 18 +++++------------- 1 file changed, 5 insertions(+), 13 deletions(-) diff --git a/docs/proposals/model-config.md b/docs/proposals/model-config.md index 496e7a498..7de0d54d6 100644 --- a/docs/proposals/model-config.md +++ b/docs/proposals/model-config.md @@ -138,17 +138,9 @@ Outputs Auto-run - Gateway start detects legacy keys and runs doctor migration. -## Open questions +## Decisions -1) Per-provider vs per-model auth order -- Proposed: per-provider only (`auth.order`). -- Alternative: allow `agent.models[...].authOrder` override. - -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? +- Auth order is per-provider (`auth.order`). +- Doctor migration is required; gateway will auto-run on startup when legacy keys detected. +- `/model Opus@profile` is explicit session override only. +- Image routing override only when `agent.imageModel` is explicitly configured.