Feature stages

On this page

Some Coder features are released in feature stages before they are generally available.

If you encounter an issue with any Coder feature, please submit a GitHub issue or join the Coder Discord.

Feature stages

Feature stage	Stable	Production-ready	Support	Description
Early Access	No	No	GitHub issues	For staging only. Not feature-complete or stable. Disabled by default.
Beta	No	Not fully	Docs, Discord, GitHub	Publicly available. In active development with minor bugs. Suitable for staging; optional for production. Not covered by SLA.
GA	Yes	Yes	License-based	Stable and tested. Enabled by default. Fully documented. Support based on license.

Early access features

Stable: No
Production-ready: No
Support: GitHub issues

Early access features are neither feature-complete nor stable. We do not recommend using early access features in production deployments.

Coder sometimes releases early access features that are available for use, but are disabled by default. You shouldn't use early access features in production because they might cause performance or stability issues. Early access features can be mostly feature-complete, but require further internal testing and remain in the early access stage for at least one month.

Coder may make significant changes or revert features to a feature flag at any time.

If you plan to activate an early access feature, we suggest that you use a staging deployment.

To enable early access features:

Use the Coder CLI --experiments flag to enable early access features:

Enable all early access features:

coder server --experiments=*
Enable multiple early access features:

coder server --experiments=feature1,feature2

You can also use the CODER_EXPERIMENTS environment variable.

You can opt-out of a feature after you've enabled it.

Available early access features

Feature	Description
`minimum-implicit-member`	Allows organizations to deviate from the default organization-member roles, in support of Gateway Accounts.

Beta

Stable: No
Production-ready: Not fully
Support: Documentation, Discord, and GitHub issues

Beta features are open to the public and are tagged with a Beta label.

They’re in active development and subject to minor changes. They might contain minor bugs, but are generally ready for use.

Beta features are often ready for general availability within two-three releases. You should test beta features in staging environments. You can use beta features in production, but should set expectations and inform users that some features may be incomplete.

We keep documentation about beta features up-to-date with the latest information, including planned features, limitations, and workarounds. If you encounter an issue, please contact your Coder account team, reach out on Discord, or create a GitHub issues if there isn't one already. While we will do our best to provide support with beta features, most issues will be escalated to the product team. Beta features are not covered within service-level agreements (SLA).

Most beta features are enabled by default. Beta features are announced through the Coder Changelog, and more information is available in the documentation.

Available beta features

Feature	Description
MCP Server	Connect external AI coding agents to Coder using its built-in Model Context Protocol server.
JetBrains Toolbox	Connect to and manage your Coder workspaces from the JetBrains Toolbox app.
Coder Agents	Delegate development work to coding agents in your deployment with Coder Agents, a chat interface and API.

General Availability (GA)

Stable: Yes
Production-ready: Yes
Support: Yes, based on license.

All features that are not explicitly tagged as Early access or Beta are considered generally available (GA). They have been tested, are stable, and are enabled by default.

If your Coder license includes an SLA, please consult it for an outline of specific expectations.

For support, consult our knowledgeable and growing community on Discord, or create a GitHub issue if one doesn't exist already. Customers with a valid Coder license, can submit a support request or contact your account team.

We intend Coder documentation to be the single source of truth and all features should have some form of complete documentation that outlines how to use or implement a feature. If you discover an error or if you have a suggestion that could improve the documentation, please submit a GitHub issue.

Some GA features can be disabled for air-gapped deployments. Consult the feature's documentation or submit a support ticket for assistance.