Explanation
Bring your own model (BYOM)
Why codingassist.bot is provider-agnostic and how the BYOM contract works.
codingassist.bot is provider-agnostic by design. Every LLM-touching step calls a Provider interface; concrete adapters exist for OpenAI, Anthropic, Azure OpenAI, and Bedrock — and you can plug your own.
The contract
interface Provider {
id: string;
complete(prompt: Prompt, opts: { temperature: 0; seed: number }): Promise<Completion>;
embed(text: string): Promise<Embedding>;
}Three properties matter:
temperature: 0is hard-coded — non-determinism breaks replay- A
seedis supplied for any provider that supports it - The output is schema-validated before it leaves the plane
Why?
- Cost control — pin Stage 1 to a cheap model, Stage 2 to a strong one
- Compliance — keep regulated workloads on Azure OpenAI in your tenancy
- Resilience — survive a provider outage by routing to a fallback
Configuration
# codingassist.policy.yaml
providers:
context: { provider: openai, model: gpt-4o-mini }
intent: { provider: anthropic, model: claude-sonnet-4-5 }
security: { provider: azure-openai, deployment: gpt-4o, region: eu-west }
fallback:
intent: { provider: openai, model: gpt-4o }Related
Was this page helpful?