Twitxy Saved

Bryan Wilder

Verified account This account is verified. Learn more

@brwilder

Asst Prof, Carnegie Mellon Machine Learning Department
bryanwilder.github.io Joined June 2019
199 Following 2.3K Followers 346 Posts

Latest posts 5

Bryan Wilder Verified account @brwilder
This! It's much better for research communities to collectively build AI systems that check soundness norms for their own area and run that once on each paper. And "meat proxy" is too apt...I wish I could just talk directly to the ICLR reviewers' LLMs.
Jessica Hullman Verified account @JessicaHullman 2d
It really is pointless and unnecessary to allow external reviewers to use AI as they want. There are obvious better alternatives.

By now, everyone should already be using AI to check their work before submitting. So what's the point of reviewers meat proxying to send more AI-generated feedback? Seemingly none.

What happens if we ban AI use in peer review? The main risk is to the imagined role of peer review as a basic soundness filter. But this is much better addressed by the venue having a centralized approach that uses validated AI tools to check that a paper is what it says it is than by individual reviewers feeding papers to LLMs using basic prompts. Such checks might include things like whether the results can be reproduced from the data/code, whether claims can be traced back to some provided evidence, whether there are TODOs left by an LLM to replace table results with non-fake data, etc.

Some of these can be used to determine if a paper should be desk rejected. Anything that is more controversial can be surfaced for reviewers.

This will shift what reviewers pay attention to, but this can be addressed by: 1) making clear to reviewers that their role is to identify what these checks miss and to weigh them, 2) being intelligent about how you select the set of LLM checks that are surfaced. See e.g., our work on learning LLM-implemented checklist that avoid adding more bias than they reduce variance. arxiv.org/pdf/2610.28666

What happened with ICLR being permissive with reviewers using AI freely is seeming pretty inexcusable.
View quoted post on X
Bryan Wilder Verified account @brwilder
A bit over a year ago, I wrote about my fear that AI reviews would lead to monoculture in research (link below). This now seems to be exactly what is happening! Feedback from different reviewers largely echoes the same LLM talking points. This is actually *worse* than scrapping peer review entirely and generating a single LLM soundness review when arxiving the paper, since it wastes a lot of effort and incentivizes authors to optimize their papers for the (currently poor) research taste of LLMs in order to land above the acceptance cutoff.
11 replies 20 reposts 205 likes 11K views View on X
Bryan Wilder Verified account @brwilder
A new home for AI safety research at CMU! Our goal is to work on topics that will shape safety over the coming years -- grounded by current frontier systems but focused on identifying and studying the new challenges that increasingly capable and broadly diffused AI will pose.
Excited to announce our new center, Conceptual Research on Safe AI! We aim to develop new frameworks informed by the latest advances but with an eye towards the future. 2nd link has mailing list, LinkedIn, YouTube, postdoc position!
cs.cmu.edu/~coresafeai
cs.cmu.edu/~coresafeai/jo…
View quoted post on X
0 replies 2 reposts 23 likes 1.3K views View on X
Bryan Wilder Verified account @brwilder
New paper with @PerraultAndrew on reverse-engineering why agents cooperate with one another. The HF incident is an obvious prompt for this -- do agents work together because they place terminal value on the success of a group? Will they "sacrifice" their interests for other agents? Or do they mostly cooperate for individual advantage? For agents, these questions are quite messy conceptually. It's not clear if they do or should differentiate between themselves, their copies, their future self, etc.

We propose that researchers should use revealed-preference methods to disentangle not just *if* agents cooperate, but *why*. This means using careful experimental design to identify terms in a utility function which rationalizes why agents cooperate under some conditions and not others. Many intuitive experiments do not cleanly distinguish different mechanisms. We give examples of specific strategies to do so and the assumptions that they require.

Empirically, we examine the behavior of Sol, Fable, and GLM in a simulated environment. Big differences between model families! E.g., Sol mostly treats other instances instrumentally, while Fable's behavior is best rationalized by other-regarding preferences.

We think it's fair right now to see most empirical results as agents roleplaying whatever scenario is suggested, with a lot of variation depending on context. But systematic training for multiagent interactions is surely coming soon. Models will be subject to lots of selection pressure that will instill more specific dispositions about cooperation. Our motivation is to prepare for that near future, and work through what experimental designs would allow us to make sense of observed behavior. We actually started this project a month or so before HF and were amazed to see the motivation laid out so clearly and so soon! Time to think ahead to what's coming next.

arxiv.org/pdf/2610.19188
Bryan Wilder Verified account @brwilder
Recently, CMU had a great workshop on "AI agency and interpretability", with a mix of philosophers and computer scientists talking about interpreting/understanding AI and safety questions through the lens of rational agency. I wrote up a few reflections on the discussion, linked below.
Mainly, I came out of the workshop more excited about the area. Philosophers and computer scientists have a lot to learn from one another. There are important questions in both theory and empirical science to test if rational-agent frameworks are good ones, infer what beliefs or desires models might "have", and work through the consequences of those for mechanism design, training, and alignment.