Really? This has never worked for me and I stopped using browser functions a long time ago because it wouldn't sign into dev environments stood up specifically for it

▲

laurels-marts 2 hours ago | parent [-]

Wait what. I never used CC but use Codex CLI with 5.5 daily and authenticating has never been an issue. I even rolled skills that instruct it how to retrieve test user credentials for auth purposes.

Today using the devtools I asked it to reverse engineer the login auth flow of another app in our company and it created a nice browser-like headless script (with cookie jars etc) that emulates the entire Auth0 flow with all the internal API calls, redirect loops etc so that given username/password I end up with a valid JWT without having to open an actual browser instance and go through the login steps manually. Zero hesitation or questions asked.

I think this is in-line with OpenAI's philosophy. They see Codex agents as just tools for developer to use. They don’t try to imbibe them with “feelings”, “constitution” or “morality” the way Anthropic does.

▲

ygjb 2 hours ago | parent | next [-]

Yeah Claude does this for me all the time. I have a template project I use that also leverages puppeteer/webdriver/Firefox, and I can point Claude at the template and a website and it will happily build me an MCP service that it can use to interact with the site if there isn't an API or MCP already available.

▲

bakies 2 hours ago | parent | prev [-]

The fucked up part is CC has no problem looking through k8s secrets for credentials and authenticating to services on the command line. It's always been protective of signing in on the web.

	▲	ceejayoz 2 hours ago \| parent [-]
		That seems highly likely to be an anti-spammer measure.