Provider Capability Matrix
Forge uses one mandatory baseline plus provider-specific advanced capabilities.
How to read this page
This page has two jobs:
- define the meaning of Forge capability categories
- show which providers are in scope for the active release program
It is not allowed to overclaim shipped provider behavior.
Baseline contract
Every approved provider is expected to support the baseline contract before it can ship as a core Forge provider.
Advanced capability definitions
| Capability | Meaning in Forge |
|---|---|
tool_calls |
Provider can participate in tool-oriented execution through the approved Forge contract |
delegated_agents |
Provider can support workflows that may create provider-managed agentic sub-runs |
terminal_session |
Provider can work through a terminal-oriented interaction surface |
structured_patch |
Provider can return patch-oriented coding output through a normalized result model |
attachments |
Provider can work with structured attachment inputs or outputs through the contract |
interrupts |
Provider supports meaningful interruption during execution |
resume_session |
Provider supports resuming an interrupted or persisted session |
approval_checkpoints |
Provider can surface checkpoints that map into Forge approval flows |
usage_streaming |
Provider can emit usage data during execution instead of only at completion |
transcript_export |
Provider can export session transcript data through a stable surface |
Approved provider matrix
| Provider | Scope status | Baseline requirement | Advanced-capability policy |
|---|---|---|---|
| Claude Code | Approved for core implementation | Must satisfy the baseline contract | May advertise only what is backed by executable coverage |
| Codex | Approved for core implementation | Must satisfy the baseline contract | May advertise only what is backed by executable coverage |
| Kimi K2.5 Coding | Approved for core implementation | Must satisfy the baseline contract | May advertise only what is backed by executable coverage |
| GLM 5 Coding | Approved for core implementation | Must satisfy the baseline contract | May advertise only what is backed by executable coverage |
| MiniMax 2.5 Coding | Approved for core implementation | Must satisfy the baseline contract | May advertise only what is backed by executable coverage |
| OpenAI | Approved as a direct model provider | Must satisfy the direct-provider core contract | May advertise only what is backed by executable coverage |
| Anthropic | Approved as a direct model provider | Must satisfy the direct-provider core contract | May advertise only what is backed by executable coverage |
| Google Gemini | Approved as a direct model provider | Must satisfy the direct-provider core contract | May advertise only what is backed by executable coverage |
| xAI | Approved as a direct model provider | Must satisfy the direct-provider core contract | May advertise only what is backed by executable coverage |
| DeepSeek | Approved as a direct model provider | Must satisfy the direct-provider core contract | May advertise only what is backed by executable coverage |
| Mistral | Approved as a direct model provider | Must satisfy the direct-provider core contract | May advertise only what is backed by executable coverage |
| Cohere | Approved as a direct model provider | Must satisfy the direct-provider core contract | May advertise only what is backed by executable coverage |
| Groq | Approved as a direct model provider | Must satisfy the direct-provider core contract | May advertise only what is backed by executable coverage |
| Moonshot AI | Approved as a direct model provider | Must satisfy the direct-provider core contract | May advertise only what is backed by executable coverage |
| Z.ai | Approved as a direct model provider | Must satisfy the direct-provider core contract | May advertise only what is backed by executable coverage |
| MiniMax | Approved as a direct model provider | Must satisfy the direct-provider core contract | May advertise only what is backed by executable coverage |
| Foundry | Approved as a core gateway provider | Must satisfy the gateway core contract | May advertise only what is backed by executable coverage |
| OpenRouter | Approved as a core gateway provider | Must satisfy the gateway core contract | May advertise only what is backed by executable coverage |
| Amazon Bedrock | Approved as a core provider host | Must satisfy the gateway or host core contract | May advertise only what is backed by executable coverage |
| Google Vertex AI | Approved as a core provider host | Must satisfy the gateway or host core contract | May advertise only what is backed by executable coverage |
| Microsoft Foundry | Approved as a core provider host | Must satisfy the gateway or host core contract | May advertise only what is backed by executable coverage |
Authentication strategies
Forge models provider authentication by strategy rather than assuming every coding product is pure OAuth.
| Strategy | Typical use |
|---|---|
browser_account_login |
Interactive account sign-in for tools like Claude Code or Codex |
api_key |
Vendor-issued bearer or platform API keys |
cloud_credentials |
Native cloud IAM, keyless, or environment-backed credential flows such as AWS-signed requests, Google Cloud native clients, or Azure keyless auth |
delegated_token |
Short-lived brokered capability material issued by Forge infrastructure |
Current hosted-provider note:
- Forge's current OpenAI-compatible Bedrock host path is API-key-backed
- Forge's current OpenAI-compatible Vertex AI host path is access-token-backed
- Forge's current Microsoft Foundry host path is API-key-backed, with keyless token-provider flows treated as a native-provider follow-on
Release-gate rule
This matrix is coupled to the Forge release gate. Public claims here must not outrun:
- executable coverage
- runtime implementation
- release-train status
Important rule
This table is a contract and release-gate surface, not marketing copy. A provider may only advertise advanced capabilities that are backed by executable coverage and runtime support.