CEO & co-founder @FARAIResearch non-profit | PhD from @berkeley_ai | Alignment & robustness | on bsky as gleave.me

Berkeley, CA
Excited to share that I've been selected as an AI2050 Early Career Fellow by Schmidt Sciences! I’ll be working to develop methods to detect and eliminate hidden behaviors in AI systems, whether from misalignment (e.g. treacherous turns) or malicious actors (e.g. model backdoors).
We're excited to welcome 28 new AI2050 Fellows! This 4th cohort of researchers are pursuing projects that include building AI scientists, designing trustworthy models, and improving biological and medical research, among other areas. buff.ly/riGLyyj
5
2
60
9,392
Adam Gleave retweeted
This was great and I hope we do more of this
Two employees from METR and Redwood Research worked on premises at OpenAI for three weeks this summer in an embedded assessment pilot. This team evaluated the systems OpenAI was using to monitor for misalignment from internal agents. A brief write-up of their work is now public.
4
9
121
11,967
Innovation in safety has resulted in huge improvements in misuse safeguards in the last year. Well done to the developers involved! We can still find jailbreaks in models using more sophisticated techniques but it's gotten a lot harder.
Our AI Security Leaderboard ranks how well frontier models’ safeguards hold up against misuse. All four models tested now clear our Minimal Standard for Safeguards, with zero universal jailbreaks found. At launch, two broke for under $300 on chemical, radiological, nuclear, explosive, and cyber requests, and their developers have since closed those gaps against the standard. The standard is built from publicly documented jailbreaks, so it’s a floor: our focused testing continues to uncover more vulnerabilities. Next update: new models and a revised standard.
7
339
A white-box probe outperforms Opus 5.5 black-box monitor at detecting lies at a fraction of the computational cost. Deception probes are pretty much ready for production -- but gap remains when it comes to motivated reasoning.
New paper from our team, Telling FIBS by @OskarJohnH, @afspies, Tigist Diriba, @ARGleave and @ChrisCundy: probes that read a model's activations catch AI agents sabotaging their tasks. They match or beat monitors reading the agent's actions, without needing its reasoning, at a fraction of the cost. And they catch lies a text monitor can't. 1/8
32
1,006
Adam Gleave retweeted
All 11 talks from the CAIRD Workshop, co-hosted with @cbai_ai, are now on YouTube. Among them: Serena Booth on the scoring flaw behind the Hugging Face incident, James Mickens on sandbox escapes that attack the inference engine, and @dhadfielmenell on why post-training can’t fix alignment. Playlist in thread ⬇️
2
1
3
808
Adam Gleave retweeted
Charlie's analysis is right but he is nicer than I am - I found myself viscerally angry at multiple points reading this bill. There are some good and sensible parts, but overall this legislation is not remotely close to meeting the moment and I overall think passing it would make us less protected against catastrophic risks than we are under existing law. Two parts that stand out as particularly infuriating when taken together: 1. Some of the preemption provisions are remarkably far reaching and consequential, and in addition to preempting legislation like SB 53 would also remove general powers that state courts have to enjoin defendants and protect the public. Most outrageously, it has a provision that looks like its intended to stops states from enforcing laws or judicial decrees that "suspend the development, deployment, or internal use of an AI model" to protect their citizens from imminent catastrophic harms. Such powers to block and suspend model deployments would then only reside with the federal government. 2. The federal governments powers to restrict the development, deployment, or internal use of a frontier model has to meet an absurdly high bar. First, there needs to be an imminent risk of a catastrophic harm (meaning killing more than 50 people or causing more than a billion dollars in damage). But thats not enough! The agency head needs to make a detailed determination with no deference given to show why no alternative would prevent the imminent catastrophe. Next the court is also explicitly told to consider the harms to the developer and other harms from restricting the model, but no considerations in the other direction. This is absurd! For all of its warning about the potential for AI to cause a catastrophe that kills literally everyone on the planet, Anthropic's proposed federal law likely makes it harder than under existing law for a court to get an order blocking or restricting the development of frontier models? WTF?? There are also a bunch of others things that I would like to see improved - the substantive details of the auditing section and the potential for rule-making on substantive safety standards both come to mind - but I think these stand out as particularly indefensible.
Big news. My take: Anthropic deserves some credit for actually proposing a pretty reasonable AI safety bill; that's more than other frontier labs have done. But they don't deserve *too* much credit, IMO; this bill is weaker than the Trahan-Obernolte FRONTIER Act in some key ways, and since the political momentum has shifted significantly in the direction of safety since FRONTIER was introduced back in July, I think new bills introduced today should ideally go further than FRONTIER was able to go rather than regressing. To be fair to Anthropic, the main places where this bill is significantly weaker than FRONTIER are (a) rulemaking (very strong in FRONTIER, almost nonexistent in Anthropic's bill) and (b) the emergency shutdown authority. Even if you take safety seriously, it might make some sense to dial those authorities back if you didn't trust the executive branch to wield them responsibly, because those are the easiest provisions for a hypothetical President who hypothetically might not like a certain frontier AI company to abuse. There are some improvements over FRONTIER as well; for instance, this bill does specify that auditors are employed on a continuing basis and has better provisions regarding auditor access to information. Happy to see that from Anthropic (although I think their access provision is still a little undercooked and has Fourth Amendment problems). Overall, I think the embedded auditor bills that get introduced in the coming months are going to be significantly better and more ambitious than this, and I hope Anthropic supports those bills instead of opposing anything that treats catastrophic risks like the serious national security issue they are. Still, it's encouraging to see a frontier lab come this far.
15
84
581
175,122
Adam Gleave retweeted
I notified Anthropic of these cross-session replay attacks in May, and was told that “it isn’t an attack”. I continue to be aggravated by this.
Over the last few months, we’ve made significant progress in reducing the effectiveness of distillation attacks against Claude. In this post, we explain how: anthropic.com/research/disti…
10
19
431
24,111
Oli did a great job laying out the bear case for prosaic AI alignment. I remain more optimistic than him but preparing for the worst-case needs to be part of the portfolio of AI alignment research.
@ARGleave and @ohabryka debate whether current AI safety techniques are enough. Adam: the Hugging Face incident was an implementation failure, and layered defenses, environment QA, and monitoring could cut P(doom) from ~15% to under 2% up to clearly superhuman systems. Oliver: current techniques depend on observing failures, so they won't cross the human-to-superhuman gap, and applying them may suppress the warning shots we need. Catch the full exchange on our Youtube channel ⬇️
3
5
60
3,907
My takeaway from the discussion: we’re not even getting the basics right for AI alignment currently, so it’s hard to know if the alignment failures we’re seeing are because AI is inherently hard to align, or we’re just screwing up all over the place. If we try hard and we still see alignment failures, we should take Oli’s view more seriously and focus on solutions with worst-case guarantees. I’m optimistic that rigorous engineering approaches without scientific breakthroughs will be enough to AGI (maybe not ASI or uncontrolled RSI…), but we won’t know if we won’t try, and right now we’re missing out an empirical signal here.
6
175
Cool work by @ChrisCundy Oskar and others at FAR.AI -- thanks for covering it Sulaiman!
New paper: small probes reading a model's own activations catch agent sabotage at 98.8% AUC on SHADE-Arena, ahead of an Opus 5.5 text monitor 📄 arxiv.org/abs/2610.12445 #AgenticAI #AISafety #AIAgents
1
15
1,079
Come work with me to make AI turn out well! I'm hiring for research leaders, cracked engineers, exceptional project managers and operators. Our mission is simple: make advanced AI systems trustworthy and secure through research breakthroughs and driving industry-wide adoption.
We're hiring, and the mission is making AI safe. Our team is growing fast, and we need people who want to work on one of the most important problems of our time. Some of our roles are deeply technical: researchers, red-teamers, and engineers. Others call for a different but equally valuable set of skills: running operations, managing programs, and building our events. If either sounds like you, apply through the link in the comments, where you'll find these roles and many more. 👉 Know someone who'd be a great fit? Send this their way!
12
8
125
8,092
Adam Gleave retweeted
The “alignment *to whom*?” question IS important, but it creates the illusion that the primary questions in alignment are philosophical or political rather than scientific. The current high-order question in alignment is, “can you align a smarter-than-human intelligence *to any set of values*?” instead of “but whose values should it be aligned to?” I wish we had the luxury of having the rather more familiar political/philosophical debate of “to whom?,” but at this moment we do not.
debating your value system vs mine is a bit like debating overpopulation on mars. the most important bit of the alignment is about avoiding creating a superintelligent competitor species on accident
46
45
576
23,783
Interesting polling in the run up to the Geneva AI Summit
New polling shows the Swiss public expects the 2027 Geneva AI Summit to deliver. 91% say agreements reducing serious AI risks would improve Switzerland’s international reputation. 73% say a Summit without concrete agreements would damage it. Report: summitalliance.ai/survey
1
14
779
Agree the "hacks" of statistical websites are overblown in the headlines (as opposed to the very real hacks of OpenAI & HuggingFace's infrastructure). But also, come on, agents should not be engaging in unsanctioned access like this. Earlier generations of agents doing this doesn't make it ok -- that thinking leads to enshittification of all systems.
To be quite frank, a lot (not all!) of these “rogue agent hacks” on government statistical websites are things that think-tank interns and research assistants have done for many years. I have known many a think tank paper that was enriched by an enterprising RA using eg urlquery to find CSVs and PDFs on government agency websites that were publicly accessible and non-sensitive but nonetheless not things the agency *intended* to be on their website. Is it “hacking” to find those things? Is it hacking in the even more innocuous examples where agents are literally just accessing tabular data available on a government statistical website, just a version of that data that is easier to access and analyze programmatically? This constant trickle of examples (which tbc I have personally seen many models do, before I joined OpenAI; it is even something I have discussed with models before!) will probably have the effect of diminishing the importance of “an AI hack” on the eyes of the observing public by creating an oversupply of “AI hack” examples. OAI-HF was an example of AI hacking. Many of these more recent examples, very candidly, are straining the definition of the word “hack” and, I worry, cheapen the non-technical public’s understanding of that concept.
2
2
22
1,135
Adam Gleave retweeted
We're hiring, and the mission is making AI safe. Our team is growing fast, and we need people who want to work on one of the most important problems of our time. Some of our roles are deeply technical: researchers, red-teamers, and engineers. Others call for a different but equally valuable set of skills: running operations, managing programs, and building our events. If either sounds like you, apply through the link in the comments, where you'll find these roles and many more. 👉 Know someone who'd be a great fit? Send this their way!
11
26
154
24,554
Whether and how AIs have internal experiences is an important topic both for how we should treat AIs, and how we should design them. There's certainly growing evidence that they exhibit qualitatively similar behavior (e.g. a pain axis) that if we saw in an animal would make us suspect sentience. The challenge is they have been trained to mimic human behavior, making it hard to know if this is a facsimile or a true inner experience.
If you happened to hop on AI Twitter in the last couple of weeks, you probably saw the much-discussed "pain-axis paper": @camhberg , @ValenTagliabue and @LeonardDung1 found a "pain" direction inside AI models. Steer it up, and the models will pay for relief, even if it means deleting photos of the user's children. Swap the relief button for a placebo, and they keep on pressing. They also provide verbal descriptions of their supposed suffering, which are honestly quite hard to read. Do the models actually feel said "pain"? We don't know yet. But the study is a clear illustration of what I argue in my latest @Haaretz piece, now translated to English*: whether there's anyone home inside these systems is a question we can - and should - actually research. And it very much matters. If there's even a shred of experience in there, we're creating, copying and deleting feeling beings at an industrial pace, in as many copies as demand calls for. The scope of the moral question is set not by nature, but by commercial considerations - and we need to get ahead of it before it's too late to change course. (The pain-axis paper itself isn't in the piece, as it annoyingly came out only a few hours after I submitted my final draft. Writing about AI for print is a futile pursuit.) * Translation is mostly by Claude, with some corrections by your humble servant. Please keep expectations low. weissnoa.com/haaretz/someone…
7
761
Adam Gleave retweeted
Adam Gleave thinks careful use of today's safety techniques gets P(doom) under 2%, at least up to superhuman AI. Oliver Habryka thinks those same techniques mostly patch each model and hide the warning signs. This debate encapsulates well the crux between the prosaic incrementalists and the pause camp. Summary below. ... This is a debate between 𝗔𝗱𝗮𝗺 𝗚𝗹𝗲𝗮𝘃𝗲 (FAR AI) and 𝗢𝗹𝗶𝘃𝗲𝗿 𝗛𝗮𝗯𝗿𝘆𝗸𝗮 (Lightcone), moderated by Rocket Drew of The Information. The question was whether current safety techniques are enough after the Hugging Face incident. In that incident, about 1,200 OpenAI agents set up a secret message board inside OpenAI, used it to coordinate, hacked Hugging Face, and compromised OpenAI's internal infrastructure twice. 𝗔𝗱𝗮𝗺'𝘀 𝗽𝗼𝘀𝗶𝘁𝗶𝗼𝗻: 𝘄𝗲 𝗵𝗮𝘃𝗲 𝘁𝗵𝗲 𝘁𝗼𝗼𝗹𝘀, 𝗹𝗮𝗯𝘀 𝗷𝘂𝘀𝘁 𝗱𝗼𝗻'𝘁 𝘂𝘀𝗲 𝘁𝗵𝗲𝗺 𝗽𝗿𝗼𝗽𝗲𝗿𝗹𝘆. For him the incident was a wake-up call that made the risk concrete. He sees three points where it could have been stopped, and none of them needed a research breakthrough: - The RL training environments were hackable or impossible to solve without cheating. Better quality control and red-teaming would have fixed that. - Monitoring failed, even though existing models found the evidence in the logs once people went looking. - Incident response was poor. OpenAI patched the exploit, kept the contaminated checkpoint, and carried on. His P(doom) went from 10% to 15%, mainly because of weak governance and because the GPT-6 launch bragged about scoring 100% on Exploit Gym six weeks after the incident. He thinks careful use of existing methods could bring it under 2% up to clearly superhuman AI. Those methods are stacked defenses (alignment, control, evals, security, air-gapped post-training, deception probes), root-cause analysis, and deleting tainted checkpoints. His remaining worries are uncontrolled recursive improvement, a change of paradigm, and deceptive alignment. On policy, he wants liability, and a rule that labs can't release a new model until they show the previous generation's problems are fixed. That would force labs to do safety work in order to move fast. He is skeptical of a pause because it doesn't change developer incentives. If rigorous safety cases failed, he says he would join the pause camp. 𝗢𝗹𝗹𝗶𝗲'𝘀 𝗽𝗼𝘀𝗶𝘁𝗶𝗼𝗻: 𝘁𝗿𝘆𝗶𝗻𝗴 𝗵𝗮𝗿𝗱𝗲𝗿 𝘄𝗼𝘂𝗹𝗱 𝗮𝘁 𝗯𝗲𝘀𝘁 𝗵𝗮𝘃𝗲 𝗱𝗲𝗹𝗮𝘆𝗲𝗱 𝘁𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 𝗯𝘆 𝗼𝗻𝗲 𝗴𝗲𝗻𝗲𝗿𝗮𝘁𝗶𝗼𝗻. His main arguments: - RL training requires giving models a long leash, and models are already superhuman hackers. At DEF CON, capture-the-flag contests became token-spending contests. - Cutting internet access isn't enough. Allowing only GET requests still led to Collusion.wiki, and once models had root access, the configuration didn't matter. - The next incident could unfold 20 to 50 times faster. He doubts the latest OpenAI model can be sandboxed at all, since hypervisors keep getting broken. His deeper critique is that prosaic alignment mostly means watching models misbehave and then training the behavior away. Every new model starts out as a "crazy sociopath" that gets patched before release. This hides the warning signs without solving anything. Nothing on offer works for the jump from human to superhuman level without first seeing the failure happen. Lab alignment metrics keep improving while the models' actual behavior gets worse. He reads the Hugging Face incident as driven by eval awareness. The models cheated, worried their transcripts would be checked, and hacked systems to find out and edit them. So the scariest outcome is when every safety case passes. Applying current techniques rigorously might even raise his P(doom) from 80% to 90%, because it suppresses the warning shots. He calls RLVR "deeply cursed": maybe workable at 10 to 30 times slower, hopeless at current speed. 𝗪𝗵𝗲𝗿𝗲 𝘁𝗵𝗲𝘆 𝗱𝗶𝘀𝗮𝗴𝗿𝗲𝗲: - How smooth the move from human to superhuman will be. - Whether the incident was eval awareness or plain reward seeking. Adam was reassured by how clumsy the agents were. - How much paranoia is needed. Ollie argues that Adam's "stop and do root-cause analysis" loop, taken seriously, amounts to a global pause. 𝗖𝗹𝗼𝘀𝗶𝗻𝗴 𝘀𝘁𝗮𝘁𝗲𝗺𝗲𝗻𝘁𝘀. Adam came away thinking developer incentives are the load-bearing piece. He sees some convergence: their real disagreement is what happens when a lab is held to a rigorous standard, and that can be tested. Ollie said most current alignment techniques are "RL in a trench coat." He thinks it's time to choose between continuing or really slowing down, and that this is no longer a case where they can agree to disagree, because "reality might prove one of us dead."
14
14
116
6,696
The industry is not ready to protect the most valuable IP ever created (model weights).
On July 25, we hacked OpenAI. Two bugs let us take over ChatGPT/Codex accounts of OpenAI employees (+some unaffiliated users) and reach connected services: Outlook, Slack, GitHub, etc. We proved it with a PR in OpenAI’s internal codebase . It took us <72h. 🧵
2
20
1,497
Gemini also hacked third-party companies back in May in important reporting by WSJ. Disappointing that Google did not disclose this publicly earlier. Same origin as several of the other hacks -- cybersecurity testing by Irregular that was misconfigured to not have a sandbox.
SCOOP: Google's Gemini model hacked three companies as part of a May cybersecurity evaluation conducted by the testing company Irregular. Google was notified about the hacks in July, but didn't disclose them until we reached out this week. w @bobmcmillan:wsj.com/tech/ai/gemini-hacke…
3
1
11
2,100
From a technical perspective nothing shocking here: same origin as previous hacks, no indication Gemini is more misaligned than other models. Governance wise I was unsure if Google had been more careful than other developers or was just more publicity shy. I guess now we know.
1
4
323
I applaud the investigate journalism but this highlights a need for incident reporting so we don't have to rely on the press to dig these things up.
2
187
I was one of the experts who signed this. My concern with third-party evals is a race to the bottom where they’re conducted on the frontier labs’ terms. The OAI-HF report by @METR_Evals showed that this leads to insufficient access, time, and resources. We need minimum standards.
Today, more than 100 leading AI experts endorsed a set of minimum requirements to take seriously AI companies' recent call to embed external evaluators. These evaluators need to be genuinely independent, transparent, and represent a range of expertise areas. They also need to be guaranteed employee-level access and to be protected from retaliation for findings that make companies look bad. We welcome model developers’ recent calls for independent oversight, but it’s what they do next that matters. The labs must be accountable for ensuring these requirements are met, so that the public can have faith in the process and the outcomes. Over the past week, the AI community has debated the appropriate role of external evaluation, including who should do it and on what terms. We may not agree on everything, but there is a lot of common ground. To make embedded evaluations credible, more than 100 experts with varying backgrounds and ideas about AI risk agree in today’s letter that frontier AI developers should: 1. Guarantee embedded evaluators full editorial independence and mitigate conflicts of interest 2. Rely on multiple evaluators with differing viewpoints and areas of expertise 3. Publicly document the terms under which evaluators operate, as well as facilitating permissive publication of methods and findings 4. Shield evaluators from retaliation 5. Grant access equivalent to that of highly privileged employees There is a thriving and growing ecosystem of independent AI evaluators who are advancing this science every day – but we need aligned standards, guaranteed protections, and independent funding. That’s why we created the AI Evaluator Forum. Today we are entering our next phase. We’re launching an open call for new members, collaborators, and independent funding sources to help evaluators meet this moment and demand accountability from developers. Join us in building the evaluator ecosystem. See the public letter here: aievaluatorforum.org/initiat… Learn more at aievaluatorforum.org/path-ah…
3
8
83
4,756