From 6439fb193cb971d3b2b1c6fec6f3cbcb74d92f0c Mon Sep 17 00:00:00 2001 From: Evan Date: Wed, 15 Apr 2026 12:49:38 +0900 Subject: [PATCH] fix: add api_key field to provider schema for inline key setup (#57) The provider creation form only collected api_key_env (the env var name) but not the actual key value. New providers were always created as "unconfigured" because no key was stored. Add an optional secret api_key field so the dashboard can pass the key value during creation. The backend strips it from the TOML and saves it to secrets.env instead. --- schema.toml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/schema.toml b/schema.toml index 155ab43..3271a60 100644 --- a/schema.toml +++ b/schema.toml @@ -41,6 +41,12 @@ required = true description = "Whether an API key is needed (false for local providers)" example = true +[provider.fields.api_key] +type = "string" +required = false +description = "API key value (stored securely in secrets.env, not in the TOML file)" +secret = true + # --- Provider: nested [[models]] section --- [provider.sections.models]