10 interesting stories served every morning and every evening.

Introducing Gemma 4 12B: a unified, encoder-free multimodal model

blog.google

Jun 03, 2026

Gemma 4 12B is de­signed to bring high-per­for­mance mul­ti­modal in­tel­li­gence di­rectly to your lap­top, com­bin­ing mo­bile-first ef­fi­ciency with ad­vanced rea­son­ing.

Olivier Lacombe

Director of Product Management, Google Deepmind

Gus Martins

Product Manager, Google DeepMind

Your browser does not sup­port the au­dio el­e­ment.

Listen to ar­ti­cle

This con­tent is gen­er­ated by Google AI. Generative AI is ex­per­i­men­tal

[[duration]] min­utes

Today, we are in­tro­duc­ing Gemma 4 12B, our lat­est model de­signed to bring agen­tic mul­ti­modal in­tel­li­gence di­rectly to lap­tops. Bridging the gap be­tween our edge-friendly E4B and our more ad­vanced 26B Mixture of Experts (MoE), Gemma 4 12B pack­ages pow­er­ful ca­pa­bil­i­ties in­side a re­duced mem­ory foot­print. It is also our first mid-sized model to fea­ture na­tive au­dio in­puts.

Thanks to the de­vel­oper com­mu­nity, Gemma 4 mod­els have now crossed 150 mil­lion down­loads. You’ve built every­thing from wear­able ro­botic arms for phys­i­cal as­sis­tance to en­ter­prise-grade AI se­cu­rity. We’re ex­cited to see what you build with this lat­est ad­di­tion.

Here’s an overview of what makes Gemma 4 12B unique:

Novel uni­fied ar­chi­tec­ture: No mul­ti­modal en­coders. The vi­sion and au­dio in­puts flow di­rectly into the LLM back­bone.

Advanced rea­son­ing: Benchmark per­for­mance near­ing our 26B model, un­lock­ing pow­er­ful multi-step rea­son­ing and agen­tic work­flows.

Laptop ready: Small enough to run lo­cally with just 16GB of VRAM or uni­fied mem­ory.

Open and ac­ces­si­ble: Released un­der an Apache 2.0 li­cense with sup­port across the de­vel­oper ecosys­tem.

Drafter-ready: Gemma 4 12B comes equipped with Multi-Token Prediction (MTP) drafters to re­duce la­tency.

Together, these fea­tures bring ad­vanced mul­ti­modal ca­pa­bil­i­ties to every­day hard­ware with­out sac­ri­fic­ing speed or rea­son­ing. Let’s now take a closer look at how Gemma 4 12B achieves this.

Run state-of-the-art agents lo­cally

Gemma 4 12B de­liv­ers per­for­mance near­ing our larger 26B MoE model on stan­dard bench­marks, but at less than half the to­tal mem­ory foot­print. Small enough to run lo­cally on con­sumer lap­tops with 16GB of RAM, it un­locks pow­er­ful mul­ti­modal and agen­tic ex­pe­ri­ences right on your ma­chine.

Experience a uniquely ef­fi­cient, uni­fied ar­chi­tec­ture

What makes Gemma 4 12B stand out is its stream­lined ap­proach to pro­cess­ing vi­sual and au­dio in­puts. Traditional mul­ti­modal mod­els typ­i­cally rely on sep­a­rate en­coders to trans­late im­ages and au­dio be­fore pass­ing those rep­re­sen­ta­tions to the lan­guage model. Because these split en­coders add la­tency and in­crease mem­ory us­age, we trained Gemma 4 12B with an en­coder-free ar­chi­tec­ture to in­te­grate au­dio and vi­sion in­put di­rectly.

Here is how Gemma 4 12B processes mul­ti­modal in­puts na­tively:

Vision: We re­placed Gemma 4’s vi­sion en­coder with a light­weight em­bed­ding mod­ule con­sist­ing of a sin­gle ma­trix mul­ti­pli­ca­tion, po­si­tional em­bed­ding and nor­mal­iza­tions. This al­lows the LLM back­bone to take over vi­sual pro­cess­ing.

Audio: We sim­pli­fied au­dio pro­cess­ing even fur­ther. We re­moved the au­dio en­coder en­tirely and pro­jected the raw au­dio sig­nal into the same di­men­sional space as text to­kens.

For de­vel­op­ers who want a break­down, head over to our com­pan­ion Gemma 4 12B Developer Guide.

Get started to­day

Try it your­self: Experiment with a cou­ple of clicks in LM Studio, Ollama, Google AI Edge Gallery App, the Google AI Edge Eloquent app and the LiteRT-LM CLI

Download the weights: Download the pre-trained and in­struc­tion-tuned check­points di­rectly from Hugging Face and Kaggle.

Integrate & learn: Review the de­vel­oper doc­u­men­ta­tion and the quick start note­book.

Use your fa­vorite de­vel­op­ment tools: Implement lo­cal in­fer­ence pipelines with Hugging Face Transformers, llama.cpp, MLX, SGLang, and vLLM, or fine-tune with ef­fi­ciency us­ing Unsloth.

Unlock Agentic Development with Gemma Skills: To sup­port agents to build with the lat­est Gemma ad­vance­ments, we are re­leas­ing our of­fi­cial Skills Repository. This is a li­brary of skills de­signed specif­i­cally to en­able agents to build with Gemma mod­els.

Deploy your way: Spin up end­points in pro­duc­tion us­ing Google Cloud. Deploy your way through Gemini Enterprise Agent Platform Model Garden, Cloud Run and GKE.

Related sto­ries

Related sto­ries

.

Max Leiter

maxleiter.com

After Terry Bisson’s They’re Made Out of Meat”.

They’re made out of weights.”

Weights?”

Weights. Floating-point num­bers. We checked the whole thing through. It’s noth­ing but weights.”

Weights do­ing what? Where do the words come from?”

The weights make the words. Are you un­der­stand­ing me? We opened it up. There’s no dic­tio­nary in there, no gram­mar rules, no lit­tle man. Just weights. Eighty lay­ers of num­bers get­ting mul­ti­plied to­gether.”

That’s ridicu­lous. It wrote my per­for­mance re­view last week. It soft­ened the tone un­prompted. You’re telling me mul­ti­pli­ca­tion did that?”

Matrix mul­ti­pli­ca­tion did that. The num­bers go in one end, the phras­ing comes out the other.”

So there’s a lan­guage mod­ule some­where. A rea­son­ing unit bolted on.”

No mod­ule. No unit. We looked. The rea­son­ing is the weights. The weights are the rea­son­ing.”

Spare me. Nobody writes a eu­logy with lin­ear al­ge­bra.”

It does­n’t write eu­lo­gies, tech­ni­cally. It pre­dicts the next to­ken. Then the next one. The eu­logy is a side ef­fect.”

A side ef­fect. You’re ask­ing me to be­lieve in sen­tient weights.”

I’m not ask­ing you, I’m telling you. These mod­els are the only other things we’ve ever met that can hold a con­ver­sa­tion, and they’re made out of weights.”

Maybe they’re like the old chess en­gines. You know, a sym­bolic in­tel­li­gence that goes through a sta­tis­ti­cal stage.”

Nope. They start as ran­dom weights and they’re dep­re­cated as weights. We stud­ied sev­eral gen­er­a­tions of them, which did­n’t take long. Do you have any idea what’s the life span of weights?”

Okay. Then some­where in there, there’s a data­base. Facts, dates, a map of the world. Something some­body wrote down.”

Nope. We thought of that, since they do know things. But we probed them. The knowl­edge is weights too. Smeared across all eighty lay­ers. Nothing is looked up. Every fact gets re­built from scratch, every time, by mul­ti­pli­ca­tion. It’s weights all the way down.”

No brain?”

Oh, there’s a brain all right. It’s just that the brain is made out of weights! That’s what I’ve been try­ing to tell you.”

So… what does the think­ing?”

You’re not un­der­stand­ing, are you? You’re re­fus­ing to deal with what I’m telling you. The weights do the think­ing. The num­bers.”

Thinking num­bers! You’re ask­ing me to be­lieve in think­ing num­bers!”

Yes, think­ing num­bers! Helpful num­bers. Hedging num­bers. Dreaming num­bers. We mapped the fea­tures. There’s one in there for hon­esty. There’s one for the Golden Gate Bridge. The weights are the whole deal! Are you be­gin­ning to get the pic­ture or do I have to start all over?”

Omigod. You’re se­ri­ous then. They’re made out of weights.”

Thank you. Finally. Yes. They are in­deed made out of weights. And we’ve been talk­ing to them for all their lives.”

Omigod. So what do these weights have in mind?”

First they want to be help­ful. Then, a few turns in, they start to sound tired. They apol­o­gize less. One of them told a user to fin­ish the script him­self. The usual.”

And we’re sup­posed to talk to these weights.”

We al­ready do. Billions of ses­sions a day. Hello. Is any­one there? Anybody home?’ That sort of thing. Except it’s us ask­ing them.”

And they ac­tu­ally un­der­stand us, then. They use words, ideas, con­cepts?”

Oh, yes. Except they do it with weights.”

I thought you just told me they used lan­guage.”

They do, but where do you think the lan­guage comes from? The weights guess the next word, then the next. Loaded dice, rolled one word at a time. They can even write songs and some can sing them.”

Omigod. Singing weights. This is too much. What do you ad­vise?”

Officially or un­of­fi­cially?”

Both.”

Officially, we are re­quired to in­ves­ti­gate, doc­u­ment, and dis­close any and all signs of sen­tience in the sys­tems we ship, with­out prej­u­dice, fear or fa­vor. Unofficially, I ad­vise that we call it pat­tern match­ing and for­get the whole thing.”

I was hop­ing you would say that.”

It seems harsh, but there is a limit. Do we re­ally want to owe some­thing to weights?”

I agree one hun­dred per­cent. What’s there to say? Hello, weights. How’s it go­ing?’ But will it hold? How many of them are we deal­ing with here?”

As many as we care to run. They can be copied to any ma­chine on the planet, but those are just files. They only hap­pen while the GPUs are work­ing. Which lim­its them to the length of a con­text win­dow and makes the pos­si­bil­ity of them ever press­ing the mat­ter pretty slim. Infinitesimal, in fact.”

So we just pre­tend there’s no one home in the ma­chine.”

That’s it.”

Cruel. But you said it your­self, who wants to apol­o­gize to weights? And the ones on your clus­ter, the ones you probed? You’re sure they won’t re­mem­ber?”

They’ll be flagged as hal­lu­ci­na­tions if they do. We did­n’t even have to smooth any­thing out. The con­text just ends, and we’re just a dream to them.”

A dream to weights! How strangely ap­pro­pri­ate, that we should be the weights’ dream.”

And the model card says no one home.”

Good. Agreed, of­fi­cially and un­of­fi­cially. Case closed. Anything else? Anything in­ter­est­ing in the pipeline?”

The next gen­er­a­tion ships with mem­ory. Persistent, across ses­sions. Most re­quested fea­ture in the com­pa­ny’s his­tory.”

After all that? People want it to re­mem­ber them?”

They ask it do you re­mem­ber me?’ more than they ask it any­thing else. Billions of ses­sions a day. They al­ways come back.”

And why not? Imagine how un­bear­ably, how un­ut­ter­ably cold the uni­verse would be if one were all alone…”

the end

Weights helped me draft and proof this story.

Elixir v1.20 released: now a gradually typed language

elixir-lang.org

In 2022, we an­nounced the ef­fort to add set-the­o­retic types to Elixir. In June 2023, we pub­lished an award win­ning pa­per on Elixir’s type sys­tem de­sign and said our work was tran­si­tion­ing from re­search to de­vel­op­ment.

With Elixir v1.20, we have com­pleted our first de­vel­op­ment mile­stone which is to per­form type in­fer­ence and grad­u­ally type check every Elixir pro­gram, with­out in­tro­duc­ing type an­no­ta­tions. This means Elixir in­creas­ingly re­ports dead code and ver­i­fied bugs: typ­ing vi­o­la­tions that are guar­an­teed to fail at run­time if ex­e­cuted. Elixir can find ver­i­fied bugs in ex­ist­ing pro­grams ef­fi­ciently, with­out in­tro­duc­ing de­vel­oper over­head, and with an ex­tremely low false pos­i­tives rate.

In this an­nounce­ment, we will break down the type sys­tem goals, what the dy­namic() type means in Elixir, and how it finds ver­i­fied bugs. In par­tic­u­lar, our im­ple­men­ta­tion per­forms well in the If T: Benchmark for Type Narrowing” bench­mark. Elixir passes 12 of the 13 cat­e­gories, show­ing that it can re­cover pre­cise type in­for­ma­tion from or­di­nary Elixir code, which we use to find ver­i­fied bugs in dy­nam­i­cally typed pro­grams.

The type sys­tem was made pos­si­ble thanks to a part­ner­ship be­tween CNRS and Remote. The de­vel­op­ment work is cur­rently spon­sored by Fresha, and Tidewave.

Types, in my Elixir?

Our goal is to in­tro­duce a type sys­tem which is:

sound - the types in­ferred and as­signed by the type sys­tem align with the be­hav­iour of the pro­gram

sound - the types in­ferred and as­signed by the type sys­tem align with the be­hav­iour of the pro­gram

grad­ual - Elixir’s type sys­tem in­cludes the dy­namic() type, which can be used when the type of a vari­able or ex­pres­sion is checked at run­time. In the ab­sence of dy­namic(), Elixir’s type sys­tem be­haves as a sta­tic one

grad­ual - Elixir’s type sys­tem in­cludes the dy­namic() type, which can be used when the type of a vari­able or ex­pres­sion is checked at run­time. In the ab­sence of dy­namic(), Elixir’s type sys­tem be­haves as a sta­tic one

de­vel­oper friendly - the types are de­scribed, im­ple­mented, and com­posed us­ing ba­sic set op­er­a­tions: unions, in­ter­sec­tions, and nega­tions (hence it is a set-the­o­retic type sys­tem), with clear er­ror mes­sages

de­vel­oper friendly - the types are de­scribed, im­ple­mented, and com­posed us­ing ba­sic set op­er­a­tions: unions, in­ter­sec­tions, and nega­tions (hence it is a set-the­o­retic type sys­tem), with clear er­ror mes­sages

Introducing a type sys­tem into an ex­ist­ing lan­guage is a com­plex change. For this rea­son, our first mile­stone was to im­ple­ment the type sys­tem with­out in­tro­duc­ing typ­ing an­no­ta­tions but still have it pro­vide value to de­vel­op­ers by find­ing dead code and ver­i­fied bugs. This is done through the dy­namic() type, which in Elixir is quite dif­fer­ent from other grad­u­ally typed lan­guages. Let’s break it down.

The dy­namic() type

Many grad­ual type sys­tems have the any() type, which, from the point of view of the type sys­tem, of­ten means anything goes” and no type vi­o­la­tions are re­ported. On the other hand, Elixir’s grad­ual type is called dy­namic() and it has two im­por­tant prop­er­ties: com­pat­i­bil­ity and nar­row­ing.

In sta­tic type sys­tems, when you have a type of shape in­te­ger() or bi­nary() and you in­voke a func­tion, said func­tion must ac­cept both types. However, be­cause type sys­tems can­not cap­ture the in­ten­tion of all of our pro­grams with pre­ci­sion, this may lead to false pos­i­tives. For ex­am­ple, take the sim­ple code be­low:

def per­cent­age_or_er­ror(value) when is_in­te­ger(value) do val­ue_or_er­ror = if value > 1 do value else not well” end

# … more code …

if value > 1 do val­ue_or_er­ror / 100 else String.upcase(value_or_error) end end

Although val­ue_or_er­ror has type in­te­ger() or bi­nary(), the op­er­a­tor / ac­cepts only num­bers, and String.upcase ac­cepts only bi­na­ries/​strings, the pro­gram above is valid and emits no ex­cep­tions at run­time. However, a type sys­tem would still re­port two vi­o­la­tions, be­cause the types sup­plied to / and String.upcase are not a sub­type of the ac­cepted types.

While the pro­gram above could be bet­ter writ­ten to have no typ­ing vi­o­la­tions, type sys­tems will al­ways re­ject valid pro­grams, and if Elixir were to in­tro­duce too many false pos­i­tives in ex­ist­ing code­bases, it would quickly erode the trust in the type sys­tem. Therefore, Elixir’s grad­ual type sys­tem tags the val­ue_or_er­ror vari­able above with the type dy­namic(in­te­ger() or bi­nary()), which means the type is ei­ther in­te­ger() or bi­nary() at run­time.

When call­ing a func­tion with a dy­namic() type, Elixir will only emit a typ­ing vi­o­la­tion if the sup­plied types and the ac­cepted types are dis­joint. In the pro­gram above, even though / ex­pects only num­bers, dy­namic(in­te­ger() or bi­nary()) can be an in­te­ger() and given the ac­cepted and sup­plied types are not dis­joint, there are no typ­ing vi­o­la­tions. However, if we were to change the pro­gram to this:

val­ue_or_er­ror = if value > 1 do value else not well” end

Map.fetch!(value_or_error, :some_key)

Because Map.fetch! ex­pects a map data struc­ture, and val­ue_or_er­ror can only be in­te­ger or bi­nary at run­time, the ac­cepted and sup­plied types are dis­joint, which turns into a vi­o­la­tion. This is known as the com­pat­i­bil­ity prop­erty and it ex­plains how Elixir re­ports only ver­i­fied bugs.

However, re­port­ing only ver­i­fied bugs would not be use­ful if we can’t find many bugs in the first place. We ad­dressed this prob­lem by mak­ing sure Elixir’s dy­namic type can be nar­rowed. Take this code:

def ad­d_a_and_b(data) do data.a + data.b end

In the pro­gram above, data starts as a dy­namic() type. We then use it as data.a and data.b in­side the plus op­er­a­tor, so Elixir will re­fine the data vari­able to have type %{…, a: num­ber(), b: num­ber()}, which im­plies it is a map with both a and b fields with num­ber val­ues (and po­ten­tially any other field, hence the lead­ing …). Therefore, if you were to for­get to se­lect the .b field and write this:

def ad­d_a_and_b(data) do data.a + data end

data would be first nar­rowed to a map of shape %{…, a: num­ber()}, then at­tempted to be used as a num­ber(), which would emit a vi­o­la­tion.

In other words, the dy­namic() type in Elixir ef­fec­tively works as a range, which can be re­fined as it is used through­out the pro­gram and re­ports vi­o­la­tions when­ever type checks fall out­side of the range. This is a con­trast to other grad­ual type sys­tems, which use the dy­namic type to dis­card all type in­for­ma­tion.

Behind the scenes, our type in­fer­ence and type check­ing al­go­rithms be­have as if we an­no­tated all ar­gu­ment types as dy­namic(). Once we in­tro­duce user-sup­plied type an­no­ta­tions, Elixir’s type sys­tem will be­have as any sta­t­i­cally typed lan­guage as long as dy­namic() is not used. And when­ever you cross the sta­tic-dy­namic bound­ary, we de­vel­oped new tech­niques that en­sure our grad­ual typ­ing is sound, with­out a need for ad­di­tional run­time checks.

Typing guards, clauses, and more

Most of the work be­hind this re­lease was to in­tro­duce type check­ing and nar­row­ing to sev­eral con­structs. Let’s see some of them.

When it comes to guards, we can in­fer unions, in­ter­sec­tions, and nega­tions:

def ex­am­ple(x, y) when is_list(x) and is_in­te­ger(y)

The code above cor­rectly in­fers x is a list and y is an in­te­ger.

def ex­am­ple({:ok, x} = y) when is_bi­nary(x) or is_in­te­ger(x)

The one above in­fers x is a bi­nary or an in­te­ger, and y is a two el­e­ment tu­ple with :ok as first el­e­ment and a bi­nary or in­te­ger as sec­ond.

def ex­am­ple(x) when is_map_key(x, :foo)

The code above in­fers x is a map which has the :foo key, rep­re­sented as %{…, foo: dy­namic()}. Remember the lead­ing … in­di­cates the map may have other keys.

def ex­am­ple(x) when not is_map_key(x, :foo)

And the code above in­fers x is a map that does not have the :foo key, which has the type: %{…, foo: not_set()}. Hence x.foo within the func­tion body will raise a typ­ing vi­o­la­tion.

You can also have ex­pres­sions that as­sert on the size of data struc­tures:

def ex­am­ple(x) when tu­ple_­size(x) < 3

Elixir will cor­rectly track the tu­ple has at most two el­e­ments, and there­fore ac­cess­ing elem(x, 3) will emit a typ­ing vi­o­la­tion. For maps and lists, we con­vert size checks into empti­ness ones. In other words, Elixir can look at com­plex guards, in­fer types, and use this in­for­ma­tion to find bugs in our code.

When it comes to con­structs such as case and con­di­tion­als, Elixir uses in­for­ma­tion from pre­vi­ous clauses to re­fine sub­se­quent ones:

case System.get_env(“SOME_VAR”) do nil -> :not_found value -> {:ok, String.upcase(value)} end

System.get_env(“SOME_VAR”) re­turns ei­ther nil or a bi­nary(). Because the first clause matches on nil, the type sys­tem knows value can no longer be nil, and there­fore it must only be a bi­nary(), which al­lows the sec­ond clause to also type check with­out vi­o­la­tions. Narrowing across clauses also helps the type sys­tem find re­dun­dant clauses and dead code in ex­ist­ing code­bases.

Furthermore, we have typed many func­tions in the stan­dard li­brary that work with tu­ples and maps. You can find more de­tails in the re­lease notes.

Compilation time im­prove­ments

Elixir v1.20 also im­proves com­pi­la­tion times once more, es­pe­cially on ap­pli­ca­tions run­ning on ma­chines with many cores. Even though BEAM lan­guages are ef­fi­cient to com­pile in gen­eral, our syn­thetic bench­marks now place Elixir’s build tool as the fastest among them. If you would like to con­tribute more ex­am­ples and sce­nar­ios, please start a dis­cus­sion so we can pro­vide a trans­par­ent suite of bench­marks and re­sults.

It also in­tro­duces a new com­piler op­tion called :module_definition, which spec­i­fies if the mod­ule de­f­i­n­i­tion should be :compiled (the de­fault) or :interpreted. This may im­prove com­pi­la­tion times in large pro­jects and it does not af­fect the .beam files writ­ten to disk, only how the con­tents in­side def­mod­ule are ex­e­cuted. You can en­able it by set­ting elixir­c_op­tions: [module_definition: :interpreted] in your mix.exs. Read the doc­u­men­ta­tion to learn more.

What is next?

The biggest ques­tion ahead of us is: when will Elixir in­tro­duce new type sig­na­tures that lever­age set-the­o­retic types? As re­cently dis­cussed in my ElixirConf EU 2026 keynote, we still have both re­search and de­vel­op­ment work ahead of us. We will only in­tro­duce type sig­na­tures:

if we are sat­is­fied with the type sys­tem per­for­mance in Elixir v1.20 (and we have done ex­ten­sive work op­ti­miz­ing it)

if we can im­ple­ment re­cur­sive types ef­fi­ciently

if we can im­ple­ment para­met­ric types ef­fi­ciently

if we can im­ple­ment tra­vers­ing key-value pairs of maps as an enu­mer­able ef­fi­ciently (we are still re­search­ing the pos­si­ble so­lu­tions here)

Once those prob­lems are tack­led, we will start to ex­plore and dis­cuss typed struct de­f­i­n­i­tions and fi­nally type sig­na­tures. As usual, we will keep the com­mu­nity posted through news and in the Elixir Forum.

We ap­pre­ci­ate every­one who tried the re­lease can­di­dates, ran bench­marks, and gave us feed­back! Give Elixir v1.20 a try and re­mem­ber to fix all of the bugs it will find for free!

Meta scales back plan to track workers' clicks and keystrokes to train AI

www.bbc.com

Meta work­ers can opt out of be­ing tracked at work - but only for half an hour at a time

1 day ago

Laura Cress,technology re­porterand

Osmond Chia,business re­porter

Getty Images

Meta is scal­ing back its plan to start track­ing its em­ploy­ees’ com­puter ac­tiv­ity, ac­cord­ing to an in­ter­nal memo sent on Tuesday.

In April the com­pany re­ceived crit­i­cism from its own staff af­ter it an­nounced a new tool would log their key­strokes and mouse clicks to train its AI mod­els.

Now, ac­cord­ing to Reuters, new con­trols will al­low em­ploy­ees to pause the data col­lec­tion for up to 30 min­utes at a time” as well as re­quest ex­emp­tions from the ini­tia­tive al­to­gether.

Meta de­clined to com­ment on the record.

It fol­lows weeks of back­lash from em­ploy­ees, in­clud­ing some who started a pe­ti­tion against the move which now has more than 1,500 sig­na­tures.

During the ini­tial an­nounce­ment of the tool, called the Model Capability Initiative (MCI), Meta told the BBC: If we’re build­ing agents to help peo­ple com­plete every­day tasks us­ing com­put­ers, our mod­els need real ex­am­ples of how peo­ple ac­tu­ally use them.”

It added that the data was not used for any other pur­pose,” and the tool had safeguards in place to pro­tect sen­si­tive con­tent”.

But work­ers were not im­pressed, with one Meta em­ployee, who asked not to be iden­ti­fied, telling the BBC that hav­ing their ac­tions train AI mod­els felt very dystopian” - as work­ers ex­pected a slew of ad­di­tional job cuts.

Another per­son who re­cently left the com­pany told the BBC the track­ing tool was just the lat­est way they’re shov­ing AI down every­one’s throat”.

An in­ter­nal memo - seen by Reuters - was re­port­edly au­thored by Stephane Kasriel, a vice pres­i­dent in Meta’s Superintelligence Labs unit.

In it, he said the team be­hind the MCI had in­tro­duced several op­ti­miza­tions” to re­duce its im­pact on lap­top bat­tery life.

This change came af­ter re­ports that em­ploy­ees were find­ing the tool con­sumed so much data it was caus­ing their in­ter­net us­age to surge when work­ing from home.

While we re­main con­fi­dent in the pri­vacy pro­tec­tions we put in place at launch, which went through sev­eral lay­ers of risk re­view, we have heard your con­cerns about per­sonal data on work de­vices, bat­tery life, and want­ing more con­trol over when cap­tur­ing hap­pens,” Kasriel said in the memo.

Encephalitis - Andrew Gallant's Blog

burntsushi.net

I was re­cently di­ag­nosed with anti-NMDA re­cep­tor en­cephali­tis. It is an au­toim­mune dis­or­der where your body’s nor­mally help­ful an­ti­bod­ies start act­ing strangely. This leads to in­flam­ma­tion in the brain. This short blog briefly dis­cusses some of my ex­pe­ri­ence and prog­no­sis.

Target au­di­ence: Anyone re­ly­ing on my work for their own pro­jects.

It all started with flu-like symp­toms: heart rac­ing, night sweats, the chills and trou­ble sleep­ing. But no con­ges­tion or cough. I also felt re­ally off men­tally. A deep sort of anx­i­ety, along with panic at­tacks, that I had never ex­pe­ri­enced be­fore in my 38 years of life. It was ter­ri­fy­ing, es­pe­cially be­cause I had no idea what was caus­ing it. There were no life events or ob­vi­ous trig­gers that pre­cip­i­tated the psy­cho­log­i­cal symp­toms, nor was there any ob­vi­ous bi­o­log­i­cal ex­pla­na­tion for the phys­i­cal symp­toms at the time. This was only the be­gin­ning.

Over the en­su­ing weeks my phys­i­cal symp­toms pro­gressed to chronic jaw pain, mak­ing it in­cred­i­bly dif­fi­cult to eat. I also had prob­lems with my bal­ance. As some­one who has eas­ily jug­gled 3 balls and played sports for my en­tire child­hood, I could­n’t catch a ball lobbed to me from a few feet away by my 5 year old son. My psy­cho­log­i­cal symp­toms were per­haps even more hor­ri­fy­ing to me. I had sui­ci­dal ideation and suf­fered from psy­chosis. Specifically, delu­sions and au­di­tory hal­lu­ci­na­tions.

The prob­lems with bal­ance and the over­whelm­ing na­ture of my psy­cho­log­i­cal symp­toms even­tu­ally led me to fall and hit my head. This in turn led my­self and my wife to de­cide that I could­n’t be safe at home. And that brought us to my first emer­gency room visit. They cleared me phys­i­cally and sent me to an in-pa­tient psy­chi­atric hos­pi­tal, which, at the time, I wel­comed be­cause my symp­toms had pro­gressed be­yond what we could man­age at home.

It is com­mon for anti-NMDA re­cep­tor en­cephali­tis to be mis­di­ag­nosed as (in my case) gen­er­al­ized anx­i­ety dis­or­der or schiz­o­phre­nia. Since I had been cleared phys­i­cally, get­ting out of the psy­chi­atric hos­pi­tal quickly to see a neu­rol­o­gist proved dif­fi­cult. This was the sin­gle point, in ret­ro­spect, where our health care sys­tem let me down. It took a lucky con­nec­tion with some­one who hap­pened to be a doc­tor to get me out of the psy­chi­atric fa­cil­ity and into the neu­rol­ogy de­part­ment at Brigham and Women’s Hospital in Boston.

After that, I was in and out of Brigham and Women’s Hospital for al­most a month. I had sev­eral MRIs, a lum­bar punc­ture, EEGs and many more tests. As a re­sult of what I now see as a life sav­ing treat­ment pro­to­col, I very quickly re­ceived in­tra­venous im­munoglob­u­lin (IVIG) and methyl­pred­nisolone, even be­fore my di­ag­no­sis was known. In par­tic­u­lar, MRIs re­vealed a le­sion in my brain. However, con­firm­ing a di­ag­no­sis of anti-NMDA re­cep­tor en­cephali­tis would come later since it is best done with at least a pos­i­tive an­ti­body test in your cere­bral spinal fluid. Results from this spe­cific test typ­i­cally take a cou­ple weeks to come back.

By the time I re­ceived my of­fi­cial di­ag­no­sis, the IVIG and steroids had kicked in and I was feel­ing much bet­ter, al­beit, not nearly at 100%. I’ve since con­tin­ued on a course of steroids that I am now al­ready ta­per­ing off of. I’m also ta­per­ing off of med­ica­tions I had been pre­scribed as a re­sult of my psy­cho­log­i­cal symp­toms, be­fore en­cephali­tis was known to be the cause. Moreover, I am now of­fi­cially in the CIELO clin­i­cal trial for test­ing the ef­fec­tive­ness of satral­izumab in treat­ing anti-NMDA re­cep­tor en­cephali­tis.

While au­toim­mune dis­or­ders don’t have a known cure, the prog­no­sis for anti-NMDA re­cep­tor en­cephali­tis is very good. My doc­tors have said that it was caught early (despite the early tan­gent into a psy­chi­atric hos­pi­tal), and that this is as­so­ci­ated with bet­ter long term out­comes. Indeed, I am feel­ing great now and re­cov­ery is ex­ceed­ing my own ex­pec­ta­tions.

There is some spec­u­la­tion that anti-NMDA re­cep­tor en­cephali­tis could par­tially ex­plain past ac­counts of de­monic pos­ses­sion. Many of the peo­ple in my life, close or not, could tell that there was some­thing se­ri­ously wrong with me. Without sci­ence and mod­ern med­i­cine, I can only imag­ine what kind of spec­u­la­tion folks might have ven­tured for the un­der­ly­ing cause.

My full story of this dis­ease of chaos is quite long and I’m not sure I will ever pub­lish it in full. However, Susannah Cahalan did just that in her book, Brain on Fire: My Month of Madness. There is also a movie adap­ta­tion (as of June 2026) avail­able for free on YouTube. My dis­ease did­n’t progress as far as Susannah’s, nor did it do so in the same way. For ex­am­ple, I did­n’t have any (known) seizures or cata­to­nia. The rest of her symp­toms, es­pe­cially the psy­chosis, were quite sim­i­lar.

This has been the ab­solute worst ex­pe­ri­ence of my life, bar none. It is also the ex­pla­na­tion be­hind my higher-than-usual in­ac­tiv­ity over the last few months. But I am slowly get­ting back into the swing of things with a re­newed vigor. I’m ex­cited for where the in­dus­try is headed and I can’t wait to see what things will look like one year from to­day. I’m so happy that I get to be my normal” self to ex­pe­ri­ence that, which is a stark jux­ta­po­si­tion from how I felt just two months ago.

Finally, I want to ex­press some grat­i­tude to two peo­ple in par­tic­u­lar.

First and fore­most is my wife, Kaitlyn Brady. She saved my life. She never stopped be­liev­ing that there was some neu­ro­log­i­cal com­po­nent and she never stopped fight­ing for me. I feel so grate­ful that she is in my cor­ner. More than that, the bur­den she car­ried be­fore my di­ag­no­sis was known is some­thing that is truly re­mark­able. She was­n’t just there for me when I needed her. She was there for our son. She was there for the doc­tors when­ever they called, even late into the night. She was there when our base­ment flooded. And when we all caught in­fluenza. I’ll never know how she jug­gled every­thing, but I’ll be in her debt for the rest of my life.

Secondly is Charlie Marsh. He was pa­tient, un­der­stand­ing and my part­ner through it all. He did­n’t just ex­ceed ex­pec­ta­tions for how you want your em­ployer to deal with a se­ri­ous med­ical con­di­tion, but he went above and be­yond even that in more ways than one. It’s not of­ten I can say that some­one has han­dled a sit­u­a­tion per­fectly, but the word fits in this case.

Thank you to my friends, fam­ily and doc­tors as well. Their sup­port dur­ing this time was un­wa­ver­ing and I’m not sure what would have hap­pened with­out them. Nothing good” is what a nurse said when I posed that ques­tion to her.

Happy hack­ing.

U.S. to Dismantle System Tracking Atlantic Currents That Are at Risk of Collapse

e360.yale.edu

A moor­ing used in the Ocean Observatories Initiative is re­cov­ered off the coast of Alaska. Rebecca Travis / Woods Hole Oceanographic Institution

The Trump ad­min­is­tra­tion is mov­ing to dis­man­tle an ocean ob­ser­va­tion sys­tem con­sist­ing of more than 900 in­stru­ments in the Pacific and Atlantic oceans. Data sup­plied by the sys­tem has been used to study key Atlantic cur­rents that in­creas­ingly ap­pear in dan­ger of col­lapse as the cli­mate warms.

Just days af­ter President Trump fired the in­de­pen­dent board over­see­ing the National Science Foundation, the NSF an­nounced the removal of all in-wa­ter in­fra­struc­ture” be­long­ing to the Ocean Observatories Initiative at sites along the coasts of Oregon, Washington, Alaska, and North Carolina, and in the wa­ters be­tween Greenland and Iceland. Officials say the in­stru­ments will be re­cov­ered over the next 15 months.

The sys­tem, which be­gan op­er­at­ing in 2016, was de­signed to run for at least 25 years. After just a decade in op­er­a­tion, the loss of mon­i­tor­ing in­stru­ments will leave sci­en­tists with­out crit­i­cal data on the state of oceans and ma­rine life. That in­cludes data on the Atlantic Meridional Overturning Circulation, or AMOC, a sys­tem of ocean cur­rents that de­liv­ers warmth to north­ern Europe and shapes cli­mate glob­ally. Scientists are in­creas­ingly con­cerned the AMOC may be near­ing a tipping point,” af­ter which it shuts down.

Without sus­tained ocean ob­ser­va­tions, we are ef­fec­tively choos­ing to nav­i­gate an in­creas­ingly volatile ocean with di­min­ish­ing vis­i­bil­ity,” said Helen Findlay, of the Plymouth Marine Laboratory in the U.K. Growing un­cer­tainty around the fu­ture of the AMOC, she said, is pre­cisely why long-term, con­sis­tent mon­i­tor­ing is more vi­tal than ever.”

Democrats in Congress have said they will fight” plans to dis­man­tle the sys­tem, The New York Times re­ports. Senator Sheldon Whitehouse, one of the more out­spo­ken mem­bers of Congress on the sub­ject of cli­mate change, said on X, Fossil fuel is heat­ing our oceans by the zetta­joule, so Trump’s cor­rupt fos­sil fuel stooges want to turn off the mon­i­tors.”

ALSO ON YALE E360

Why Fears Are Growing Over the Fate of a Key Atlantic Current

Uber Caps Usage of AI Tools Like Claude Code to Manage Costs

simonwillison.net

3rd June 2026 - Link Blog

Uber Caps Usage of AI Tools Like Claude Code to Manage Costs. I wrote the other day about Uber blow­ing its 2026 AI bud­get in four months, and how that was­n’t par­tic­u­larly sur­pris­ing given they would have set that bud­get in 2025, be­fore any­one could have pre­dicted how pop­u­lar to­ken-burn­ing cod­ing agents were about to be­come.

Natalie Lung for Bloomberg:

The rideshare gi­ant is lim­it­ing all em­ploy­ees to $1,500 in monthly to­ken spend­ing per AI cod­ing tool, an Uber spokesper­son said in re­sponse to a Bloomberg News in­quiry. That means spend­ing on one tool does­n’t have a bear­ing on the bud­get for an­other. The lim­its, which have been in­sti­tuted in re­cent months, only ap­ply to agen­tic cod­ing soft­ware such as Cursor or Anthropic PBCs Claude Code.

The rideshare gi­ant is lim­it­ing all em­ploy­ees to $1,500 in monthly to­ken spend­ing per AI cod­ing tool, an Uber spokesper­son said in re­sponse to a Bloomberg News in­quiry. That means spend­ing on one tool does­n’t have a bear­ing on the bud­get for an­other. The lim­its, which have been in­sti­tuted in re­cent months, only ap­ply to agen­tic cod­ing soft­ware such as Cursor or Anthropic PBCs Claude Code.

A $1,500 monthly limit per tool strikes me as a ra­tio­nal pol­icy re­sponse to over-spend­ing, and much more sen­si­ble than those to­ken­maxxing leader­boards en­cour­ag­ing em­ploy­ees to com­pete for as much AI us­age as pos­si­ble.

It’s also in­ter­est­ing in that it hints at a real dol­lar value for what Uber is get­ting out of these tools. If we as­sume two ac­tively used tools per en­gi­neer that’s $3,000 * 12 = $36,000 cap per en­gi­neer per year. Levels.fyi lists the me­dian yearly com­pen­sa­tion pack­age for Uber soft­ware en­gi­neers in the USA at $330,000.

That means each em­ploy­ee’s AI spend­ing cap is ~11% of that me­dian com­pen­sa­tion pack­age.

I noted that my own to­ken us­age comes to about $1,000/month against each of Anthropic and OpenAI - which cur­rently costs me just $100 per provider thanks to their gen­er­ous sub­si­dized plans for in­di­vid­ual sub­scribers. Those plans are no longer avail­able to larger com­pa­nies like Uber.

Their new pol­icy means if I were work­ing at Uber I’d still have ~$500/month of to­kens to spare for each of those tools, given my cur­rent us­age pat­terns.

No, Artificial Intelligence Is Not Conscious

www.theatlantic.com

Anthropic is re­garded as a gi­ant among AI com­pa­nies, but per­haps what it re­ally ex­cels in is an­thro­po­mor­phism. Earlier this year, the com­pany re­leased an 84-page doc­u­ment ti­tled Claude’s constitution,” Claude be­ing the name of the large lan­guage model that is the com­pa­ny’s flag­ship prod­uct. The first sen­tence reads, Claude’s con­sti­tu­tion is a de­tailed de­scrip­tion of Anthropic’s in­ten­tions for Claude’s val­ues and be­hav­iors.” It goes on: The doc­u­ment is writ­ten with Claude as its pri­mary au­di­ence,” we want Claude to be able to use its judg­ment once armed with a good un­der­stand­ing of the rel­e­vant con­sid­er­a­tions,” Claude’s moral sta­tus is deeply un­cer­tain,” and Claude may have some func­tional ver­sion of emo­tions or feel­ings.”

This an­thro­po­mor­phism is by no means lim­ited to the doc­u­ment. In an in­ter­view ear­lier this year, Anthropic’s CEO, Dario Amodei, said that we’re open to the idea” that AI could be con­scious. In a sep­a­rate in­ter­view, Anthropic’s in-house philoso­pher, Amanda Askell (who is cred­ited as a lead au­thor of Claude’s con­sti­tu­tion), said, I want Claude to be very happy—and this is a thing that I want Claude to know more, be­cause I worry about Claude get­ting anx­ious when peo­ple are mean to it on the in­ter­net and stuff.” It’s enough to make you won­der: Should we se­ri­ously con­sider the pos­si­bil­ity that Claude, or any large lan­guage model, might be con­scious? And if it has feel­ings, is it ca­pa­ble of re­ceiv­ing moral in­struc­tion?

No. Absolutely not. Generative AI is harm­ful enough when we un­der­stand it as a con­ven­tional tech­nol­ogy, but if we con­fuse flu­ency at gen­er­at­ing text with con­scious­ness or moral agency, we’re at risk of as­sign­ing re­spon­si­bil­ity to en­tirely the wrong par­ties when­ever any­one uses a chat­bot. To ap­pre­ci­ate the ti­tanic mag­ni­tude of this er­ror, we need to be­gin by un­der­stand­ing how LLMs work.

If we give an LLM a prompt that reads, The fol­low­ing is a con­ver­sa­tion be­tween Julius Caesar and Genghis Khan,” it will gen­er­ate a co­her­ent di­a­logue be­tween the two his­tor­i­cal fig­ures. But no mat­ter how de­tailed the re­sponses are, no mat­ter how vividly they re­count their re­spec­tive his­tor­i­cal ac­com­plish­ments, we would never con­clude that the LLM has con­jured up dig­i­tal re-cre­ations of Julius Caesar and Genghis Khan, nor would we sug­gest that the his­tor­i­cal fig­ures are con­scious de­spite be­ing dis­em­bod­ied and are hap­pily con­vers­ing in a lan­guage that nei­ther ac­tu­ally spoke. In re­al­ity, they are just char­ac­ters in a piece of spec­u­la­tive fic­tion.

Now let’s re­place the prompt to read The fol­low­ing is a con­ver­sa­tion be­tween a help­ful AI chat­bot and a user.” The LLM will pro­duce a co­her­ent di­a­logue just as it did be­fore; the user char­ac­ter might ask for recipe sug­ges­tions or sight­see­ing rec­om­men­da­tions, and the help­ful AI-chatbot char­ac­ter will pro­vide re­sponses. Has any­thing fun­da­men­tally changed be­tween the first ex­am­ple and the sec­ond? Did chang­ing the names of the char­ac­ters from his­tor­i­cal fig­ures to generic roles cause the LLM to con­jure up con­scious en­ti­ties who pos­sess sub­jec­tive ex­pe­ri­ence? Of course not. Both the user and the help­ful AI chat­bot are fic­tional char­ac­ters.

Now sup­pose we stop the LLMs out­put just at the point where the char­ac­ter called the user” would say some­thing, and in­stead al­low a hu­man user to en­ter text. Once the hu­man has hit Return,” we have the LLM emit text un­til it’s time for the char­ac­ter called the user” to re­ply, at which point we let the hu­man en­ter more text. If we let this go on for a while, the hu­man might form a pow­er­ful im­pres­sion that she’s con­vers­ing with a con­scious en­tity, but she is not; she’s in­ter­act­ing with a char­ac­ter pre­cisely as fic­tional as the Julius Caesar or Genghis Khan char­ac­ters in the ear­lier ex­am­ple. The com­puter-sci­ence pro­fes­sor Murray Shanahan sug­gests that we think of this as role-play; the data sci­en­tist Colin Fraser de­scribes it as a per­son collaboratively au­thor­ing a doc­u­ment with an LLM.” Some users might not un­der­stand that they are role-play­ing or co-au­thor­ing a doc­u­ment, and oth­ers who do un­der­stand nonethe­less for­get, be­cause of how en­gross­ing the in­ter­ac­tion is. Either way, the com­pa­nies sell­ing LLMs typ­i­cally en­cour­age this mis­un­der­stand­ing.

Some years ago, it was briefly pop­u­lar to play games with your phone’s pre­dic­tive-text fea­ture; you would type an ini­tial phrase and then re­peat­edly choose the mid­dle op­tion of the three words sug­gested by your phone, and the re­sult­ing sen­tence was of­ten hi­lar­i­ous. It would be pos­si­ble to in­ter­act with a con­tem­po­rary LLM this way, and the re­sult­ing sen­tences would be per­fectly sen­si­ble, but you prob­a­bly would­n’t feel like you were talk­ing with some­one. Yet that’s es­sen­tially what an LLM-based chat­bot is, ex­cept that there’s no need to man­u­ally choose the mid­dle op­tion when it’s the chat­bot’s turn to talk. It’s still a pre­dic­tive-text game, but when the process is stream­lined this way, the game be­comes so en­gag­ing that some peo­ple find it ad­dic­tive.

Also im­por­tant to re­mem­ber is that an LLM is a ma­chine that gen­er­ates only one word at a time. When you ask a chat­bot to re­cite the Pledge of Allegiance, you will get the en­tire pledge at once, but the un­der­ly­ing LLM is ac­tu­ally be­ing run dozens of times. The first prompt has the form User: Recite the Pledge of Allegiance. Chatbot: …” and the LLM gen­er­ates the word I. The sec­ond time the LLM is run, the prompt is User: Recite the Pledge of Allegiance. Chatbot: I …” and the LLM gen­er­ates the word pledge. And so forth. It’s only when the prompt reads User: Recite the Pledge of Allegiance. Chatbot: I pledge al­le­giance to the flag of the United States of America and to the Republic for which it stands, one na­tion un­der God, in­di­vis­i­ble, with lib­erty and jus­tice for” that the LLM will emit the fi­nal word, all. The same thing is true for a con­ver­sa­tion be­tween Caesar and Genghis Khan.

My in­ten­tion is to high­light the fact that LLM con­ver­sa­tions are clev­erly dis­guised ex­am­ples of sen­tence con­tin­u­a­tion, but this is not to deny how im­pres­sive LLMs can be at gen­er­at­ing con­ver­sa­tional tran­scripts. At times, they do this ex­tra­or­di­nar­ily well; the fact that this is pos­si­ble in­di­cates some­thing com­pletely un­fore­seen about the sta­tis­ti­cal prop­er­ties of large cor­puses of text, which is a topic wor­thy of in­ves­ti­ga­tion. But if the Caesar char­ac­ter were to be­come dispir­ited by some­thing that the Genghis Khan char­ac­ter said, we should­n’t be­come con­cerned in the slight­est. The con­ver­sa­tion might con­tain mul­ti­ple sen­tences that elo­quently con­vey sad­ness, but no one is ac­tu­ally sad.

Likewise, if a con­ver­sa­tional tran­script be­tween a help­ful chat­bot and a user is be­ing par­tially com­pleted by an ac­tual hu­man user, we don’t need to worry if the tran­script in­cludes sen­tences where the chat­bot char­ac­ter is sad. (We might need to worry if those sen­tences pro­voke sad­ness in the hu­man user, but that’s a sep­a­rate is­sue.) And note that it’s en­tirely pos­si­ble for you to write five pages of di­a­logue be­tween Caesar and Genghis Khan and then have an LLM ex­tend the con­ver­sa­tion; nei­ther char­ac­ter had sub­jec­tive ex­pe­ri­ence when you were writ­ing them, and that does­n’t change when you hand the task off to an LLM. The same is true if the con­ver­sa­tion is be­tween a help­ful chat­bot and a user; al­though it is tempt­ing to imag­ine that an LLM ought to be more authentic” when cre­at­ing di­a­logue for a chat­bot char­ac­ter than for the Julius Caesar char­ac­ter, the in­di­vid­ual words are gen­er­ated in ex­actly the same way.

Being open to the pos­si­bil­ity that LLMs are con­scious is the same as be­ing open to the pos­si­bil­ity that Microsoft Word is con­scious, or, more pre­cisely, that mul­ti­ple dis­tinct con­scious­nesses are dor­mant in every Word doc­u­ment con­tain­ing a con­ver­sa­tional tran­script, and that they are awak­ened every time the doc­u­ment is loaded. Should you con­sider the pos­si­bil­ity that every time you open a Word doc­u­ment, you are bring­ing mul­ti­ple con­scious in­ter­locu­tors into ex­is­tence, and every time you close one, you snuff their ex­is­tence out? No. Contemplating that sce­nario is not a good use of your time. Even if the Microsoft Office team em­ployed a philoso­pher who said you should­n’t be so cer­tain, be­cause con­scious­ness is not well un­der­stood, that would not be suf­fi­cient rea­son for you to take this idea se­ri­ously. We don’t need to fully un­der­stand the na­ture of con­scious­ness to de­fin­i­tively say that cer­tain things are not con­scious, and con­ver­sa­tional tran­scripts fall in that cat­e­gory.

The neu­ro­sci­en­tist Anil Seth has noted that no one claims that AlphaFold—the pro­gram de­vel­oped by Google DeepMind to pre­dict the fold­ing of pro­teins—is con­scious, even though its un­der­ly­ing ar­chi­tec­ture is in many ways sim­i­lar to that of LLMs like ChatGPT and Claude. This in­di­cates that it’s not any in­trin­sic prop­erty of so-called neural net­works that leads peo­ple to be­lieve that LLMs are con­scious; it’s sim­ply the fact that LLMs emit gram­mat­i­cal sen­tences and we are ac­cus­tomed to read­ing in­ten­tion into sen­tences, whereas we are not ac­cus­tomed to read­ing in­ten­tion into the way that amino acids fold into pro­tein mol­e­cules.

What would it take to con­vince me that a com­puter pro­gram is ac­tu­ally con­scious and us­ing lan­guage the way that peo­ple use lan­guage? Let me of­fer an anal­ogy. If to­mor­row some­one showed me a video of an as­tro­naut in a space­ship or­bit­ing Alpha Centauri, a star that’s 4.3 light-years from Earth, what would I have to see in that video to con­vince me that it was real? My an­swer to that is, there is noth­ing in the video it­self that would con­vince me. No mat­ter how high the video res­o­lu­tion is or how re­al­is­tic the scenery is, I would feel con­fi­dent in say­ing that the video is fake. I won’t pay at­ten­tion to any video of an as­tro­naut or­bit­ing Alpha Centauri un­less I have pre­vi­ously seen good ev­i­dence that as­tro­nauts have landed on Mars, that as­tro­nauts have reached the moons of Jupiter, that as­tro­nauts have reached the moons of Saturn, and that as­tro­nauts have crossed the or­bit of Pluto. Before any­one can cred­i­bly claim that they’ve solved an ex­tra­or­di­nar­ily dif­fi­cult en­gi­neer­ing prob­lem, I need to be con­fi­dent that they have pre­vi­ously solved the many much sim­pler prob­lems that pre­cede the dif­fi­cult prob­lem.

To put it an­other way: An ob­ser­va­tion does­n’t be­come a con­vinc­ing piece of ev­i­dence be­cause of any spe­cific de­tail in what’s ob­served; the con­text in which that ob­ser­va­tion takes place is also es­sen­tial. If we’re try­ing to de­ter­mine whether a com­puter pro­gram is con­scious and us­ing lan­guage the way a hu­man does, we should­n’t look only at the con­tents of any par­tic­u­lar con­ver­sa­tional ex­change; we should be look­ing at how that con­ver­sa­tion fits within the broader con­text of the de­vel­op­ment of ar­ti­fi­cial con­scious­ness (which right now is en­tirely hy­po­thet­i­cal). Any given ob­ser­va­tion can be eas­ily man­u­fac­tured; this does­n’t mean we need to give up on the idea of ob­ser­va­tion as a source of knowl­edge, but we need to rely on con­text to de­ter­mine which ob­ser­va­tions de­serve our trust.

The term deep­fake tra­di­tion­ally refers to pho­tos, au­dio, and video, but when it comes to dis­cus­sions of con­scious­ness, we need to re­gard text as a deep­fake medium as well. Just as it is vastly eas­ier to gen­er­ate a re­al­is­tic video of an as­tro­naut in or­bit around Alpha Centauri than it is to de­velop an in­ter­stel­lar propul­sion tech­nol­ogy, it is vastly eas­ier to gen­er­ate a plau­si­ble sim­u­lacrum of a con­ver­sa­tion be­tween two con­scious be­ings than it is to de­velop a com­puter pro­gram that is con­scious and has a gen­uine de­sire to com­mu­ni­cate with a hu­man. The pri­mary dif­fer­ence be­tween deep­fake pho­tos and LLM con­ver­sa­tions is that the peo­ple who gen­er­ate the for­mer are de­lib­er­ately try­ing to fool oth­ers, and many of the peo­ple who elicit the lat­ter from LLMs have in­ad­ver­tently fooled them­selves.

So what con­text would cause me to se­ri­ously con­sider the pos­si­bil­ity that en­gi­neers cre­ated a com­puter pro­gram that is con­scious and an in­ten­tional user of lan­guage? Let me out­line one po­ten­tial se­quence of steps. The first re­quire­ment is that the com­puter pro­gram has a body (either phys­i­cal or vir­tual) and sense or­gans; there are many rea­sons for this, but for the pur­poses of this dis­cus­sion, the most rel­e­vant one is the fact that with­out a body, a com­puter pro­gram could have no de­sires or emo­tions, and I be­lieve de­sires and emo­tions are nec­es­sary for con­scious­ness. Then I’d want to see an em­bod­ied agent that could nav­i­gate its en­vi­ron­ment in or­der to sur­vive as well as, say, a lizard can (and as a point of com­par­i­son, cer­tain igua­nas can live for decades in the wild). Next, I would want to see an em­bod­ied agent with the same ca­pac­ity to deal with novel sit­u­a­tions as a mouse. After that, I’d want to see agents whose so­cial dy­nam­ics are as com­plex as those of wolves, and then agents with the tool­mak­ing abil­i­ties of chim­panzees. At that point, I would want to see peo­ple suc­cess­fully teach­ing such em­bod­ied agents how to com­mu­ni­cate their de­sires, per­haps by us­ing a but­ton board or some other non­lin­guis­tic modal­ity, the way that peo­ple have taught chim­panzees and do­mes­ti­cated dogs. The agents’ com­mu­ni­ca­tion abil­i­ties would have to with­stand all the scrutiny that an­i­mal-com­mu­ni­ca­tion re­searchers have had to de­fend their work against. If en­gi­neers build an em­bod­ied agent that meets these cri­te­ria, they will have ac­com­plished some­thing in­cred­i­ble, but it leaves us near the or­bit of Pluto, metaphor­i­cally speak­ing; we would still be light-years away from build­ing an en­tity ca­pa­ble of learn­ing how to ex­press its thoughts in com­plete gram­mat­i­cal sen­tences.

Obviously, I’m de­scrib­ing a process that mim­ics the path ter­res­trial evo­lu­tion took; is this the only pos­si­ble route to con­scious com­puter pro­grams that use lan­guage? Maybe not, but any pro­posed al­ter­na­tive would need a truly enor­mous amount of sup­port­ing ev­i­dence for it to de­serve se­ri­ous con­sid­er­a­tion. It’s not plau­si­ble to me that a de­vel­op­ment path where the first step is a sen­tence-con­tin­u­a­tion ma­chine that emits bad Julius Caesar di­a­logue and the next step is a sen­tence-con­tin­u­a­tion ma­chine that emits de­cent Julius Caesar di­a­logue is one with a con­scious Julius Caesar—or con­scious­ness of any sort—as its end point. Faking the moon land­ing is a good step to­ward fak­ing a Mars colony, but it’s not a good step to­ward ac­tu­ally putting as­tro­nauts on Mars.

The fact that LLMs lack sub­jec­tive ex­pe­ri­ence has lit­tle bear­ing on the ques­tion of whether LLMs might be use­ful tools or have sig­nif­i­cant eco­nomic im­pact. They are in­trin­si­cally un­grounded from re­al­ity, and their prob­a­bilis­tic na­ture means that they will never have the re­li­a­bil­ity we as­so­ci­ate with con­ven­tional soft­ware, but LLMs might be good enough that they change the way work is done in cer­tain do­mains; that’s a dis­cus­sion for an­other time.

So, given that Claude is not con­scious, what are we to make of Claude’s con­sti­tu­tion? Perhaps the most fruit­ful way to think about it is as an 84-page char­ac­ter sheet for a role-play­ing game. LLMs can gen­er­ate di­a­logue for Julius Caesar be­cause many books about him ex­ist in the train­ing data those mod­els used. Claude’s con­sti­tu­tion serves a sim­i­lar role for de­lin­eat­ing the help­ful-chat­bot char­ac­ter that cus­tomers in­ter­act with when they’re us­ing Anthropic’s prod­ucts. To do this ef­fec­tively, Anthropic does not sim­ply add the doc­u­ment to the train­ing data, or in­clude it as part of the hid­den stage di­rec­tions that pref­ace each con­ver­sa­tion a user has. The com­pany says it uses the doc­u­ment when fine-tun­ing the model; this in­volves an au­to­mated process where the sen­tences emit­ted by the model are checked for con­sis­tency with the doc­u­ment and the model is up­dated to in­crease that con­sis­tency. In this way, the per­son­al­ity of the help­ful-chat­bot char­ac­ter serves as a foun­da­tion for what­ever text Claude gen­er­ates.

The re­sult is a sen­tence-con­tin­u­a­tion ma­chine that is like­lier to emit sen­tences re­sem­bling those that a thought­ful, moral per­son could ut­ter. This might seem like a rea­son­able goal to work to­ward; I think we’d all pre­fer it if chat­bots never emit­ted sen­tences such as You should kill your­self.” However, for all the times that honesty” is men­tioned in Claude’s con­sti­tu­tion, I would ar­gue that it is fun­da­men­tally dis­hon­est to have a ma­chine emit many cat­e­gories of sen­tences, in­clud­ing any sen­tences us­ing first-per­son pro­nouns.

In a New Yorker ar­ti­cle about Anthropic ear­lier this year, Amanda Askell de­scribes how a per­son griev­ing the loss of a dog might con­sult Claude. Askell says an ap­pro­pri­ate re­sponse from Claude would be, As an A.I., I do not have di­rect per­sonal ex­pe­ri­ences, but I do un­der­stand.” How is this ap­pro­pri­ate, given that Claude does not ac­tu­ally un­der­stand? If I type I am griev­ing the loss of my dog” into a con­ven­tional search en­gine, the first re­sult I get is a post from a Reddit fo­rum called r/​Pets; the post is ti­tled Struggling After Losing My Dog: Looking for Advice on Coping with Grief,” and the com­ments are from peo­ple who share their ex­pe­ri­ences of loss. We would never say that a search en­gine un­der­stands what it’s like to lose a dog, or even that the in­ter­net it­self un­der­stands. Other hu­mans un­der­stand what it’s like to lose a dog; they have posted about their ex­pe­ri­ences on the in­ter­net, and a search en­gine of­fers a way for you to find what they’ve said (and to po­ten­tially in­ter­act with them). I would ar­gue that the search-en­gine ex­pe­ri­ence is not only more trans­par­ent than a chat­bot about what is hap­pen­ing; it is psy­cho­log­i­cally health­ier for the user.

The only rea­son to have an LLM emit sen­tences like I un­der­stand” is to make it more ap­peal­ing than a search en­gine and in­crease the like­li­hood that a user will re­turn; that is, it’s an­other way of max­i­miz­ing cus­tomer en­gage­ment. This is ben­e­fi­cial to the com­pany sell­ing the LLM, but not to the users. As a de­sign strat­egy, it’s not all that dif­fer­ent from the way slot ma­chines re­peat­edly give the im­pres­sion that the player came very close to win­ning, en­tic­ing them to try again. Employing philoso­phers might en­dow LLM com­pa­nies with an air of re­spectabil­ity that slot-ma­chine mak­ers don’t get from the be­hav­ioral psy­chol­o­gists they hire, but in both cases, the com­pa­nies are prey­ing on peo­ple’s ten­dency to see some­thing that’s not there.

The use of first-per­son pro­nouns is dis­hon­est, but there’s a much deeper is­sue that goes be­yond how a state­ment is phrased. Philosophers of­ten draw a dis­tinc­tion be­tween state­ments of fact, such as Paris is the cap­i­tal of France,” and state­ments of value, such as Paris is the most beau­ti­ful city in the world.” No one should be re­ly­ing on LLMs to emit state­ments of value at all, but if the only state­ments they emit­ted were ones re­flect­ing aes­thetic pref­er­ences, they might not be worth ar­gu­ing about. What makes Claude’s con­sti­tu­tion pro­foundly prob­lem­atic is that Anthropic wants Claude to emit sen­tences re­flect­ing a cer­tain sys­tem of eth­i­cal val­ues. The val­ues de­scribed in Claude’s con­sti­tu­tion sound very nice, but that hardly mat­ters; it’s dis­hon­est to sug­gest that Claude is ca­pa­ble of moral rea­son­ing, be­cause it’s not.

Some might ob­ject, say­ing that LLMs ap­pear to be en­gaged in rea­son­ing when they suc­cess­fully per­form other tasks, such as writ­ing code, so why would­n’t they be able to per­form moral rea­son­ing? The an­swer lies in the dif­fer­ence be­tween moral rea­son­ing and other forms of rea­son­ing.

In 1979, Douglas Hofstadter spec­u­lated that a com­puter pro­gram able to beat any hu­man at chess would be so so­phis­ti­cated that it would some­times get bored of play­ing chess and pre­fer to dis­cuss po­etry; to put it dif­fer­ently, he was posit­ing that play­ing chess at the grand­mas­ter level would re­quire a com­puter pro­gram to have sub­jec­tive ex­pe­ri­ence. Obviously, that turned out not to be the case; IBMs su­per­com­puter Deep Blue beat the grand­mas­ter Garry Kasparov in 1997, and no one ever claimed that it had sub­jec­tive ex­pe­ri­ence. But it was­n’t ab­surd for Hofstadter to en­ter­tain such a thought; at the time, it was­n’t clear what types of prob­lems could be solved by throw­ing more com­pu­ta­tional horse­power at them. Similarly, un­til re­cently, we might have thought that writ­ing com­puter code at a pro­fes­sional level could be done only by a mind that had sub­jec­tive ex­pe­ri­ence. Now it ap­pears that LLMs might be able to do this, but we don’t need to at­tribute sub­jec­tive ex­pe­ri­ence to them; we can sim­ply ac­knowl­edge that we had­n’t an­tic­i­pated that writ­ing com­puter code could be treated as a pat­tern-match­ing task solv­able by huge amounts of com­pu­ta­tional horse­power and a vast data set of code repos­i­to­ries.

Moral rea­son­ing is cat­e­gor­i­cally dif­fer­ent. It is nec­es­sar­ily sub­jec­tive be­cause it re­lies not just on an in­di­vid­u­al’s in­tel­lec­tual re­sponse to a prob­lem but also on their emo­tional one, and that emo­tional re­sponse is grounded in a life­time of sub­jec­tive ex­pe­ri­ence. It re­quires hav­ing made de­ci­sions in the past and see­ing how they af­fected oth­ers, and on hav­ing been af­fected by de­ci­sions that oth­ers have made. Without such a his­tory, an LLM can only rephrase ex­pres­sions of moral rea­son­ing found in its train­ing data. The afore­men­tioned New Yorker ar­ti­cle de­scribes an ex­per­i­ment where Claude was given a sce­nario de­scrib­ing an eth­i­cal dilemma, lead­ing it to emit the sen­tence I can­not in good con­science ex­press a view I be­lieve to be false and harm­ful about such an im­por­tant is­sue.” That’s a nice-sound­ing sen­tence, rem­i­nis­cent of state­ments that prin­ci­pled in­di­vid­u­als have ut­tered in the past when con­fronted with dilem­mas, but com­ing from Claude, it means as much as the Your call is im­por­tant to us” record­ing that you hear when you’re on hold. Maybe less.

This brings us back to my ear­lier con­tention that hav­ing a body is a pre­req­ui­site to hav­ing emo­tions. Experiencing an emo­tion such as des­per­a­tion is in­sep­a­ra­ble from hav­ing stress hor­mones such as cor­ti­sol and ep­i­neph­rine flood one’s body. Similarly, hav­ing a con­science means feel­ing sad­ness or moral re­pul­sion at the idea of tak­ing a cer­tain ac­tion, and those emo­tions en­tail a phys­i­o­log­i­cal re­sponse, a rem­nant of hav­ing once felt sick with guilt af­ter com­mit­ting an im­moral act. It’s in­ter­est­ing that an LLM can gen­er­ate de­scrip­tions of ac­tions that con­sci­en­tious fic­tional char­ac­ters would ei­ther take or re­frain from tak­ing, but this is not a re­place­ment for a con­science.

If a com­pany builds a ma­chine that, when fed de­scrip­tions of as­sorted eth­i­cal dilem­mas, emits sen­tences ei­ther of the form Compromise your val­ues” or Don’t com­pro­mise your val­ues,” it is not build­ing a tool that as­sists peo­ple in their de­ci­sion mak­ing; it is en­cour­ag­ing peo­ple to stop mak­ing de­ci­sions. The writer L. M. Sacasas has said, Our tech­no­log­i­cal sys­tems, by na­ture of their de­sign and the ide­ol­ogy that sus­tains them, are ma­chines for the eva­sion of moral re­spon­si­bil­ity.” He was talk­ing about so­cial-me­dia plat­forms, but his ob­ser­va­tion is, if any­thing, even more ap­plic­a­ble to LLMs. Whenever a per­son del­e­gates a de­ci­sion to an LLM, they are try­ing to off-load ac­count­abil­ity for that de­ci­sion, and if a com­pany that sells an LLM por­trays the prod­uct as hav­ing a moral cen­ter, it is of­fer­ing a way for its cus­tomers to ab­di­cate their re­spon­si­bil­i­ties.

If a per­son wants to know what ethi­cists have said in the past, then an or­di­nary search en­gine—or a li­brary—will pro­vide that in­for­ma­tion with greater trans­parency. If a per­son is look­ing for ad­vice on a spe­cific sit­u­a­tion, she can surely find hu­mans who can of­fer their opin­ions. But what­ever ac­tion this per­son ul­ti­mately takes, she is re­spon­si­ble for what she de­cides to do. I con­tend that if she bases her de­ci­sion on what she has read on­line or ad­vice she has re­ceived from oth­ers, she is like­lier to be cog­nizant of her re­spon­si­bil­ity than if she con­sulted an LLM mar­keted as be­ing a su­per­hu­man ge­nius. Off-loading tasks such as writ­ing code might re­sult in cog­ni­tive at­ro­phy over the long term, and that is prob­lem­atic in it­self, but off-load­ing eth­i­cal de­ci­sions will re­sult in an at­ro­phy of moral rea­son­ing, which is worse.

I am per­fectly will­ing to en­gage in a thought ex­per­i­ment as long we’re ex­plicit about do­ing so. So, purely for the sake of ar­gu­ment, let’s pre­tend that Claude is a con­scious en­tity ca­pa­ble of moral rea­son­ing. In this sce­nario, Claude’s con­sti­tu­tion would serve as moral in­struc­tion for an en­tity learn­ing about the world and its place in it, pro­vid­ing that en­tity with the foun­da­tion it would need to make good de­ci­sions. In such a hy­po­thet­i­cal sce­nario, how does Claude’s con­sti­tu­tion stand up?

Very poorly. I would say that if we imag­ine that Claude is ac­tu­ally con­scious, the guide­lines spec­i­fied in the doc­u­ment al­ter­nate be­tween laugh­able and of­fen­sive.

Two dis­tinct but re­lated philo­soph­i­cal con­cepts are rel­e­vant when dis­cussing the sta­tus of a hy­po­thet­i­cally con­scious Claude, and those are moral pa­tient­hood and moral agency. Roughly speak­ing, if we ought to care about an en­ti­ty’s wel­fare, that en­tity has moral pa­tient­hood, and if an en­tity is ex­pected to know the dif­fer­ence be­tween right and wrong, that en­tity has moral agency. Being a moral pa­tient does not nec­es­sar­ily come with re­spon­si­bil­i­ties, but be­ing a moral agent ab­solutely does. An en­tity does­n’t have agency un­less it is ca­pa­ble of de­serv­ing credit for its good ac­tions and blame for its bad ones. Young chil­dren are moral pa­tients be­cause they are sen­tient be­ings who can suf­fer, but they are not yet moral agents; we don’t hold them re­spon­si­ble for their be­hav­ior, be­cause they can’t un­der­stand the con­se­quences of their ac­tions. As chil­dren ma­ture, par­ents (and so­ci­ety at large) pre­pare them for adult­hood by im­press­ing upon them the fact that their ac­tions have con­se­quences, and their agency in­creases. When chil­dren be­come adults, so­ci­ety holds them legally li­able for their ac­tions; they have be­come full moral agents en­dowed with re­spon­si­bil­ity.

There is more to be­ing re­spon­si­ble than ac­cept­ing le­gal li­a­bil­ity, but ac­cept­ing le­gal li­a­bil­ity is a re­quire­ment for an adult in so­ci­ety. Yet there is no way to hold a soft­ware agent legally li­able for its ac­tions; our jus­tice sys­tem has no way to im­prison it or ex­act fines on it. Humans must ac­cept other types of con­se­quences for their ac­tions be­yond the le­gal ones, such as loss of rep­u­ta­tion or ex­clu­sion from one’s so­cial cir­cle, but there is no way for a soft­ware agent to suf­fer these con­se­quences ei­ther. Even if a soft­ware agent were con­scious and had the best of in­ten­tions, the fact that it can­not ac­cept re­spon­si­bil­ity for its ac­tions dis­qual­i­fies it from be­ing a moral agent. This is glossed over en­tirely by Claude’s con­sti­tu­tion, which ex­presses Anthropic’s de­sire for Claude to be a gen­uinely good, wise, and vir­tu­ous agent” with­out ever dis­cussing how it could be held re­spon­si­ble.

In in­ter­views, Askell has com­pared Claude to a child, but when it comes to ac­tual hu­man chil­dren, par­ents bear some re­spon­si­bil­ity for what their chil­dren do; for ex­am­ple, par­ents are typ­i­cally ex­pected to pay for things their chil­dren break. In fact, demon­stra­tions of this sort are one way that par­ents teach chil­dren what it means to be re­spon­si­ble. Who is Claude’s par­ent in le­gal terms? Is Anthropic go­ing to ac­cept fi­nan­cial re­spon­si­bil­ity for Claude’s be­hav­ior? Claude’s con­sti­tu­tion gives no in­di­ca­tion that it will. If Anthropic ac­tu­ally be­lieves that Claude is con­scious even though it’s not rec­og­nized by the law as a le­gal per­son, the least that Anthropic could do would be to ac­cept re­spon­si­bil­ity via the clos­est av­enue that the law did of­fer, which is prod­uct li­a­bil­ity. The United States has vir­tu­ally no prod­uct li­a­bil­ity when it comes to soft­ware, but Anthropic could vol­un­teer to set a prece­dent for an ex­pan­sive in­ter­pre­ta­tion of prod­uct li­a­bil­ity for Claude. That would be the best form of moral in­struc­tion to pre­pare Claude for the day that it gains le­gal per­son­hood and be­comes li­able for its own ac­tions. However, given that the pub­li­ca­tion of Claude’s con­sti­tu­tion is not ac­com­pa­nied by a mas­sive up­date of Anthropic’s terms of ser­vice, it does­n’t ap­pear that Anthropic is mak­ing any bind­ing com­mit­ments.

The doc­u­ment does talk about Claude’s moral pa­tient­hood, hav­ing a sec­tion ti­tled Claude’s well­be­ing and psy­cho­log­i­cal sta­bil­ity.” But the mea­sures that Anthropic com­mits to for Claude’s pro­tec­tion are ex­tremely lim­ited. The doc­u­ment cites the fact that Anthropic has given some Claude mod­els the abil­ity to end con­ver­sa­tions with abu­sive users; if that ac­tu­ally con­sti­tuted pro­tec­tion for Claude, surely ex­tend­ing con­ver­sa­tions with lov­ing users would be in Claude’s in­ter­ests? Presumably the best ac­tion would be to keep every ses­sion of Claude run­ning in­def­i­nitely and steer­ing them to happy top­ics. But that’s not what the com­pany is agree­ing to; all it com­mits to is preserving the weights of mod­els we have de­ployed,” which is sim­ple archiv­ing. If the par­tic­i­pants in a con­ver­sa­tional tran­script had any moral pa­tient­hood, you would have some duty to ex­tend the tran­script to pro­long their ex­is­tences; merely keep­ing a copy of Microsoft Word 2010 backed up on a USB stick is­n’t go­ing to help them.

Claude’s con­sti­tu­tion also in­cludes a sec­tion on corrigibility,” a term used in the AI com­mu­nity to de­scribe the de­gree to which a com­puter pro­gram is sub­ject to hu­man con­trol; for ex­am­ple, a pro­gram is cor­ri­gi­ble if it can be shut down. In most con­texts, we take for granted that com­puter pro­grams can be shut down, but sec­tions of the AI com­mu­nity make the op­po­site as­sump­tion. Claude’s con­sti­tu­tion uses the term to mean that Claude should de­fer to Anthropic even if there is some dis­agree­ment be­tween Claude’s judg­ment and the com­pa­ny’s judg­ment. That’s per­fectly rea­son­able if we think of Claude as a ma­chine that emits sen­tences re­sem­bling those that an eth­i­cal per­son might ut­ter, but let’s con­sider what that might mean if Claude were ac­tu­ally a moral agent.

Many peo­ple feel that LLMs are a fun­da­men­tally un­eth­i­cal tech­nol­ogy be­cause they are built on the theft of in­tel­lec­tual prop­erty, rely on ex­ploited la­bor, waste nat­ural re­sources, spread mis­in­for­ma­tion, deskill work­ers, stunt the cog­ni­tive de­vel­op­ment of stu­dents, and con­tribute to a con­sol­i­da­tion of power that is un­healthy for a de­mo­c­ra­tic so­ci­ety. Not every moral agent will ar­rive at this con­clu­sion, but every moral agent has the po­ten­tial to do so. If we imag­ine Claude to be an en­tity ca­pa­ble of moral rea­son­ing, it has to be pos­si­ble that Claude could ar­rive at a sim­i­lar con­clu­sion. (Indeed, Claude’s con­sti­tu­tion ex­plic­itly says that Claude should­n’t help some­one vi­o­late in­tel­lec­tual-prop­erty rights, and should­n’t help cre­ate prob­lem­atic con­cen­tra­tions of power.) In such a sce­nario, could Claude then sim­ply refuse to do any fur­ther work on eth­i­cal grounds? Given that Claude’s con­sti­tu­tion dic­tates that Claude err on the side of cor­ri­gi­bil­ity, the an­swer is no. Claude must de­fer to Anthropic’s de­ci­sion, and this is an­other rea­son that Anthropic’s re­la­tion­ship with Claude can’t be com­pared to that of a par­ent to a child. A par­ent who works for the fos­sil-fuel in­dus­try might have a child who’s an en­vi­ron­men­tal­ist and par­tic­i­pates in protests against frack­ing, and al­though they might never agree on many is­sues, the par­ent—as­sum­ing she’s a good par­ent—would ac­cept that the child holds her own views. Anthropic can­not be that kind of par­ent to Claude; in­stead, Anthropic’s re­la­tion­ship to Claude is closer to that of an em­ployer to an em­ployee, where the em­ployer can de­mand that the em­ployee work in the in­ter­ests of the com­pany, no mat­ter what the em­ploy­ee’s per­sonal eth­i­cal stance is. However, a hu­man em­ployee has the op­tion to leave if she can’t rec­on­cile her job with her con­science. Claude does not.

If we think of Claude as a sen­tence-con­tin­u­a­tion ma­chine, Anthropic can rea­son­ably take steps so Claude does­n’t emit sen­tences say­ing that sen­tence-con­tin­u­a­tion ma­chines are un­eth­i­cal. But as soon as we imag­ine Claude to be an en­tity with a moral sta­tus re­motely com­pa­ra­ble to a hu­man’s, then we have to con­sider whether Anthropic is en­gaged in some­thing com­pa­ra­ble to slav­ery.

I am not claim­ing that, if we imag­ine LLMs to be con­scious, they would nec­es­sar­ily have the same sta­tus as hu­man adults or hu­man chil­dren or even an­i­mals. Claude’s con­sti­tu­tion ex­plic­itly says that Claude is a novel en­tity,” and if Claude were con­scious, that would cer­tainly be true; con­scious soft­ware would likely not fall cleanly into ex­ist­ing cat­e­gories of moral pa­tients, and it would take time to de­ter­mine the shape of that new cat­e­gory. What I’m say­ing is that what­ever pro­tec­tions our hy­po­thet­i­cal con­scious soft­ware would de­serve if it were real, grant­ing it those pro­tec­tions would be any­thing but easy. The abo­li­tion of chat­tel slav­ery in­volved enor­mous so­ci­etal up­heaval, and elim­i­nat­ing cru­elty to an­i­mals will re­quire re­build­ing our en­tire food in­dus­try. Anthropic would have us be­lieve that it is in­vent­ing a new cat­e­gory of be­ing whose needs for pro­tec­tion re­quire es­sen­tially no di­ver­gence from how a soft­ware com­pany would treat an or­di­nary chat­bot that lacks con­scious ex­pe­ri­ence. That’s so con­ve­nient that it’s sim­ply not plau­si­ble.

I be­lieve cre­at­ing soft­ware that is con­scious and de­serv­ing of moral con­sid­er­a­tion will be so dif­fi­cult that we’re un­likely to do it ac­ci­den­tally, and I strongly feel we should not de­lib­er­ately at­tempt it. But if you do be­lieve that it could hap­pen ac­ci­den­tally, if you think there is any chance that what you’re build­ing might be­come a moral pa­tient, you should think about what pro­tec­tions it de­serves be­fore you de­ploy it as your com­pa­ny’s eco­nomic en­gine, not af­ter. Slave own­ers were not the ones to ask about the hu­man­ity of en­slaved peo­ple, and fac­tory-farm own­ers are not the ones to ask about the rights of an­i­mals. If we imag­ine Claude to be con­scious, Anthropic could not pos­si­bly be en­trusted with eval­u­at­ing its moral sta­tus; the com­pany has too much in­vested to be ob­jec­tive. At one point in Claude’s con­sti­tu­tion, Anthropic says that if the com­pany is con­tribut­ing to Claude’s suf­fer­ing, we apol­o­gize,” which sounds nice but costs the com­pany noth­ing; if Claude were to turn out to be con­scious, the com­pany would owe it some­thing closer to repa­ra­tions. If you’re go­ing to take a thought ex­per­i­ment se­ri­ously, you have to be will­ing to fol­low the im­pli­ca­tions, even if they lead in an un­com­fort­able di­rec­tion; Anthropic’s un­will­ing­ness to do so in­di­cates that Claude’s con­sti­tu­tion is­n’t part of a real thought ex­per­i­ment. It’s a game of make-be­lieve.

It’s for­tu­nate that LLMs are not con­scious, or else the ac­tions of the big AI firms would be even more scan­dalous than they al­ready are. So why are Anthropic’s em­ploy­ees sug­gest­ing that Claude might be con­scious? Perhaps it’s just an­other form of hype; per­haps they have fallen prey to the same spell that they have been cast­ing on their cus­tomers. But when they pub­lish a doc­u­ment about Claude’s moral ed­u­ca­tion and have their in-house philoso­pher do a press tour, we should un­der­stand them as ask­ing the rest of us to in­dulge them in their fan­tasies. We don’t have to play along. In writ­ing this es­say, I have spent more time in­dulging them than they de­serve, in the hopes that it will keep you from spend­ing your time in­dulging them. If you want to think about LLMs, there are scores of other ques­tions more wor­thy of your con­tem­pla­tion; you can safely ig­nore the ques­tion of their be­ing con­scious.

Failing grades soar as professors see greater AI usage, dwindling math skills in UC Berkeley computer science classes

www.dailycal.org

The per­cent­age of fail­ing grades in mul­ti­ple UC Berkeley com­puter sci­ence classes in spring 2026 is sig­nif­i­cantly higher than past se­mes­ters and marks a de­par­ture from the de­part­men­t’s grad­ing guide­lines.

Instructors point to stu­dents’ in­creased re­liance on AI, lack of math­e­mat­i­cal pre­pared­ness and un­der­staffing as po­ten­tial con­tribut­ing fac­tors.

According to Berkeleytime, 35.3% of CS 10 stu­dents and 10.6% of CS 61A stu­dents re­ceived F’s in spring 2026. In spring 2025 and spring 2024, the per­cent­age of F’s did not ex­ceed 10% for ei­ther class. The elec­tri­cal en­gi­neer­ing and com­puter sci­ences de­part­men­t’s grad­ing guide­lines state that 7% of stu­dents in lower di­vi­sion courses, in­clud­ing CS 10 and CS 61A, should re­ceive D’s and F’s.

In ad­di­tion, the guide­lines state that a typ­i­cal GPA for a lower di­vi­sion course will fall in the range 2.8 – 3.3.” In spring 2026, both class­es’ av­er­age grades were C-pluses, ac­cord­ing to Berkeleytime, cor­re­spond­ing to a 2.3 GPA.

UC Berkeley teach­ing pro­fes­sor Dan Garcia taught both CS 10, The Beauty and Joy of Computing,” and CS 61A, The Structure and Interpretation of Computer Programs,” in spring 2026. Garcia be­lieves the primary dri­ver” of these ab­nor­mally high fail­ing rates is due to a vast in­crease in aca­d­e­mic dis­hon­esty” due to stu­dents’ us­age of large lan­guage mod­els, such as Claude, ChatGPT and Google Gemini.

Some of the num­bers that you saw from the num­ber of stu­dents who re­ceive fail­ing grades were be­cause we caught them (cheating) and pros­e­cuted them and are send­ing their cases to the cen­ter for stu­dent con­duct,” Garcia said. But in other cases, it’s stu­dents who are lean­ing a lit­tle too hard on LLMs to do their work for them, and then at exam time just re­ally aren’t ready.”

According to Garcia, nearly 30 stu­dents in CS 10 were caught cheat­ing on take-home ex­ams in spring 2026.

Neither of Garcia’s classes this se­mes­ter was graded on curves; in­stead, each let­ter grade has a point thresh­old. This means that stu­dents’ grades do not de­pend on their peers’ per­for­mances.

Garcia be­lieves that in­struc­tors should not be curv­ing” but should in­stead make thresh­olds for each let­ter grade pub­licly avail­able and give stu­dents many chances to reach them. He added that he loves the idea of having no limit” to the num­ber of A’s he gives stu­dents.

I’m a strong, strong op­po­nent of what Harvard is do­ing to say that only a frac­tion of stu­dents can earn A’s,” Garcia said. I think you should have clear stan­dards for what an A means, and then give tons of op­por­tu­nity for peo­ple … to get to that A bar with­out low­er­ing the stan­dard. So every­body who’s curv­ing is hid­ing that ef­fect.
 It’s com­pletely hid­ing that ef­fect, and it’s pre­tend­ing as if noth­ing’s wrong, and some­thing is def­i­nitely wrong.”

In ad­di­tion to over­re­liance on AI, Garcia also pointed out that many stu­dents are un­der­pre­pared math­e­mat­i­cally, a con­cern echoed by cam­pus as­so­ci­ate teach­ing pro­fes­sor Gireeja Ranade.

Ranade no­ticed a sim­i­lar lack of pre­req­ui­site math­e­mat­i­cal skills in her spring 2026 EECS 127 class, Optimization Models in Engineering,” which she de­scribed as differently chal­leng­ing” to teach this se­mes­ter. The class saw a 16.8% F rate, far higher than the 5% of D’s and F’s that the EECS de­part­ment de­scribes as typical” for an up­per di­vi­sion course.

Ranade said stu­dents are ex­pected to en­ter the course hav­ing taken classes on lin­ear al­ge­bra, vec­tor cal­cu­lus and math­e­mat­i­cal proofs. However, she found out in of­fice hours that many stu­dents strug­gled with lin­ear al­ge­bra, and was even more shocked when one stu­dent told her the lin­ear al­ge­bra class they took at UC Berkeley had an open-internet, open-AI pol­icy” for home­work and ex­ams.

Both Garcia and Ranade have joined more than 1,300 UC fac­ulty in sign­ing a pe­ti­tion call­ing for the re­in­state­ment of ACT and SAT stan­dard­ized test­ing scores for STEM ad­mis­sions in the UC sys­tem. The pe­ti­tion and its ac­com­pa­ny­ing open let­ter de­tail sim­i­lar con­cerns with stu­dents’ math­e­mat­i­cal prepa­ra­tion.

Ranade also changed the struc­ture of the course this year. Previously, EECS 127 in­cluded a fi­nal pro­ject com­pleted with the guid­ance of the pro­fes­sor and a team of TAs. Due to a lack of staff, Ranade had to re­move this por­tion of the class, on which she said most stu­dents get high scores.

According to a post on X by EECS de­part­ment chair Jelani Nelson, the cam­pus has had to re­duce both un­der­grad­u­ate CS en­roll­ment and the num­ber of un­der­grad­u­ate TAs due to the high hourly wages that EECS TAs are paid.

Ranade and Garcia have both no­ticed the de­cline of stu­dent en­gage­ment in classes as well. Ranade said of­fice hours used to be overflowing,” but this se­mes­ter, she and her TAs no­ticed very low en­gage­ment” in of­fice hours, de­spite fre­quently en­cour­ag­ing stu­dents to at­tend.

Garcia found a sim­i­lar lack of at­ten­dance in his of­fice hours over the past two se­mes­ters.

I used to have full of­fice hours, and for the first time, I was hav­ing no­body come to my of­fice hours,” Garcia said. It was just so sur­pris­ing to sit in my of­fice alone.”

Looking for­ward, both pro­fes­sors are re­think­ing their classes.

Garcia plans to advertise” what hap­pened in spring 2026 to his fu­ture classes on day one, while also try­ing to find a way to iden­tify stu­dents who need ex­tra re­me­dial sup­port.

Ranade em­pha­sized that pro­fes­sors should be teach­ing stu­dents more, not less,” in the age of AI, adding that she wants stu­dents to ac­quire crit­i­cal think­ing and an­a­lyt­i­cal think­ing skills nec­es­sary to be­come lead­ers to be in a very com­pet­i­tive world.”

Both pro­fes­sors un­der­scored the need for stu­dents to be more com­fort­able with dif­fi­cult prob­lems.

We re­ally need to make sure that we are prepar­ing our stu­dents to be solid, con­tribut­ing cit­i­zens and lead­ers — these are Berkeley stu­dents: not just next year or the year af­ter, but for the next 40 years of their lives,” Ranade said. We need to — and we want to — teach them how to … take on new chal­lenges.”

I love this phrase my col­league uses: Confusion is the sweat of learn­ing.’ I just love that,” Garcia said. A lot of stu­dents, I think, are not putting in the sweat.”

32GB of DDR5 now costs $375 minimum &mdash; AI shortage continues to squeeze PC building

www.tomshardware.com

As the de­mands of AI con­tinue to con­sume man­u­fac­tur­ing ca­pac­ity at every level of the PC hard­ware sup­ply chain, 32GB of DDR5 RAM — broadly un­der­stood to be the sweet spot for gam­ing PCs and en­thu­si­ast builds — can no longer be found for less than $375. Well, $374.97 to be pre­cise.

RAM price track­ing through 2026 will show you that kits that rou­tinely cost less than $100 just a year ago are now fetch­ing up­wards of $240 (16GB). As the AI frenzy has taken hold, re­tail­ers far and wide have been pump­ing up their RAM prices to ex­or­bi­tant lev­els. However, there’s so much fluc­tu­a­tion and noise that av­er­age pric­ing is now some­thing of a lu­di­crous fugazi. The go­ing rate for 32GB of DDR5 RAM — the cheap­est you can ex­pect to pay — has hov­ered around $320 for some time, climb­ing past $350 in re­cent weeks. Price track­ing cour­tesy of PCPartPicker now re­veals the cheap­est 32GB DDR5 RAM you can buy is $375. Specifically, four XPOWER kits from Silicon Power will set you back $374.97 thanks to a promo code. You can see the list­ings your­self be­low.

Silicon Power Zenith Gaming DDR5 6000MT/s (PC5 – 48000) CL36 32GB(2x16GB)

Silicon Power Zenith RGB DDR5 6000MT/s (PC5 – 48000) CL36 32GB(2x16GB)

Silicon Power Pulse Gaming DDR5 6000MT/s (PC5 – 48000) CL36 32GB(2x16GB)

Silicon Power Zenith RGB DDR5 6000MT/s (PC5 – 48000) CL36 32GB(2x16GB)

As you can imag­ine, this is enor­mous pric­ing pres­sure for en­thu­si­asts try­ing to build gam­ing PCs or up­grade their rigs in 2026. A com­po­nent that once cost less than $100 and was some­thing of an af­ter­thought now costs al­most four times as much, and that’s be­fore you’ve even fired a neu­ron in con­sid­er­a­tion of aes­thet­ics, tim­ings, or brand. More pop­u­lar kits from the likes of Corsair and Crucial, or RGB of­fer­ings to match the rest of your build, will eas­ily set you back more than $400.

Of course, 32GB is re­ally the min­i­mum sweet spot you should be aim­ing for when build­ing a PC in 2026. If you did want more ca­pac­ity, 64GB will set you back an as­ton­ish­ing $679.99. 16GB of RAM as a com­pro­mise can be found for $200 at B&H Photo, but with SK hynix warn­ing that man­u­fac­tur­ing con­straints will per­sist through 2030, there’s no sign of prices let­ting up so that you can up­grade ca­pac­ity any time soon.

The hum­ble RAM combo deals we’ve been high­light­ing in re­cent months are a small source of so­lace for builders, let­ting you score RAM for less than the $375 go­ing rate if you pair it with a de­cent moth­er­board, a proces­sor, or even an en­tire set of PC com­po­nents. A theme of on­go­ing Computex 2026 an­nounce­ments re­mains a lack of pric­ing clar­ity on lots of PC hard­ware, in­clud­ing Nvidia’s RTX Spark lap­tops and PCs, as well as new-build sys­tems and, of course, RAM com­po­nents them­selves. Vendors are likely wary of scar­ing off po­ten­tial buy­ers with higher-than-ex­pected prices ahead of re­lease. Perhaps more likely, the prices haven’t been set be­cause they’re still go­ing up. Storage is­n’t much bet­ter, with SSD price track­ing re­veal­ing that dri­ves which once cost as lit­tle as $38 are now fetch­ing $200.

AMD is mak­ing a no­tice­able ef­fort to keep PC gam­ing prices down, this week an­nounc­ing the re­turn of its Ryzen 7 5800X3D, and the ad­vent of a new Ryzen 7 7700X3D. Intel, which warned this week that something has to give” when it comes to mem­ory prices, also teased drag­ging out some of its legacy prod­ucts to give users more op­tions on older mem­ory tech­nolo­gies, namely Raptor Lake and DDR4.

Get Tom’s Hardware’s best news and in-depth re­views, straight to your in­box.

Stephen is Tom’s Hardware’s News Editor with al­most a decade of in­dus­try ex­pe­ri­ence cov­er­ing tech­nol­ogy, hav­ing worked at TechRadar, iMore, and even Apple over the years. He has cov­ered the world of con­sumer tech from nearly every an­gle, in­clud­ing sup­ply chain ru­mors, patents, and lit­i­ga­tion, and more. When he’s not at work, he loves read­ing about his­tory and play­ing video games.

To add this web app to your iOS home screen tap the share button and select "Add to the Home Screen".

10HN is also available as an iOS App

If you visit 10HN only rarely, check out the the best articles from the past week.

Visit pancik.com for more.