[FEATURE]: Add a /experimental command to allow users to view the current experimental options and dynamically enable/disable them #7392

Closed
opened 2026-02-16 18:07:02 -05:00 by yindo · 2 comments
Owner

Originally created by @KelvinJRosado on GitHub (Jan 23, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

At the moment, the experimental options rely on users enabling them prior to launching OpenCode. However, I think it would be nice to provide a /experimental command. This could list the available experimental options and current status (enabled/disabled).

I imagine this command having 2 benefits:

  • Allow an easy way to view all active experimental options within OpenCode itself (maybe along with a brief description). This allows users to verify which experimental options they are currently using, and what is available.
  • Give users an easy way to enable/disable these experimental options (for the current instance)

For example if a user wants to compare the experimental plan mode to the original plan mode, the current process is several steps. They have to open and close OpenCode to reflect the opt in/out after manually changing a setting. This command would allow a better user experience by allowing simple opt in/out through a single command.

Some additional notes:

  • This would likely just want to change the internal variable, so it wouldn't persist if they close and re-open OpenCode.
  • Not sure if /experimental or /experiments would be a better name
Originally created by @KelvinJRosado on GitHub (Jan 23, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request At the moment, the experimental options rely on users enabling them prior to launching OpenCode. However, I think it would be nice to provide a `/experimental` command. This could list the available experimental options and current status (enabled/disabled). I imagine this command having 2 benefits: * Allow an easy way to view all active experimental options within OpenCode itself (maybe along with a brief description). This allows users to verify which experimental options they are currently using, and what is available. * Give users an easy way to enable/disable these experimental options (for the current instance) For example if a user wants to compare the experimental plan mode to the original plan mode, the current process is several steps. They have to open and close OpenCode to reflect the opt in/out after manually changing a setting. This command would allow a better user experience by allowing simple opt in/out through a single command. Some additional notes: * This would likely just want to change the internal variable, so it wouldn't persist if they close and re-open OpenCode. * Not sure if `/experimental` or `/experiments` would be a better name
yindo added the discussion label 2026-02-16 18:07:02 -05:00
yindo closed this issue 2026-02-16 18:07:02 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 23, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #7717: add "/experimental" command to toggle experimental features

Both issues are requesting essentially the same functionality - a /experimental command to view and toggle experimental features within OpenCode. Feel free to ignore if your request includes additional context or requirements not covered by #7717.

@github-actions[bot] commented on GitHub (Jan 23, 2026): This issue might be a duplicate of existing issues. Please check: - #7717: add "/experimental" command to toggle experimental features Both issues are requesting essentially the same functionality - a /experimental command to view and toggle experimental features within OpenCode. Feel free to ignore if your request includes additional context or requirements not covered by #7717.
Author
Owner

@KelvinJRosado commented on GitHub (Jan 23, 2026):

Didn't see the existing issue. Closing as duplicate

@KelvinJRosado commented on GitHub (Jan 23, 2026): Didn't see the existing issue. Closing as duplicate
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7392