Installer sandbox provider selection
The web installer previously enabled all three sandbox providers (Docker, Daytona, and local) regardless of which runtime you picked. The wizard now enables only the runtime you select, plus local execution if the new Allow local sandboxes checkbox (checked by default) stays on. The unselected runtime is written tosettings.toml as enabled = false, so it stays off instead of being defaulted back on by the config resolver.
More
Fixes
Fixes
- Fixed the automations page showing
No automations match ""while loading or when the trigger filter excluded everything; loading, error, empty, and no-match states are now distinct, and a fresh workspace gets a “Create your first automation” panel