Prime OpenCode catalog before container login and model validation

This commit is contained in:
2026-10-09 23:34:01 +01:00
parent 08b8647d5b
commit 16389b8270
3 changed files with 157 additions and 18 deletions
+5 -1
View File
@@ -33,7 +33,11 @@ after completed setup; `./install.sh --relogin` opens it again without
deleting accounts. Setup asks which connected provider/model to validate, then
requires a real, small **tool-free model response** before marking setup complete
(provider charges may apply). `--model PROVIDER/MODEL` selects it explicitly;
reinstall retests the saved selection. New drafts/templates inherit this selection;
reinstall retests the saved selection. Login, discovery and validation prime
OpenCode's integration catalog in their own container/service. Discovery retries empty model
reads in the same container, avoiding a cold-start empty-catalog response.
An empty catalog is not proof of an invalid key; saved credentials are retained.
New drafts/templates inherit this selection;
published definitions and retry versions stay unchanged. Failed checks print
bounded, credential-redacted evidence and retain their OpenCode session.
The installer then starts/recreates the Compose services,