Feature Availability
Vast deliberately distinguishes stable features from opt-in and experimental surfaces.
| Feature | Status | How it becomes available |
|---|---|---|
| Web browsing and navigation | Available | Always |
| Tabs, groups, pinned tabs, split view | Available | Always |
| Workspaces | Available | Always |
| Multiple workspaces | Available | Always |
| Notes / Advanced Notes | Available | Always |
| Bookmarks, History, Downloads, Reading List | Available | Always |
| Session Timeline | Available | Always |
| Advanced import/export | Available | Always |
| Extensions | Available | Open Extensions |
| Video & Audio | Labs | Enable Vast Labs, then Video & Audio |
| Network Devices | Labs | Enable Vast Labs, then Network Devices |
| Automation | Labs | Enable Vast Labs, then Automation |
| Password Manager | Labs | Enable Vast Labs, then Password Manager |
| Advanced Diagnostics | Labs | Enable Vast Labs, then Advanced Diagnostics |
| Spoofing tools | Labs | Enable Vast Labs, then Spoofing |
| Purist layout | Experimental | Enable Experimental features |
| Deeper developer actions | Developer | Enable Developer Mode |
| Experimental themes | Coming soon | Not active in the current build |
What a Labs switch means
Section titled “What a Labs switch means”The master Enable Vast Labs switch reveals the Labs section. A feature still needs its own local switch before it becomes usable.
Turning a feature off hides and blocks it but does not automatically erase its local data.
Why Vast does this
Section titled “Why Vast does this”Experimental controls often have a narrower compatibility envelope, more complex local dependencies, or a higher support burden than normal browsing. Explicit gating prevents a fresh profile from feeling like a development console and makes feature status visible instead of implicit.