Feature switches
Use Labs to control optional feature visibility and activation. A switch does not install dependencies, configure accounts, or authorize actions.
Find available switches
Open Settings > Labs. Groups show controls available for the build, enabled modules, and organization policy. Internal development switches are not part of the public feature list.
| State | Meaning and action |
|---|---|
| Editable | Read the description, change the value, and wait for save results |
| Organization or managed-policy lock | Read the lock notice; personal settings cannot override it |
| Module unavailable | Changing a switch cannot enable an unavailable module |
| Runtime restricted by policy | A saved choice and runtime permission are separate; an enabled switch does not prove the task can run |
Choose switches by purpose rather than enabling everything. Public feature rows include:
| Item | Effect | Application and verification |
|---|---|---|
| Computer Use | Operates supported Windows or macOS apps | Complete system authorization; switching it off requests that active screen operations stop; browser automation continues |
| Plugins, self-evolution records, memory, swarm network | Shows the corresponding surfaces | Check each entry; displaying swarm does not consent to data sharing |
| Coding helper-view tabs | Shows auxiliary tabs in the coding area | Check the tabs; this does not edit project files |
| Browser tools | Opens pages and provides reading and interaction tools | Configure browser identity and site permissions separately |
| Feishu / Lark knowledge sources | Provides the knowledge-source entry | Configure the connection and reading scope |
| Context management | Shows the composition of each model request’s context | Inspect system instructions, project files, tools, and message sources |
| Messaging contacts and groups | Provides contacts, groups, and @ selection in message input | Check the channel connection too |
| Egress control | Provides outbound-policy settings in Advanced | Backend restart required; enforcement also requires an enabled or administrator-configured policy |
| Scheduled tasks | Runs tasks on a schedule | Backend restart required; check schedules and runtime permission |
| Daily AutoResearch | Seeds swarm evolution with daily research | Backend restart required; automatic-run policy still applies |
| Frequent experience consultation | Fetches task-related experience more frequently | Backend restart required; increases network requests |
| Long-conversation memory-saving mode | Reduces memory use for long conversations | Check reading and scrolling in a long conversation |
| Quick bug reporting | Sends a report with Cmd/Ctrl + Shift + B | Includes a screenshot and recent logs; review before sending |
| Session diagnostic logs | Records full model and tool inputs and outputs | Increases session-file size and stores task content; enable for a diagnostic need |
Feature visibility, runtime capability, and diagnostic recording are different effects. Module availability, organization locks, and runtime policies still apply. Internal-only features are not listed as public configuration options.
Change and verify
- Record the original value and read the effect and scope.
- Change one switch and wait for saving.
- Reopen the panel to check the persisted value, then inspect the feature entry or behavior.
- If a restart is requested, save work and use the supplied background-restart action.
- Wait for backend readiness and verify a small task.
Not every switch requires a restart. Restart-dependent features adopt settings in a new background process; a changed control alone does not prove runtime adoption.
Save failures and rollback
A failed save restores the previous value and shows an error. Resolve the error before retrying; a temporary toggled state is not a saved result.
Turn the original switch off when no longer needed, follow any restart instruction, and verify visibility and runtime behavior. Hiding an entry does not delete data, stop every task, or revoke external account authorization.
If restart fails, inspect the error and retry action. See Network and background operation for service checks and Permissions and approvals for task authorization.