Oceans of Wisdom

so tl;dr this was my fault it deployed

you can't expect the deployment train to all all the conditionalities of every agent thread someone is working on

of course the FE and BE should go together but the person or AI responsible should be the person doing that feature

and in the meantime someone called me and by the time I got off the phone a deployment happened

and was going to come here and tell everyone to be careful

and then I merged it and deliberately did not deploy because I suspected you had the AUTH v2 FE ready but not the BE

I was semi-irritated at @[prxt0] forgetting that AIs exist so I had the AI autonomously fix all his failing Jest tests

none of this is the AI's fault

I merged and someone else must have deployed (maybe me, on another thread)

i did not deploy!

if you want roll back the deployment

in any case, in good news, I resolved all of your 1,000+ Jest tests

and not just merged?

are you sure it is deployed

ah, i told it not to deploy

i will come back when I have more

lets see how it does and if we can resolve today

in any case @[prxt0] @[simo] i sent off a small swarm to deal with the Jest stuff

Developer mode works with Browser use in Chrome and the Codex in-app browser. It gives Codex controlled access to the Chrome DevTools Protocol (CDP). Use it when you want Codex to profile JavaScript, inspect console output and network traffic, examine page state such as the DOM and applied styles, or diagnose an issue directly in the live browser. To enable it, open Settings > Browser and, under Developer mode, turn on Enable full CDP access. If your organization has disabled this setting, you can’t enable it locally. Admins can set browser_use_full_cdp_access = false under [features] in requirements.toml. Full CDP access lets Codex inspect and control sensitive browser internals that may put your data at risk. Codex asks for explicit approval before it uses full CDP to inspect a website. Review the site, task, and requested access before you approve it. Use @Browser for the in-app browser. To use Developer mode in Chrome, set up the Codex Chrome extension and invoke @Chrome.

https://developers.openai.com/codex/app/browser#developer-mode

also related unrelated this is good

don't see it, not sure why, I feel I remember reading the tweet


just to give a flavor of what I am grinding (ofc they will have to be checked/tested/etc)

we can use this: https://aws.amazon.com/device-farm/

and then for broader testing across different device types

we can do this for development team loop

and there is something similar we can do with android

codex

iirc there is an xcode plugin in codes

i think you can set this up to work natively on your computer/iphone

For mobile you mean?

What do you mean about #2 real access to the app?

Codex and bots are already superhuman

On topics like "can we fix every little stupid thing"

Codex will

You see the team has not mentally yet grokked that nobody is manually going to fix 500 failing jest tests

To do all of this we need rigorous testing framework

None of them are urgent

If this means the PRs wait for a day, it is fine

I am 100% certain if I don't force the issue this way it will not get resolved like it hasn't the last 4 years

I have thought about the consequences just fine

I am not thinking through the consequences

But if I don't merge you ticket in the next 5 minutes

For 1 week it was no problem to delay auth v2

You see i think this is all a bit ironic

I prefer you don't merge anything and we fix this

"i did not fail the test" because "i did not take it"

"turning off the step" is the same thing with nicer bedtime story to yourself?

it is going to be dealt with today