SigmaOS markets itself as "the first browser specifically made for work" and targets "students managing courses" and "founders building startups." Yet it fundamentally fails at the most basic institutional workflow: SSO redirect authentication. Without this fundamental and game-breaking failure, it would easily be a 5 star browser and I would have no complaints.
Every university library system (Ex Libris, OCLC), corporate SSO (Okta, SAML), government portal, and B2B platform uses redirect-based authentication. You save the redirect URL, click it, authenticate, and access your tools. This is Web 101 for institutional users.
SigmaOS removed traditional bookmarks without understanding what bookmarks actually do - they're deferred execution triggers for authentication flows. Their "locked pages" system requires visiting a URL first, but redirect URLs auto-forward immediately, making it impossible to save the trigger URL.
The "Edit locked URL" feature is broken - when you try to reset to your saved redirect, it errors out when trying to load the redirect URL instead of executing the authentication flow. Meanwhile, Arc handles this perfectly with persistent saved tabs with editable URLs, and Chrome, Safari and Firefox handle it perfectly with bookmarks. (But all of these other browsers fail for my workflow for other reasons.)
How can you charge a monthly subscription for a "work browser" that can't access the tools people actually use for work? Either fix redirect URL handling, or stop marketing as a "work browser" to institutional users.
What needs improvement
poor SSO redirect handling (1)
Report
7 views