Beta features

Beta features in Speedwave are controlled through a single global switch in the Desktop application. Enabling it reveals interface components and settings currently under active development, such as meeting transcription. Disabling the switch hides these features from view. The toggle is disabled by default and applies to your user profile on the local system rather than to individual projects. Consequently, a repository .speedwave.json file cannot enable it automatically.

Enabling beta features

The beta switch is located in the Speedwave system tray menu and becomes accessible after completing the initial application setup wizard.

1. Open the Speedwave menu from the system tray icon.
2. Select Beta features. A checkmark indicates when beta mode is active.

When beta features are enabled, the Desktop application displays a Beta badge in the lower-right corner of the window. Selecting Beta features again turns the mode off.

Direct configuration file editing

The toggle corresponds to the ui.beta_enabled property in your user configuration file at ~/.speedwave/config.json. You can set this value directly to true or false. For all available configuration parameters, see the Configuration keys reference.

Scope and stability of beta features

Beta features are in active development. The single beta switch governs access to four independent areas of the application:

Feature	Location
Meeting transcription	Navigation tab, dedicated view, and Settings section
Telemetry configuration	Settings section for directing OTLP exports to custom collectors
Security policies	Settings section for selecting PII tokenization templates
Office integration	Service list within the Integrations panel

Toggling beta features affects all four areas simultaneously.

Access gating extends beyond hiding navigation links: navigating directly to a beta-gated URL while the switch is disabled redirects you to the default chat view. If you encounter unexpected behavior with an experimental feature, refer to the Troubleshooting guide.

For most features, the beta switch controls only interface visibility. Security boundaries (such as host resource access, stored credentials, and network isolation) remain strictly enforced regardless of the beta setting, as detailed in the Isolation model. The exception is PII tokenization: tokenization enforcement is active when beta features are enabled or when mandatory policies are configured via MDM. Without an organization MDM profile, disabling beta features turns off tokenization enforcement as well as the Security settings panel.