Cmd. /experimental
Toggle experimental Codex features from the TUI.
Key takeaways
- Toggle experimental Codex features from the TUI.
- Check the input surface and availability before using the examples below.
Purpose
Toggle experimental Codex features from the TUI.
/experimentalAvailability
| Field | Value |
|---|---|
| Input surface | Running CLI prompt |
| Kind | Built-in |
| Status | Current reference |
| Aliases | — |
| Documented minimum | Not specified |
| Reviewed against | 2026-09-22 · Codex CLI 0.155.1 |
The installed command menu and account or organization settings determine availability.
Examples
/experimentalWhen to use it
- Enable experimental voice conversations on a supported build before trying
/voice. - Inspect experimental toggles during onboarding so team docs match actual feature flags.
Choosing related commands
| Command | Difference | Choose It When |
|---|---|---|
/experimental | Toggles optional features | You need to enable or inspect feature gates |
/debug-config | Shows config layers | You need to understand why a flag is active |
/status | Shows session state | You need runtime confirmation |
Effects and persistence
Lets you select experimental features offered by the installed build. Follow its activation and restart instructions.
/experimental opens controls for optional Codex features. Some changes may require a restart.
Voice conversations in 0.155.0
On supported builds, enable voice conversations through /experimental, then run /voice. This remains experimental and build-dependent.
Cautions
- Treat experimental toggles as version-sensitive.
- Do not put experimental behavior into team standards without a version and rollback note.
Official sources
Complete command list · Verification scope · History for this command