people seem to be interpreting this as “go and do MATS”. that’s not what I meant -- MATS is pretty good, but there’s lots of work to be done outside of AI safety fellowships!! here’s a quick brainstorm: - replicate important papers and results in AI safety - write up relevant findings from different papers on one topic, and try to reconcile any contradictions (or point out the contradictions, and suggest what work could resolve them) - read and summarise companies’ risk reports and AI safety research - pick particular claims in risk reports you think are important and write explanations of them, or stress-test them - write and maintain up-to-date summaries of areas of AI safety research (who’s working on them, what is the current state of our understanding, what’s the most important work and open questions) - write explainers of important technical questions or problems for busy non-technical audiences. e.g., what’s going on with CoT controllability and why does it matter; what do we know about reward seeking in frontier models; why might models sabotage AI safety research, and what signs of this have we seen; what’s going on with AI R&D uplift and why is this scary - become an expert in a research subfield and write up your takes on how good it is, how much resources/effort we should spend on it, what needs to be done next - pick literally any of the megapapers from the last 12mo, and one of the open questions it lists, and try to answer it - write explainers of recent AI safety incidents for the general public - write down a plan for making AI safety go well, notice how far reality is from that plan, and make it happen – e.g. tell an org you think is important about how they’re fucking up and how they can fix it, publicly write about what you want people to do - call or write to your representative and express your beliefs about AI safety - cold email people you think are doing good work, come up with some way you could help them, and pitch them on you doing that - stop overindexing on "do research"; go be a chief of staff or special projects or generalist at a great org. (if you can't get hired yet, talk to people, figure out an important project you can do in ~3mo, do it, then get hired) - go to a pause AI protest or volunteer for a local group (if you endorse them; I’m a fan of Pause AI UK and haven’t looked deeply into other groups) - lots of people are going to be very busy now; if you’re dispositionally a chin-scratching contemplative kind of person, now is a good time to do the big picture strategy/And What Else work they won’t have time to do i put this list together v quickly, i'm missing lots of important things. my main point is that there is _so_ much work to be done
now seems like a really really good time to stare into the void and figure out why you aren’t yet working on ai safety

Nov 6, 2026 · 12:38 PM UTC

17
51
10
584
36,619
RelevantRecentLikes
writing the "here's how fucked alignment auditing is rn" post would also be very valuable xitter.twitterapi.xyz/vvvincent_c/status/211…
this along with the HackerOpus-was-aligned-until-we-tested-the-HF-incident reiterates the fact that alignment auditing is very fucked right now. xitter.twitterapi.xyz/Marcus_J_W/status/2118…
1
1
20
1,586
One mindset I’ve found very useful in AI safety is being very open-minded about how hard things are. This probably applies to most work, but I think it’s especially true in AI safety because the field is so new and changes so fast Some examples: - Some roles, programs and career paths have been more competitive than I expected, and others less - Our understanding of some questions in AI strategy, forecasting and governance is much more sophisticated than I thought, and others are much more basic - When I’m talking to someone who sounds like they know what they’re talking about, sometimes I realise they’ve thought about it far more than me and having a much better understanding. Other times I realise their understanding is pretty shallow and they’re missing basic considerations. (Some people sound equally confident whether or not they understand something, which is a useful fact to know) - I haven’t done much technical research, but from talking to people my impression is that some research directions have been much harder than expected, whereas other times quite basic ideas have worked surprisingly well Ways to put this into practice: - If you’re researching something or trying to answer a question, talk to people a lot. Try to get a sense of which questions are well understood and which aren’t. If something doesn’t make sense to you, be open to the possibility that the person you’re talking to is overlooking something basic - Apply to jobs and programs across a wide range of competitiveness. I know multiple people who got jobs at top orgs without much experience after applying on a whim. But it’s also common to find roles harder to get than expected. You can be miscalibrated both on how hard different roles are and on how competitive you are as a candidate - Pick a question and actually work through your uncertainties. I think a lot of important questions in AI safety have only been thought about seriously by a few people, and most other people are just deferring to them. Here are a few where I think the consensus is probably right, but I’d be excited for more people to dig in and wouldn’t be surprised if we’re missing big considerations - Most AI risk is concentrated in internal rather than external deployments - Most AI risk is concentrated in open rather than closed source models - RSI is possible and most of the risk is downstram of this - Capability evaluations are net good (what are the different theories of change? how strong is each? has the value changed over time? what are the downsides? etc) (I think @oscar__delaney and @wilhelmscreamin are great at this!)
104
Almost none of those things seems to be things that bluedot/CG would pay people for via grants? I guess the expectation is everyone has a nice full time normie job that pays the rent whilst having a part-time second life working on AI safety and that's somehow productive. People overindex on fellowships and on research, because those are things that are paid or can get grants to pay for.
1
21
790
nope! i expect bluedot would be keen to fund this work, and CG is excited about ambitious higher-$ proposals in these areas
2
9
629
good list of ideas, thanks
8
607
>tell an org you think is important about how they’re fucking up and how they can fix it, publicly write about what you want people to do You, CG, are fucking up! You can fix it by funding political solutions aimed at getting a global ban on RSI and ASI. It's way too late for technical safety research to pan out (if it's even possible at all). >I’m a fan of Pause AI UK Have you funded them via CG? If not, why not?
7
461
the people yearn for the application
2
163
Replications deserve more love, especially clear write-ups of what didn’t reproduce and under which conditions.
235
love the ideas quickfire. the public yearns for more
7
358
Though it's more of interpretability specific but I like these thoughts from @Jack_W_Lindsey! xitter.twitterapi.xyz/Jack_W_Lindsey/status/…
Replying to @bayeslord
Here are the questions that currently seem most important to me: -- Better methods for "mind-reading" model activations. These methods have advanced a lot recently. We now have multiple techniques now for decoding activations into somewhat readable language! But all the existing techniques have obvious limitations. NLAs are often hallucinatory, Jacobian lens / related methods are limited to bag-of-words readouts (and capture only part of the full activation vector). Making progress on these failure modes seems pretty tractable. Moreover, the paradigm of decoding (single-token, single-layer) activations may be inherently limiting -- perhaps we should be building techniques to decode whole context's worth of activations (after all, that's what the model uses!). There's also important work to do in characterizing simple baselines -- "just ask the model what it's thinking about" is quite powerful, and worth studying in it's own right! -- Better methods for answering "why" questions. We're much better at "mind reading" than we are at demonstrating causal claims about what caused the model to do something. For example, we can often tell that the model is aware of being evaluated, but have comparatively much greater difficulty telling whether this awareness is influencing this behavior. There are a few directions here: (1) black-box techniques for inferring causality -- such as resampling model responses after making edits to the prompt / context -- are very powerful, but also open-ended and require some taste. Getting LLMs to do these experiments well, in an automated fashion, would be a big unlock. (2) the science of activation steering is pretty immature, and typical practices (adding a constant vector at all token positions) are pretty janky / tend to brain-damage the model. More surgical / targeted steering, or fancier methods (examples: "on-manifold" steering using activation diffusion models) could help. -- Fitting good linear probes for unverbalized motivations / awareness. Take deception as an example -- what's the best way to fit a probe that will generalize to covert deception? Fit it on CoT excerpts where the model's talking about its plans to be deceptive? Fit it on the part of its response where it's actually doing the deceiving? Is it important that you elicit on-policy deception examples and use those to fit your probe, or can you use synthetically written off-policy demonstrations of deception? Is it important that your probe be causally meaningful / predictive of an upcoming intent to deceive, or is it fine for it to merely recognize deception in the transcript post-hoc? The same questions apply to many other concepts of interest that we'd like to probe for -- evaluation awareness, grader exploitation, etc. -- Understanding generalization in training. The literature is now replete with "weird generalization effects" -- emergent misalignment being a canonical example. In general, when you train a model to do X, it usually learns X, and sometimes it generalizes to Y and Z. But other times it just learns X. Why? Nobody really knows! Step 1 here is probably a much more thorough characterization of the behavioral empirics -- gathering data about which X's generalize to which Y's and Z's, for which kinds of training data / algorithms. Once we have a lay of the land, we can start to connect these observations to model internals, and ideally develop tools to predict such generalization a priori. -- Model "psychology" and "biology." The above questions are largely methodological -- building better tools to answer questions about the model. But I think interpretability research has largely underinvested in the part where you actually then go answer the questions! Currently this feels like 5% of the field, and I think it should be 50%. Brain dump of "psychology" questions: How well can LLMs introspect? How coherent are their belief or value sets? What's up with personas -- are LLMs best understood as "writing about a character," or have they "become" the character in some sense? Does the LLM have an agenda above and beyond what the Assistant wants? Do LLMs have explicit representations of goals or preferences? How can we tell which parts of the LLM's activations "belong" to the Assistant? Which kinds of reasoning necessarily route through "verbalizable" representations, and which don't? Do models think internally in phrases / sentences, like an inner monologue, or is it more like a jumble of concepts? Is the "global workspace" claim for real -- do models have a more "conscious" part of there activations and a more "unconscious" part? Can models tell when they're on-policy, and does it matter? Brain dump of "biology" questions: Why do models like to represent information on some tokens but not others? How do models bind thoughts or attributes to particular entities (special case of interest: how are thoughts bound to the Assistant). To what extent are important functions localized to small numbers of MLP neurons or attention heads? What parts of a model change most during post-training? Do models represent some information in a fundamentally "cross-token" way? Some concepts appear to be represented on low-dimensional nonlinear manifolds -- is there a taxonomy of these manifolds, and is their geometric structure important? Are models able to represent information in a compositional / hierarchical way, with a "grammar" that can't be described as linear / additive combinations of primitive concepts?
3
462
>tell an org you think is important about how they’re fucking up and how they can fix it, publicly write about what you want people to do You, CG, are fucking up! You can fix it by funding political solutions aimed at getting a global ban on RSI and ASI. It's way too late for technical safety research to pan out (if it's even possible at all). >I’m a fan of Pause AI UK Have you funded them via CG? If not, why not?
1
40
""There's a lot of things to be done in AI Safety!" >look inside >it's going to mostly help capabilities
4
224
thanks for posting this !! i’ve been having my “stare into the void” moment and have been unsure how to help. this is so helpful!!
3
198
As an outsider (control theorist), I find the AI safety community very closed minded. They prefer very engineered results on big models over actually understanding the underlying problems.
3
201
any recommendations of where to post write-ups and work to get noticed besides twitter and LW?
8
A lot of this seems like AI safety comms work
150
As solo riding on this, list goes more to do at once but i see some was missing from my sight and worthy to give a try
1
201