import type { Logger } from "@onenomad/przm-cortex-core"; /** * Seed an LLM provider config from environment variables. The intended * caller is the Cortex Cloud startup path on Fly — pyre-web's deploy * action stamps an OPENROUTER_API_KEY (and optional base URL + default * model) onto the per-tenant Fly machine, and a freshly provisioned * tenant comes up with enrichment-capable LLM routing already wired. * * Without this seed, every new tenant deploys with the bootstrap * `cortex.yaml` — empty providers, default task pointing at * `anthropic/claude-haiku-4.5` — and an operator has to SSH in, * apply the openrouter wizard, edit the task model, and restart. * That's not a product; it's a per-customer science project. * * Idempotent: re-running on a populated workspace re-applies the * wizard config (overwriting `cortex.local.yaml` provider block) and * re-stamps the default task. If the tenant has since edited their * provider config via the dashboard wizard, this overwrites it on * next restart — that's the right tradeoff because the env vars * are the source of truth for managed deployments. * * Env contract: * OPENROUTER_API_KEY required to fire the seed * PRZM_CORTEX_LLM_BASE_URL optional — defaults to OpenRouter's URL * when unset. For Azure OpenAI, set: * https://.openai.azure.com/openai/v1 * PRZM_CORTEX_LLM_DEFAULT_MODEL optional — defaults to the OpenRouter * package's bootstrap default. For Azure * set the deployment name (e.g. `gpt-4o-mini`). * * No-op when OPENROUTER_API_KEY is unset — self-hosted Cortex installs * keep the existing dashboard-wizard flow. */ export declare function seedLlmProviderFromEnv(logger: Logger): Promise; //# sourceMappingURL=seed-llm-provider.d.ts.map