--version 2.20.0

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.

Use the [Coder CLI](../../install/cli.md) `--experiments` flag to enable early access features:

```shell

coder server --experiments=*

```

```shell

coder server --experiments=feature1,feature2

```

You can also use the `CODER_EXPERIMENTS` [environment variable](../../admin/setup/index.md).

Currently no experimental features are available in the latest mainline or stable release.

- **Support**: Documentation, [Discord](https://discord.gg/coder), and [GitHub issues](https://github.com/coder/coder/issues)

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](https://coder.com/contact), reach out on [Discord](https://discord.gg/coder), or create a [GitHub issues](https://github.com/coder/coder/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](https://coder.com/changelog), and more information is available in the documentation.

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](https://discord.gg/coder), or create a [GitHub issue](https://github.com/coder/coder/issues) if one doesn't exist already.

Customers with a valid Coder license, can submit a support request or contact your [account team](https://coder.com/contact).

We intend [Coder documentation](../../README.md) to be the [single source of truth](https://en.wikipedia.org/wiki/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](https://github.com/coder/internal/issues/new?title=request%28docs%29%3A+request+title+here&labels=["customer-feedback","docs"]&body=please+enter+your+request+here).

Some GA features can be disabled for air-gapped deployments.

Consult the feature's documentation or submit a support ticket for assistance.

# https://gist.github.com/lukechilds/a83e1d7127b78fef38c2914c4ececc3c#gistcomment-2758860

# Fetch the releases from the GitHub API, sort by version number,

# and take the first result. Note that we're sorting by space-

# separated numbers and without utilizing the sort -V flag for the

# best compatibility.

# Go doc doesn't include inline array comments, so this parsing should be

# good enough. We remove all whitespaces so that we can extract a plain

# string that looks like {}, {ExpA}, or {ExpA,ExpB,}.

#

# Example: ExperimentsAll=Experiments{ExperimentNotifications,ExperimentAutoFillParameters,}

go doc -all -C "${dir}" ./codersdk ExperimentsAll |

grep -E -o 'ExperimentsAll=Experiments\{[^}]*\}' |

# Extracts the experiment name and description from the Go doc output.

# The output is in the format:

#

# ||Add new experiments here!

# ExperimentExample|example|This isn't used for anything.

# ExperimentAutoFillParameters|auto-fill-parameters|This should not be taken out of experiments until we have redesigned the feature.

# ExperimentMultiOrganization|multi-organization|Requires organization context for interactions, default org is assumed.

# ExperimentCustomRoles|custom-roles|Allows creating runtime custom roles.

# ExperimentNotifications|notifications|Sends notifications via SMTP and webhooks following certain events.

# ExperimentWorkspaceUsage|workspace-usage|Enables the new workspace usage tracking.

# ||ExperimentTest is an experiment with

# ||a preceding multi line comment!?

# ExperimentTest|test|

#

# Track preceding/multiline comments.

# Missing var/key, this is a comment or description.

# If desc (trailing comment) is empty, use the preceding/multiline comment.

# Skip experiments not listed in ExperimentsAll.

log "Skipping ${var}, not listed in ExperimentsAll"

# Don't overwrite desc, prefer first come, first served (i.e. mainline > stable).

# Track the release channels where the experiment is available.