anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-21 17:56:33 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: Allow per-experiment opt-out when OPENCODE_EXPERIMENTAL=true #8886

New Issue
Open
opened 2026-02-16 18:11:06 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:11:06 -05:00
Owner
Copy Link
Copy Source

Originally created by @oomathias on GitHub (Feb 9, 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

Problem

OPENCODE_EXPERIMENTAL=true currently enables all experimental features, but there’s no way to explicitly disable a single experimental feature while keeping the others enabled.

Requested behavior

Allow per-feature opt-out to take priority over the global flag.

Example (current behavior)

OPENCODE_EXPERIMENTAL=true OPENCODE_EXPERIMENTAL_PLAN_MODE=0
# still enables plan mode (because the global flag wins)

Example (desired behavior)

OPENCODE_EXPERIMENTAL=true OPENCODE_EXPERIMENTAL_PLAN_MODE=0
# plan mode disabled
Originally created by @oomathias on GitHub (Feb 9, 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 #### Problem `OPENCODE_EXPERIMENTAL=true` currently enables all experimental features, but there’s no way to explicitly disable a single experimental feature while keeping the others enabled. #### Requested behavior Allow per-feature opt-out to take priority over the global flag. #### Example (current behavior) ```sh OPENCODE_EXPERIMENTAL=true OPENCODE_EXPERIMENTAL_PLAN_MODE=0 # still enables plan mode (because the global flag wins) ``` #### Example (desired behavior) ```sh OPENCODE_EXPERIMENTAL=true OPENCODE_EXPERIMENTAL_PLAN_MODE=0 # plan mode disabled ```
yindo added the discussion label 2026-02-16 18:11:06 -05:00
yindo commented 2026-02-16 18:11:06 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 9, 2026):

This issue might be a duplicate or related to existing issues. Please check:

  • #7717: Requests a /experimental command to toggle experimental features dynamically
  • #10313: Similar feature request to view and manage experimental options dynamically
  • #5397: Broader request to expose set flags using configuration, making experimental features configurable
  • #7399: Related pattern - selective tool/feature loading with include/exclude controls
  • #9203: Related pattern - support for disabling specific features via config
  • #10021: Related - env flag to selectively disable global config while using project config
  • #10025: Related - env flag to prevent inheriting configs from parent directories

The core issue here (selective per-feature opt-out of experimental flags) aligns with broader discussions around granular feature control and configuration. #7717/#10313 may provide an alternative solution path through a /experimental command.

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Feb 9, 2026): This issue might be a duplicate or related to existing issues. Please check: - #7717: Requests a /experimental command to toggle experimental features dynamically - #10313: Similar feature request to view and manage experimental options dynamically - #5397: Broader request to expose set flags using configuration, making experimental features configurable - #7399: Related pattern - selective tool/feature loading with include/exclude controls - #9203: Related pattern - support for disabling specific features via config - #10021: Related - env flag to selectively disable global config while using project config - #10025: Related - env flag to prevent inheriting configs from parent directories The core issue here (selective per-feature opt-out of experimental flags) aligns with broader discussions around granular feature control and configuration. #7717/#10313 may provide an alternative solution path through a /experimental command. Feel free to ignore if none of these address your specific case.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8886
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?