Coding Subscriptions

Forge treats approved external coding platforms as part of the core runtime contract, not side plugins.

Approved provider set for the active program

Claude Code
Codex
Kimi K2.5
GLM 5
MiniMax 2.5

What "coding subscriptions" means in Forge

In Forge, this term covers external platforms that can participate in coding-centric agent workflows through a normalized runtime contract.

That includes concerns such as:

session setup
capability negotiation
long-running task execution
structured event handling
interrupts and cancellation
usage tracking
authority-aware delegated execution

Why this belongs in core

For Forge, external coding systems are not ornamental integrations. They are execution surfaces that affect:

workflow portability
security posture
observability
downstream compatibility
developer ergonomics

Keeping them outside core would create contract drift across languages and products.

What Forge normalizes

Forge is not trying to erase vendor differences. It is normalizing the parts developers must be able to trust:

whether a provider can be used for a requested workflow
how a session is opened and closed
how events are observed
how usage is reported
how denials are surfaced
how security boundaries are enforced before provider execution

What Forge does not fake

Forge will not pretend that:

every provider supports the same advanced features
unsupported features can be safely downgraded
provider-specific behavior should leak into the common contract

That is why the capability matrix exists alongside the baseline contract.

Session model

Forge normalizes these providers through one session lifecycle:

validate configuration
negotiate capabilities
verify authority
open session
submit work
stream or poll events
record usage and audit data
interrupt, cancel, or complete
close the session cleanly

Security note

Some coding platforms may execute code, hold long-lived sessions, or create sub-agent behavior. Forge therefore requires authority checks before those sessions begin, not after they are already running.

Release status

This is an approved core contract under active implementation. Public docs in this portal should be read as the authoritative target contract until the release train ships the runtime implementation.