Chloé Bakalar left OpenAI in July, about eleven months after joining from Meta, where she had been chief ethicist since 2019. The Financial Times reported it this week, and by that account she was the company's only dedicated ethicist, with no replacement named.

OpenAI's response is the part worth keeping. Asked to confirm there is now no ethicist on staff, a spokesperson said AI ethics "doesn't live with one owner or team" and that ethical considerations are "deeply embedded into the model building process driven by a number of teams across research." As a principle that's fine, and probably right; a lab where ethics is one person's job has already lost. As a description of who actually does what, it can't be audited from outside. The principle also arrived only once the owner had gone, and the job itself was created in August 2025.

The exodus framing built up around this deserves less confidence than it's getting. The FT piece is single-sourced, neither Bakalar nor the company has given a reason, and her LinkedIn still lists the role, so even the shape of the exit is thinner than the coverage around it. Reading a departure as a warning shot, when nobody involved has said anything, produces a story that writes itself and then gets cited as though someone reported it.

What needs no motive is the shape of the org. Superalignment stopped existing as a standalone team in 2024, Mission Alignment was disbanded earlier this year, and its former head Josh Achiam left in July, the same week as Safety Systems head Johannes Heidecke. Each of those sat outside the teams shipping the models. Chief Research Officer Mark Chen told Wired the goal now is safety work integrated with frontier-model development, earlier and closer to launch decisions.

That might genuinely be the better design, and the distinction worth holding onto is between responsibility and authority. Spreading responsibility across every team is good practice. Authority to stop a launch is a different thing, and it has to sit somewhere a deadline can't reach it. The behaviour that needs catching is rarely the behaviour anyone asked for, which is why whoever raises it needs a job that survives the raising. A reviewer inside the build shares the shipping deadline; a dedicated one doesn't, and that's most of the point of having one.

Sources: