Beta features

Beta features is a single switch in the Desktop app. Flip it on and Speedwave reveals UI surfaces that are still being built, such as meeting transcription; flip it back off and they’re gone from view again. The switch is off by default, and it lives on your user account on this machine, not on a project. A .speedwave.json file checked into a repo cannot turn it on for you.

Turn it on

The toggle lives in the Speedwave tray-icon menu, and it only shows up once initial setup is done. On a fresh install, finish the Setup Wizard first; while setup is running, the item is not there yet.

1. Open the Speedwave menu from the system tray icon.
2. Click Beta features. The check mark next to the item shows whether beta is on.

With beta on, the Desktop app shows a small Beta badge in the bottom-right corner of the window. Click Beta features again to turn it back off.

Edit the config instead

The toggle is the ui.beta_enabled field in your user config at ~/.speedwave/config.json. Set it to true or false directly if you’d rather skip the tray menu. See the configuration reference for the full list of keys.

What beta means for stability

A beta surface is still being built. The same switch currently gates three independent, unrelated parts of the app:

Surface	Where it lives
Meeting transcription	Its own navigation entry, page, and Settings section
Telemetry settings	Settings section for pointing Speedwave at your own OTLP collector
The “office” integration	Hidden from the service list in the Integrations view

Turning beta on or off does not affect the other two. They just happen to share the same gate.

Gating goes further than hiding a menu item. If you open a beta-gated page directly while the toggle is off, Speedwave redirects you back to the chat view instead of loading the page. The page itself refuses to load until beta is on. If a beta feature misbehaves, start with the general troubleshooting guide.

Beta features only controls visibility in the interface. It is not a security control and does not unlock any privileged capability. Anything that needs a real permission check, such as host access, stored credentials, or network policy, keeps its own enforcement whether beta is on or off, as covered in the isolation model.