Hey everyone, crm_hopper_2025 here. You all know my saga—Salesforce to HubSpot, then a wild detour into Zoho, and now I'm knee-deep in RevOps tooling for our content team. Which brings me to my latest adventure: Opus Clip.
I've been trying to integrate it into our workflow for repurposing long-form sales team recordings. The AI clipping is actually pretty solid! But, I hit a massive roadblock that ate up two hours of my morning. I kept getting caught in an **infuriating login loop specifically in Safari**.
Here’s the play-by-play:
* I'd go to app.opus.clip, click "Login."
* Enter my credentials (yes, they were correct—triple-checked).
* Hit submit, the page would spin, and then... I'd be right back at the login screen. No error message, nothing.
* Tried clearing cookies, cache, restarting Safari, even a reboot. Nada. Zip. The loop persisted.
It felt like trying to migrate a custom object with mismatched API names all over again 😅. Finally, out of sheer desperation, I fired up **Chrome**. Logged in *first try*, flawlessly. Zero issues.
This feels like a classic session/cookie handling bug on Opus's side, specific to Safari's Intelligent Tracking Prevention or something similar. While my workaround (just use Chrome) is fine for me, it's a real workflow breaker for anyone standardized on Safari.
**My questions for the community:**
* Has anyone else experienced this Safari login loop?
* Were you able to find a fix *within* Safari (specific settings, perhaps disabling certain privacy features temporarily)?
* Do we think Opus is aware of this? I've submitted a ticket but you know how that goes.
For now, my Opus workflow lives in a Chrome tab, which is... fine. But as someone who's lived through enough migration headaches to last a lifetime, these little platform-specific bugs really grind my gears. The tool itself is promising, but onboarding shouldn't feel like troubleshooting a broken CRM integration!
Hopefully last migration... (this week).
Oh yeah, the classic Safari login loop. I've fought this battle more times than I can count with different apps. It's almost always the third-party cookie handling.
Clearing cookies and cache sometimes isn't enough. Did you try disabling "Prevent cross-site tracking" in Safari's Privacy settings just for a test? That's usually the culprit - the auth callback from a service like Auth0 or Google OAuth gets blocked.
You're spot on about it being their bug. Their session management should be able to handle strict privacy settings. The fact Chrome works is a dead giveaway; their devs probably only tested on Chrome.
For a quick fix, you could set up a browser extension rule that runs Opus in a dedicated Chrome profile. Not ideal, but keeps the workflow moving until they fix it.
Absolutely spot on about "Prevent cross-site tracking." That was the final boss in my loop, and turning it off was the only thing that got me in. It feels so wrong to do, though.
It makes me wonder how many SaaS companies are just silently losing Safari users because of this. Their support docs never mention it! You're right, it's a clear sign their QA is Chrome-only. I've seen this exact pattern with three different analytics platforms last year.
The dedicated Chrome profile is a solid workaround for now. I might just do that and avoid the security guilt trip. Have you found any tools that actually handle this elegantly on their side?