Skip to content

chore(experiments): add registry of existing experiments - #30919

Open
ibetitsmike wants to merge 1 commit into
mainfrom
mike/experiments-registry
Open

ibetitsmike wants to merge 1 commit into
mainfrom
mike/experiments-registry

Conversation

@ibetitsmike

Copy link
Copy Markdown
Collaborator

Adds experiments/registry.yaml, an inventory of every experiment on main today. Nothing reads it yet. It is the first piece of the experiment promotion gate: a later PR adds a lint check that keeps it in sync with the code and enforces the stage rules.

The scan covered every marker the repo uses: the 17 flags in codersdk.ExperimentsKnown, the x/ directories, exp_ files, /api/experimental routes, docs/manifest stage labels, and the frontend experiments.includes(...) gates. Each entry records the stage, the date it entered that stage, the flag, the paths it owns, its experimental routes and its docs page. A tools section lists exp_ files that are dev tools, not features (scale tests, debug commands).

27 entries: 17 flagged experiments, 10 unflagged ones. Stage comes from the docs label. A feature behind a hidden flag with no label is early access.

Drift the scan found, recorded in each entry's notes:

  • Coder Agents and agent skills are GA, but their code is still under x/ and some routes are still under /api/experimental.
  • mcp-server-http: the docs label the page beta, but the endpoint needs a hidden flag.
  • notifications: nothing reads the flag since chore: remove notifications experiment #14869, but it is still a known experiment.
  • chat-virtual-desktop: the desktop stream route and the agent desktop API are not gated by the flag.
  • Virtual desktop and debug-logging docs name /api/v2 routes that do not exist.
  • startup-coordination and external-workspaces are early access by docs label only. No flag gates them.

Left out: JetBrains Toolbox (labelled beta, but no gate or experimental code) and the removed agents and chat-automations flags. No owner field yet, since there is no team mapping to fill it.

Testing

A local script (not committed) checked that every path glob matches at least one tracked file, every docs page exists, the flags match ExperimentsKnown exactly, and every x/ and exp_ file belongs to an entry or a tool. Six routes are missing from swagger; each was confirmed in the router.

Xum acted for @ibetitsmike to open this PR.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 18, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-18T10:11:25.165856Z 82bf2fe PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant