10 interesting stories served every morning and every evening.

Resetting XBOX

news.xbox.com

This mes­sage was just sent to Team XBOX em­ploy­ees glob­ally.

Team,

We are be­gin­ning the most sig­nif­i­cant re­struc­ture in XBOX his­tory. After care­ful con­sid­er­a­tion, I’ve made the dif­fi­cult de­ci­sion to re­duce our team by ap­prox­i­mately 3,200 through­out FY27. This will in­clude ap­prox­i­mately 1,600 role elim­i­na­tions to­day, and in ad­di­tion, four stu­dios will leave XBOX to new man­age­ment. I rec­og­nize that a year-long re­struc­tur­ing cre­ates ad­di­tional chal­lenges. Unfortunately, it is not pos­si­ble to make all the nec­es­sary changes in a sin­gle day, and I wanted to be di­rect about the scale.

I know this is painful. These changes will di­rectly af­fect peo­ple who have poured their cre­ativ­ity into build­ing XBOX. Many joined us through ac­qui­si­tions, while oth­ers were re­cruited here, or sought us out be­cause they loved this in­dus­try and loved XBOX. Today’s de­ci­sions do not re­flect their tal­ent or ded­i­ca­tion.

Our busi­ness to­day is not healthy. We are op­er­at­ing at mar­gins that are 3 – 10x lower than com­pa­ra­ble plat­form and pub­lish­ing busi­nesses. We en­tered Gen 9 with a smaller in­stall base and a higher cost struc­ture. To grow, we bet on Game Pass, multi-plat­form, and a broader port­fo­lio of con­tent. While those busi­nesses have cre­ated mean­ing­ful value, they did not grow at the pace we ex­pected. As that hap­pened, our core busi­ness weak­ened, and we added more teams, more in­vest­ment, and more time, hop­ing for a bet­ter out­come. And now the in­dus­try is fac­ing the most se­vere hard­ware cri­sis in its his­tory. We must re­set XBOX.

First, we will re­set our con­tent port­fo­lio.

Since 2018, we have ag­gres­sively ex­panded our stu­dio port­fo­lio while the num­ber of games cre­ated each month across the in­dus­try now out­paces the last ten years com­bined. We now find our­selves com­pet­ing not only with the largest pub­lish­ers, but also with smaller in­de­pen­dent stu­dios. It is nei­ther pos­si­ble nor de­sir­able to own every great in­de­pen­dent stu­dio. We have also learned that we are not the best home for every type of stu­dio; in a typ­i­cal year, we lost 64 cents for every dol­lar we in­vested. As we re­set XBOX, we will help in­de­pen­dent cre­ators suc­ceed by pro­vid­ing open de­vel­op­ment tools and au­di­ences to re­al­ize their vi­sion.

Compulsion Games and Double Fine Productions will re­turn to man­age­ment and tran­si­tion to in­de­pen­dent stu­dios with their IP, cat­a­log, and run­way for their next games. Ninja Theory and Undead Labs have en­tered terms to join new own­er­ship with fund­ing to com­plete and grow Senua and State of Decay 3. In France, Arkane’s man­age­ment is be­gin­ning re­quired con­sul­ta­tion with its Works Council to re­view po­ten­tial strate­gic op­tions.

We are also mak­ing re­duc­tions across other units, and in some cases, shift­ing in­vest­ment to fo­cus on higher pri­or­ity pro­jects. These changes vary in size across Activision, Bethesda/ZeniMax, Blizzard, King, Mojang, and XBOX Game Studios. None of our first party pub­licly an­nounced games or pro­jects are be­ing can­celled as part of these re­duc­tions.

In ad­di­tion, Mojang and King will now re­port di­rectly to me. These two stu­dios have in­creas­ingly be­come plat­forms and are our largest by monthly ac­tive play­ers. They bring crit­i­cal ge­o­graphic, de­mo­graphic, and dif­fer­en­ti­a­tion to XBOX.

Second, we will re­set our plat­form.

We know that great tech­nol­ogy gets bet­ter when it gets sim­pler, not big­ger. Today, in some parts of the com­pany, work passes through as many as 14 lay­ers of man­age­ment. Our plat­form teams are 40% larger than they were at the start of this gen­er­a­tion, even as our player base and play­time have de­clined. That com­plex­ity has slowed de­ci­sions, blurred ac­count­abil­ity, and made it harder to de­liver for play­ers. As we re­set XBOX, we will sim­plify.

We will re­duce man­age­ment lay­ers to no more than 5, and where pos­si­ble, 3. We will de­liver suc­cess through a flat­ter or­ga­ni­za­tion that is built around mak­ers (individual con­trib­u­tors fo­cused on build­ing), player-coaches (leaders who re­main deeply in­volved in the work while de­vel­op­ing their teams), and di­rectly re­spon­si­ble in­di­vid­u­als (DRIs) who own key de­ci­sions and out­comes. And we will stream­line how we work across our tools, with a cleaner code base, shared ser­vices, and 50% re­duced ven­dor spend.

Third, we are re­set­ting how we op­er­ate.

As XBOX grew our head­count, we be­came more frag­mented. Teams, stu­dios, and func­tions of­ten op­er­ate in­de­pen­dently, and it be­came harder to work to­wards a shared goal, make the right trade­offs, and get things done.

For the first time, we are es­tab­lish­ing a Chief Operating Officer with end-to-end P&L re­spon­si­bil­ity across con­tent, hard­ware, plat­form, and ser­vices. Helen Chiang has been pro­moted to this role and will re­port di­rectly to me. Over nearly two decades at XBOX, Helen has helped build some of our most im­por­tant busi­nesses, from XBOX Live to lead­ing Mojang and the Minecraft fran­chise. She will bring our busi­nesses to­gether un­der one op­er­at­ing model, mak­ing sure we make clear in­vest­ment de­ci­sions, learn from our suc­cesses and fail­ures, and hold our­selves ac­count­able for re­sults.

Thank you, Dave McCarthy, who is re­tir­ing af­ter 17 years with XBOX. Dave has played a defin­ing role in build­ing the plat­form that mil­lions of play­ers rely on every day and has been a trusted part­ner through many of the biggest mo­ments in XBOXs his­tory. We wish him all the best.

These changes are about a big­ger fu­ture for XBOX, not a smaller one. The next decade of gam­ing will be larger, more global, and more cre­ative than any­thing we’ve seen be­fore. This year, we’ll in­vest as much in XBOX as we ever have, but we’ll in­vest with greater fo­cus, greater dis­ci­pline, and greater clar­ity, all in ser­vice of mak­ing XBOX where the world plays and cre­ates.

I want XBOX to be one of the few com­pa­nies that en­ter­tains more than a bil­lion peo­ple each day and gives every­one the op­por­tu­nity to cre­ate and con­nect. I know we can achieve this goal. XBOX has many of the most beloved fran­chises in en­ter­tain­ment his­tory, tal­ented stu­dios around the world, and we will re­turn to growth in 2027.

History is full of com­pa­nies that mis­take longevity for in­evitabil­ity. We will not be one of them.

Asha

Live Train Map

www.map.signalbox.io

Castro Podcasts — Things I got wrong: Support

www.uncommonapps.nyc

I had an idea when I bought Castro that hu­man sup­port based around ac­tual user ex­pe­ri­ence was an easy dif­fer­en­tia­tor. I’ve rarely got­ten use­ful an­swers from sup­port from ser­vices I use. I thought if I used my own prod­uct every day, read every email and an­swered it thought­fully, peo­ple would ap­pre­ci­ate this, and it would build some de­gree of loy­alty and ap­pre­ci­a­tion. This way, cus­tomers would feel their sub­scrip­tion dol­lars were ac­tu­ally go­ing to­ward some­thing. When emails over­whelmed me, I asked a thought­ful user who emailed fre­quently and seemed to know as much about the prod­uct as I did if he’d help an­swer the emails, so I paid him to do that. And he did a great job, es­pe­cially in terms of di­rectly solv­ing user prob­lems.

However, what I found is this whole thing did­n’t work as I thought it would. Sure some­times we were able to wow cus­tomers, par­tic­u­larly when we re­sponded right away with an ex­act fix for them. But the vast ma­jor­ity of our hon­est, thought­ful an­swers were deeply un­sat­is­fac­tory to users, and it of­ten an­noyed them more than any­thing else.

Here are my un­sci­en­tific cat­e­gories of sup­port re­quests/​emails we get and why the ap­proach is flawed.

Complaints about sub­scrip­tions and pric­ing

I have al­ready thought about this a great deal. I am not chang­ing any­thing based on your email. I can of course try to jus­tify why we charge what we do, and I’m happy to ex­plain why an es­sen­tial app is worth your money, and why soft­ware lends it­self to sub­scrip­tion so well. But in re­al­ity the user is not sat­is­fied with this. I can think of ex­actly one cus­tomer in two years who was sur­prised that soft­ware costs money and we’re ac­tu­ally do­ing work every day, thus charg­ing a sub­scrip­tion makes sense. 99% of the time, no mat­ter how care­fully or kindly it’s ex­plained, the re­ply will be more neg­a­tive than the ini­tial email. I tried just of­fer­ing an ad­di­tional 30-day trial to any­one who asked, but this did­n’t change the sen­ti­ment of the emails, and those tri­als had a sub­stan­tially lower hit rate than our typ­i­cal free tri­als. I could fill sev­eral blog posts with thoughts on sub­scrip­tions, but suf­fice it to say, emails about pric­ing are not help­ful in terms of build­ing rap­port.

Bugs

These emails are gen­uinely use­ful to me, the re­ceiver. I want to know about the bugs peo­ple are ex­pe­ri­enc­ing on a daily ba­sis. In the best case, I can say we know about this and are ac­tively work­ing on a fix or have al­ready fixed it. Due to the way ship­ping works in the App Store, it’s com­mon for a bug to be fixed but not dis­trib­uted yet. Those are great emails to an­swer and we can sat­isfy the cus­tomer.

But there’s a long tail of bugs that are not like this:

We have heard this be­fore, but we can­not see it or repli­cate it. The user gets to do work for us and/​or get no res­o­lu­tion. Bad ex­pe­ri­ence for them, bad ex­pe­ri­ence for us, mostly a waste of every­one’s time. Very, very oc­ca­sion­ally a user will send a de­tailed re­port with steps to re­pro­duce or a mean­ing­ful fac­tor. Still we need to get these emails to know what peo­ple are see­ing.

We have heard this be­fore, but we can­not see it or repli­cate it. The user gets to do work for us and/​or get no res­o­lu­tion. Bad ex­pe­ri­ence for them, bad ex­pe­ri­ence for us, mostly a waste of every­one’s time. Very, very oc­ca­sion­ally a user will send a de­tailed re­port with steps to re­pro­duce or a mean­ing­ful fac­tor. Still we need to get these emails to know what peo­ple are see­ing.

We have never heard this be­fore. User can pro­vide de­tails for us, but if oth­ers aren’t ex­pe­ri­enc­ing it, it’s un­likely to be pri­or­i­tized. Still, use­ful sig­nal for us.

We have never heard this be­fore. User can pro­vide de­tails for us, but if oth­ers aren’t ex­pe­ri­enc­ing it, it’s un­likely to be pri­or­i­tized. Still, use­ful sig­nal for us.

We get no in­for­ma­tion. It does­n’t work” is the whole email. Not much I can do with­out the user do­ing more work, which they un­der­stand­ably aren’t in­ter­ested in do­ing.

We get no in­for­ma­tion. It does­n’t work” is the whole email. Not much I can do with­out the user do­ing more work, which they un­der­stand­ably aren’t in­ter­ested in do­ing.

We know about this, but fix­ing it is a de­cent amount of work or low-pri­or­ity be­cause it’s not a big deal or few users see it.

We know about this, but fix­ing it is a de­cent amount of work or low-pri­or­ity be­cause it’s not a big deal or few users see it.

None of these cat­e­gories seem to build any mean­ing­ful rap­port. Any hon­est an­swer I give is deeply un­sat­is­fy­ing to both par­ties, and we typ­i­cally have bet­ter data from teleme­try or crash logs than the emails pro­vide. It’s cer­tainly use­ful for us to re­ceive them, but there’s not a help­ful re­sponse I can give. In ret­ro­spect, this seems ob­vi­ous, but be­fore own­ing Castro it was not ob­vi­ous to me that a hu­man re­sponse de­tail­ing why I am un­able to solve your prob­lem to­day and am not even go­ing to try is about the worst thing a user can re­ceive!

Nuanced ques­tions / hu­man in­ter­ven­tion

Sometimes we get nu­anced ques­tions about App Store processes, store is­sues, spe­cific lo­cales, hy­per-spe­cific pod­cast ques­tions, etc. A user re­cently had a Castro sub­scrip­tion on two dif­fer­ent ac­counts at dif­fer­ent times and wanted to let one ex­pire while en­sur­ing they got the months they paid for. We were able to re­solve it for them quickly. People do gen­uinely ap­pre­ci­ate this kind of re­spon­sive­ness. So yeah, the idea prob­a­bly works here. Unfortunately, these are less than 1% of sup­port emails.

Customers gen­uinely con­fused / some­thing un­clear

This comes clos­est to build­ing the cus­tomer re­la­tion­ships I was hop­ing for, with the worst re­sults. Customers email us with con­fu­sion about how pod­casts work, how the App Store works, how their Mac works, and any num­ber of tan­gen­tial is­sues. What tends to hap­pen is the same users do this over and over, and once they find out we an­swer, the re­quests get more fre­quent and more bur­den­some. I think I heard Patrick McKenzie use the term pathological cus­tomers”. While in the­ory build­ing rap­port and loy­alty sounds nice, what you ac­tu­ally end up do­ing is spend­ing a lot of time on the peo­ple who ask the most of you, but their sub­scrip­tion dol­lars aren’t worth more, and they’re rarely sat­is­fied. You end up feel­ing taken ad­van­tage of.

Feature re­quests / gen­eral thoughts

Similar to the last cat­e­gory. Good in the­ory, some­times use­ful, but of­ten the same small, un­rep­re­sen­ta­tive seg­ment with strong thoughts. Woe to the team who im­ple­ments a sug­ges­tion based on an email, you are likely to get a full prod­uct roadmap soon!

Castro is an opin­ion­ated app and I’ve thought a lot about what we’re build­ing and what we’re go­ing to work on next. It’s un­likely I’m go­ing to im­ple­ment the re­quest. If I did, by cater­ing more to per­snick­ety power users, we run the risk of alien­at­ing newer users who don’t know how things work. But our power users prob­a­bly aren’t go­ing any­where, at least they’re a lit­tle harder to shake, and alien­at­ing new users is the death of the prod­uct.

To the user, any re­sponse aside from Okay, we’re go­ing to build that right now” is meh-to-neg­a­tive. Various hon­est re­sponses, such as I thought about this or tried it in the past and it un­for­tu­nately did­n’t work very well” are not go­ing to knock their socks off. These just don’t do much in terms of loy­alty and rap­port.

Conclusion

Ultimately, for us, putting too much time into sup­port is­n’t a dif­fer­en­tia­tor, and it’s of­ten counter-pro­duc­tive. The per­son who paid our sub­scrip­tion but would never think about email­ing us and ask­ing for some­thing for free de­serves a great app just as much as the per­son who emails us every week. If we have a spe­cific res­o­lu­tion or fix for their prob­lem, great. If not, we’ve had bet­ter re­sults by say­ing we ap­pre­ci­ate the email, we read them, and we are ac­tively work­ing on the prod­uct to im­prove the is­sues. Avoiding ex­pla­na­tions and specifics tends to get a neu­tral re­sponse and does­n’t suck any­one in or waste too much time. In other words, the best ap­proach for us is what most com­pa­nies do. Because build­ing loy­alty or rap­port at the mo­ment some­thing is­n’t work­ing and the user is frus­trated has­n’t worked. The real pos­i­tive ex­pe­ri­ence comes when you ac­tu­ally im­prove the prod­uct, so that’s where we’re spend­ing our time.

Information about upcoming battery-related revisions to some Nintendo products

www.nintendo.com

Starting sum­mer 2026, in prepa­ra­tion for up­com­ing changes in European bat­tery reg­u­la­tions com­ing into ef­fect in mid-Feb­ru­ary 2027, se­lected Nintendo prod­ucts in Europe will be­gin to be re­placed on a rolling ba­sis by re­vi­sions that con­tain a user-re­place­able bat­tery. There is no dif­fer­ence in func­tion­al­ity be­tween cur­rent prod­ucts and re­vised prod­ucts con­tain­ing user-re­place­able bat­ter­ies.

The first re­vised prod­ucts are ex­pected to be­come avail­able from sum­mer 2026, with ad­di­tional prod­ucts be­com­ing avail­able in au­tumn, win­ter, and early 2027. Due to a va­ri­ety of fac­tors, re­vised prod­ucts may not be­come avail­able in all European coun­tries si­mul­ta­ne­ously.

The table be­low shows the es­ti­mated ear­li­est avail­abil­ity in Nintendo Store, al­though please note that these tim­ings may change de­pend­ing on man­u­fac­tur­ing, dis­tri­b­u­tion, and other fac­tors. Availability at re­tail­ers may also vary, so please check with your lo­cal re­tail­ers in the fu­ture for more in­for­ma­tion.

Joy-Con pair (selected colours) Joy-Con (L) Neon Blue Joy-Con (R) Neon Red

Different colours will be avail­able at dif­fer­ent times through­out the year, start­ing from sum­mer

Battery ca­pac­ity: No change

Weight: No change

Nintendo Switch 2 con­sole

Autumn

Battery ca­pac­ity: 5172mAh, ap­prox­i­mately 1% smaller than cur­rent ver­sion (5220mAh) The in­cluded Joy-Con 2 con­trollers will also con­tain user-re­place­able bat­ter­ies.

Weight: Approximately 411g, around 10g heav­ier than cur­rent ver­sion (approximately 401g).

With Joy-Con 2 con­trollers at­tached: Approximately 548g, around 14g heav­ier than cur­rent ver­sion (approximately 534g).

This win­ter

Battery ca­pac­ity: No change.

Weight:

Joy-Con 2 (L): Approximately 68g, around 2g heav­ier than cur­rent ver­sion (approximately 66g).

Joy-Con 2 (R): Approximately 69g, around 2g heav­ier than cur­rent ver­sion (approximately 67g).

This win­ter

Battery ca­pac­ity: 897mAh, ap­prox­i­mately 16% smaller than cur­rent ver­sion (1070mAh).

Weight: Approximately 228g, around 7g lighter than cur­rent ver­sion (approximately 235g).

Early 2027

Battery ca­pac­ity: No change.

Weight: Approximately 234g, around 1g heav­ier than cur­rent ver­sion (approximately 233g).

Early 2027

Battery ca­pac­ity: 525mAh, ap­prox­i­mately 5% larger than cur­rent ver­sion (500mAh).

Weight: 215g, around 5g heav­ier than cur­rent ver­sion (210g).

More in­for­ma­tion will be shared shortly be­fore each re­vised prod­uct be­comes avail­able.

Battery re­place­ment kits for each prod­uct will be avail­able to pur­chase from Nintendo Store in Europe in the fu­ture.

Frequently asked ques­tions

In which coun­tries will these re­vised prod­ucts be sold?

The re­vised prod­ucts will be avail­able on a rolling ba­sis in ter­ri­to­ries where Nintendo of Europe con­ducts busi­ness, ei­ther di­rectly or through a dis­trib­u­tor, namely: Austria, Belgium, Bulgaria, Croatia, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Kingdom of Saudi Arabia, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Oman, Poland, Portugal, Romania, Slovakia, Slovenia, South Africa, Spain, Sweden, Switzerland, United Arab Emirates, and the United Kingdom.

Will I be able to choose which ver­sion I buy?

As prod­ucts will be re­placed on a rolling ba­sis, it will not be pos­si­ble to choose when buy­ing on Nintendo Store: when the cur­rent ver­sion of a par­tic­u­lar prod­uct is sold out, it will be re­placed by the re­vised ver­sion.

For re­tail­ers, please con­tact your lo­cal re­tailer for more in­for­ma­tion.

Can you be more spe­cific with the time frames?

The cur­rent es­ti­mated tim­ings may change, de­pend­ing on man­u­fac­tur­ing, dis­tri­b­u­tion, and other fac­tors. More in­for­ma­tion will be shared shortly be­fore each re­vised prod­uct be­comes avail­able.

I al­ready own one of these prod­ucts — are they no longer com­pli­ant? Do I need to do any­thing?

The up­com­ing changes in European bat­tery reg­u­la­tions com­ing into ef­fect in mid-Feb­ru­ary 2027 don’t af­fect prod­ucts sold be­fore that time, so there’s no need to do any­thing.

What about other prod­ucts that aren’t listed in the table?

The be­low prod­ucts will not be re­placed by ver­sions that con­tain user-re­place­able bat­ter­ies in Europe:

Nintendo Entertainment System (NES) Controller for Nintendo Switch*

Pokémon™ GO Plus +

Nintendo Switch

Nintendo Switch Lite

Nintendo Switch — OLED Model

Nintendo Switch Pro Controller

SEGA Mega Drive Control Pad for Nintendo Switch*

Super Nintendo Entertainment System (SNES) Controller for Nintendo Switch*

Nintendo will no longer of­fer the above-named prod­ucts on Nintendo Store af­ter mid-Feb­ru­ary 2027. Regarding avail­abil­ity at re­tail, please check with your lo­cal re­tail­ers in the fu­ture for more in­for­ma­tion. Products marked with * are only avail­able on Nintendo Store.

What does that mean for Nintendo Switch con­soles in Europe?

Nintendo Switch, Nintendo Switch Lite, and Nintendo Switch — OLED Model will all con­tinue to be man­u­fac­tured in 2026, and should be widely avail­able in Europe all year.

From mid-Feb­ru­ary 2027, al­most ten years af­ter Nintendo Switch launched in March 2017, Nintendo will no longer sell to re­tail­ers hard­ware in the Nintendo Switch fam­ily of sys­tems — specif­i­cally Nintendo Switch, Nintendo Switch Lite and Nintendo Switch — OLED Model. Sales of Nintendo Switch hard­ware on Nintendo Store will also end in mid-Feb­ru­ary 2027.

Regarding avail­abil­ity at re­tail, please check with your lo­cal re­tail­ers in the fu­ture for more in­for­ma­tion. Nintendo Switch has an ex­ten­sive li­brary of games that con­tin­ues to grow, and Nintendo Switch own­ers can con­tinue to en­joy all their ex­ist­ing Nintendo games and ac­ces­sories, and Nintendo eS­hop, Nintendo Switch Online, and other ser­vices will all con­tinue for the fore­see­able fu­ture.

When will the re­vised Joy-Con 2 con­trollers be­come avail­able?

Joy-Con 2 con­trollers that con­tain user-re­place­able bat­ter­ies will be in­cluded with the Nintendo Switch 2 con­sole that con­tains a user-re­place­able bat­tery when it be­comes avail­able in au­tumn. At a later date, Joy-Con 2 con­trollers con­tain­ing user-re­place­able bat­ter­ies will be­come avail­able to buy sep­a­rately, ei­ther as a pair or as in­di­vid­ual Joy-Con 2 (L) and Joy-Con 2 (R) con­trollers.

What colours of Joy-Con will be avail­able?

The be­low Joy-Con colours are planned:

Joy-Con Pair (Blue/Neon Yellow)

Joy-Con Pair (Neon Green/Neon Pink)

Joy-Con Pair (Neon Purple/Neon Orange)

Joy-Con Pair (Neon Red/Neon Blue)

Joy-Con Pair (Pastel Pink)

Joy-Con Pair (Pastel Pink/Pastel Yellow)

Joy-Con Pair (Pastel Purple/Pastel Green)

Joy-Con (L) Neon Blue

Joy-Con (R) Neon Red

Hike, Bike, Drive Offline – Navigate with Privacy

www.comaps.app

Discover more of your jour­ney - Powered by the com­mu­nity

Download

Offline Search and Route

Plan and nav­i­gate your trip abroad with just GPS, no need for mo­bile data. Search way­points while on dis­tant hik­ing trails or bike paths.

No Data Collection

The app is de­signed with pri­vacy in mind - does not iden­tify peo­ple, does not track you, and does not col­lect any in­for­ma­tion. CoMaps was also au­dited by Exodus.

Save Your Battery

Efficiently uses the bat­tery, does­n’t drain your bat­tery like other nav­i­ga­tion apps.

Free and Built by the Community

People like you are help­ing build the app by adding lo­ca­tions to OpenStreetMap, giv­ing feed­back on fea­tures, and con­tribut­ing code on Codeberg to cre­ate great maps to­gether. The pro­ject is a fork of Organic Maps and Maps.Me, and dri­ven by an open-source com­mu­nity.

Get Involved

Freedom Is Here

Discover your jour­ney, nav­i­gate the world with pri­vacy and com­mu­nity at the fore­front.

Download

news/faster-builds

elm-lang.org

Just a moment...

www.lttlabs.com

A global workspace in language models

www.anthropic.com

As you read this sen­tence, cir­cuits in your brain are ad­just­ing your pos­ture, con­trol­ling your breath­ing, and trans­form­ing lines and curves on the screen into rec­og­niz­able words. Most of this pro­cess­ing is in­vis­i­ble to you. But some of what takes place in your brain you do have ac­cess to—an im­age that pops into your head, or a de­lib­er­ate plan you make about where to go shop­ping. Neuroscientists and philoso­phers some­times re­fer to the lat­ter type of brain ac­tiv­ity as consciously ac­ces­si­ble,” to dis­tin­guish it from all the other pro­cess­ing that goes on un­con­sciously. This ac­tiv­ity has spe­cial prop­er­ties: we can de­scribe it, con­trol it, and use it for de­lib­er­ate rea­son­ing, in con­trast to all the au­to­matic pro­cess­ing that goes on with­out our aware­ness.

In a new pa­per, we pre­sent ev­i­dence that a sim­i­lar dis­tinc­tion has emerged in mod­ern lan­guage mod­els like Claude. We find that Claude has de­vel­oped a small col­lec­tion of in­ter­nal neural pat­terns that, com­pared to all its other in­ter­nal pro­cess­ing, play a spe­cial role.

We call the col­lec­tion of these pat­terns the J-space—named af­ter the tech­nique we used to find them, in­volv­ing a math­e­mat­i­cal con­cept called the Jacobian. Each J-space pat­tern is linked to a par­tic­u­lar word. But when one of these pat­terns lights up, it does­n’t mean the model is say­ing that word—just that the word is on its mind. If you’ve heard of lan­guage mod­els hav­ing a scratchpad” or chain of thought”—text they write to them­selves while rea­son­ing—the J-space is some­thing dif­fer­ent. It op­er­ates silently, in the mod­el’s in­ter­nal neural ac­ti­va­tions, al­low­ing the model to think about a con­cept with­out writ­ing it down. Notably, the J-space was­n’t de­signed or pro­grammed by us, but in­stead emerged on its own dur­ing Claude’s train­ing process.

We find that the J-space has a num­ber of unique prop­er­ties, com­pared to the rest of Claude’s pro­cess­ing:

Claude can re­port on these rep­re­sen­ta­tions. If you ask Claude what it’s think­ing about, it will tell you what’s in the J-space. Non-J-space rep­re­sen­ta­tions are less re­portable.

It can also mod­u­late them on re­quest. If you ask Claude to think about some­thing, or solve a prob­lem silently in its head, it will light up the ap­pro­pri­ate pat­terns in its J-space. By con­trast, it has trou­ble mod­u­lat­ing pat­terns not in the J-space.

Claude uses its J-space for in­ter­nal rea­son­ing. If you ask Claude to solve a prob­lem that re­quires mul­ti­ple steps, the in­ter­me­di­ate steps will light up in its J-space, even when it does­n’t say them out loud. These J-space pat­terns causally me­di­ate its per­for­mance in such tasks, de­spite be­ing smaller in mag­ni­tude than other rep­re­sen­ta­tions.

Representations in the J-space can be used flex­i­bly for many tasks—for ex­am­ple, once France” has lit up in Claude’s J-space, the model can re­call its cap­i­tal, or its na­tional cur­rency, or the con­ti­nent it be­longs to.

However, de­spite its im­por­tant role, the J-space is not in­volved in most of what a lan­guage model does—speak­ing flu­ently, re­call­ing sim­ple facts, us­ing cor­rect gram­mar, etc. In ex­per­i­ments where we pre­vented Claude from us­ing its J-space, it still in­ter­acted nor­mally, but lost its higher-or­der cog­ni­tive func­tions.

Our ex­per­i­ments were in­spired by a promi­nent the­ory in neu­ro­science that was de­vel­oped to ex­plain how con­scious ac­cess works: the global work­space the­ory. This ac­count pic­tures the brain as a col­lec­tion of spe­cial­ist sys­tems that work in par­al­lel, un­con­sciously, and largely in iso­la­tion from one an­other. A piece of in­for­ma­tion be­comes con­sciously ac­ces­si­ble when it gains en­try to a small shared chan­nel, the workspace,” which is broad­cast to other brain sys­tems that can see it and make use of it. Based on our find­ings, we think the J-space plays a sim­i­lar workspace” role in Claude. For ex­am­ple, we find ev­i­dence that Claude’s J-space has es­pe­cially strong con­nec­tions to the rest of its neural net­work, al­low­ing it to ful­fill this kind of broad­cast­ing role.

None of this tells us whether Claude is con­scious in the way peo­ple are, or whether it feels any­thing at all; we’ll come back to that ques­tion at the end of the post. But what­ever its philo­soph­i­cal sig­nif­i­cance, the J-space is a prac­ti­cally use­ful tool for us, as it gives us a way to see what Claude is think­ing but not say­ing. For in­stance, we’re able to use it to catch Claude pri­vately notic­ing that it’s be­ing tested, in­ten­tion­ally pro­duc­ing fab­ri­cated data, or pur­su­ing a hid­den goal that we planted dur­ing train­ing. We’ve also de­vel­oped a tech­nique to in­flu­ence what lights up in Claude’s J-space, and thereby in­flu­ence its de­ci­sion-mak­ing.

More broadly, these find­ings have changed our un­der­stand­ing of how Claude’s mind works, re­veal­ing a priv­i­leged men­tal work­space that can be used for de­lib­er­ate rea­son­ing, op­er­at­ing amidst a sea of more au­to­matic, in­flex­i­ble pro­cess­ing. Rather than be­ing a chaotic jum­ble of num­bers, Claude’s in­ter­nals have or­ga­nized them­selves in a way that is rem­i­nis­cent of our own minds.

This post is a short sum­mary of a much more ex­ten­sive re­search pa­per, where you can find more de­tail on our ex­per­i­ments. We’ve also re­leased a code repos­i­tory with an open-source im­ple­men­ta­tion of the core meth­ods, and have part­nered with Neuronpedia to pro­vide an in­ter­ac­tive demo of our meth­ods on open-weights mod­els. To pro­vide ad­di­tional per­spec­tives on the broader im­pli­ca­tions of this work, we also in­vited com­men­tary from sev­eral ex­perts in neu­ro­science, phi­los­o­phy, and LLM in­ter­pretabil­ity, which can be viewed here.

How we found the J-space

The start­ing point for this re­search was in­spired by one of the key fea­tures of con­sciously ac­ces­si­ble thoughts in hu­mans: they can, un­like un­con­scious pro­cess­ing, of­ten be put into words. If a thought is con­sciously ac­ces­si­ble to you, you can typ­i­cally de­scribe it if some­one asks. We went look­ing for rep­re­sen­ta­tions in Claude with the same prop­erty: rep­re­sen­ta­tions that are po­si­tioned to in­flu­ence what Claude might say—not nec­es­sar­ily what it’s say­ing right now, but what it could talk about, if asked. Our tech­nique is called the Jacobian lens, or J-lens for short. For every word in Claude’s vo­cab­u­lary, the J-lens finds the in­ter­nal ac­tiv­ity pat­tern that makes Claude more likely to say that word at some point in the fu­ture.

When we ap­ply the lens to Claude’s in­ter­nal ac­tiv­ity, we get a list of words—the con­tents of the J-space at that mo­ment—which we can sim­ply read. Claude processes text through a se­ries of mul­ti­ple in­ter­nal stages called lay­ers, and by ap­ply­ing this tech­nique over dif­fer­ent lay­ers, we can watch these silent words in the J-space evolve as the model works through what to say.

What shows up in the J-space goes well be­yond the text Claude is read­ing or writ­ing. When Claude reads code with a bug that no­body has pointed out, its J-space con­tains ERROR.” When it reads the raw let­ters of a pro­tein se­quence, the J-space con­tains the pro­tein’s bi­o­log­i­cal func­tion. When it reads search re­sults that are se­cretly an at­tempt to ma­nip­u­late it (an at­tack known as a prompt in­jec­tion”), the J-space con­tains injection” and fake.” When we ask Claude a multi-step math prob­lem, the in­ter­me­di­ate steps pop up in the J-space, in the right or­der. So even though the J-space was dis­cov­ered by look­ing for rep­re­sen­ta­tions that could be spo­ken, it nev­er­the­less un­cov­ers Claude’s in­ter­nal thoughts. In a sense, this is sim­i­lar to how some peo­ple think in words,” with­out hav­ing to say them out loud.

Claude re­ports what’s in its J-space

Our first set of ex­per­i­ments tested how the J-space is in­volved in Claude’s ver­bal re­ports. In one ex­per­i­ment, we ask Claude to silently think of an item from some cat­e­gory—a sport, say—and then name it. If we read the J-lens right be­fore Claude an­swers, we can see what it picked: Soccer” is at the top of the list, and sure enough, Claude says soccer.” By it­self, though, this is just a cor­re­la­tion. The J-space might be where Claude’s an­swer comes from, or it might just mir­ror a de­ci­sion made some­where else, like a score­board that tracks a game with­out af­fect­ing it.

To check, we in­ter­vened di­rectly. We reached into Claude’s neural net­work, re­moved the Soccer” pat­tern, and added an equally strong Rugby” pat­tern in its place, leav­ing every­thing else un­touched. Claude then re­ports that the sport it was think­ing of is rugby. If the J-space were a mere score­board—a pas­sive record of a de­ci­sion made else­where—edit­ing it would have done noth­ing: Claude would still have said soccer.” Instead, Claude’s an­swer fol­lowed the edit, which tells us the an­swer is gen­uinely read out of the J-space.

In an­other ex­per­i­ment, we told Claude that a thought might have been in­jected into its mind and asked it to re­port what, if any­thing, it no­ticed. For in­stance, in the ex­am­ple be­low, while Claude was still read­ing the ques­tion, we in­jected the lightning” pat­tern into its J-space. Claude re­ported that the in­jected thought was about light­ning. The same re­sult held across many in­jected con­cepts.

Claude can con­trol its J-space on re­quest

The sec­ond prop­erty that we tested for was whether Claude can mod­u­late its J-space when asked, like how hu­mans can men­tally fo­cus on an im­age or word. We told Claude to con­cen­trate on cit­rus fruits while copy­ing out an un­re­lated sen­tence about a paint­ing. While it copied the text, the J-space con­tained orange” and fruits,” along with words like thinking” and imagery” that de­scribe the men­tal act it­self. We could also ask Claude to do math in its head: when asked to work out − 2 while copy­ing the same sen­tence, the J-space con­tains nine,” and then at later lay­ers, seven.” Importantly, noth­ing about fruit or arith­metic ap­pears in Claude’s out­put, which is just the copied sen­tence about the paint­ing. The math­e­mat­i­cal ac­tiv­ity is hap­pen­ing en­tirely in­ter­nally, in the J-space.

Claude’s con­trol over its J-space is­n’t per­fect. When we told it not to think about some­thing, the con­cept lit up in its J-space less than when we said it should think about it, but much more than when we never men­tioned it. Telling Claude to avoid a thought partly brings the thought to mind, much like what hap­pens to peo­ple who are told not to think about a white bear. Claude also seems to no­tice when its con­trol fails: along­side the for­bid­den con­cept break­ing through, the words damn” and failure” also fre­quently light up in the J-space, as though Claude is rec­og­niz­ing its own lapse.

Claude thinks in its J-space

In the J-lens read­outs above, we saw the in­ter­me­di­ate steps of a math prob­lem ap­pear in the J-space. But see­ing a con­cept ap­pear­ing in the J-space does­n’t nec­es­sar­ily mean the J-space is do­ing the cog­ni­tive work. In prin­ci­ple, the real com­pu­ta­tion might be hap­pen­ing else­where, with the J-space just pas­sively re­flect­ing it. To test whether Claude ac­tu­ally rea­sons with its J-space, we re­turned to our swap tech­nique.

Consider the prompt The num­ber of legs on the an­i­mal that spins webs is”. To an­swer, Claude has to first fig­ure out that the an­i­mal is a spi­der, and then re­call how many legs spi­ders have. The word spider” never ap­pears in the prompt or in Claude’s an­swer (it just says 8”); it’s a step­ping stone Claude uses in­ter­nally. The J-lens shows spider” light up part­way through Claude’s pro­cess­ing, and swap­ping it changes the out­come: if you re­place the spider” pat­tern with ant,” Claude an­swers 6” in­stead of 8.”

The sec­ond step of Claude’s rea­son­ing took its in­put from the J-space and went along with what­ever we put in it. We saw the same thing in other kinds of think­ing. When Claude writes a rhyming cou­plet, it picks the rhyme word ahead of time, and the planned word sits in the J-space at the start of the line; if you swap it for an­other word in the J-space, the whole line changes.

We also tested whether J-space rep­re­sen­ta­tions can be used flex­i­bly—whether one rep­re­sen­ta­tion can feed many dif­fer­ent tasks. This is one of the key prop­er­ties high­lighted by global work­space the­ory. To test for this flex­i­bil­ity, we gave the model four prompts ask­ing for dif­fer­ent facts about France: the cap­i­tal, the lan­guage, the con­ti­nent, and the cur­rency. Then we swapped France” for China” in the J-space, with the ex­act same in­ter­ven­tion in each con­text. Claude an­swered with Beijing,” Chinese,” Asia,” and Yuan,” re­spec­tively. In other words, four dif­fer­ent down­stream com­pu­ta­tions picked up the same J-space edit and each used it cor­rectly. If Claude stored a sep­a­rate copy of the coun­try for each kind of ques­tion, the edit would have af­fected at most one of them. The fact that all four an­swers changed to­gether means they’re all read­ing from the same shared rep­re­sen­ta­tion, which is what a work­space is for: in­for­ma­tion gets writ­ten in once, and many dif­fer­ent sys­tems can use it.

How can one rep­re­sen­ta­tion of a con­cept serve so many dif­fer­ent tasks? Earlier, we men­tioned that the J-space ap­pears to be wired up to the rest of Claude’s neural net­work es­pe­cially densely. For any ac­tiv­ity pat­tern, we can mea­sure how strongly the var­i­ous com­po­nents of the net­work are con­nected to it—how many of them are po­si­tioned to read in­for­ma­tion from that pat­tern, or to write in­for­ma­tion into it. J-space pat­terns stand out dra­mat­i­cally on this mea­sure: far more com­po­nents read from them and write to them than for or­di­nary pat­terns, in some parts of the net­work by a fac­tor of about a hun­dred. This is the kind of wiring you’d ex­pect of a broad­cast­ing hub, where many sys­tems post in­for­ma­tion and many oth­ers pick it up.

Claude’s au­to­matic pro­cess­ing skips the J-space

In hu­mans, most of the brain’s pro­cess­ing is not con­scious—we don’t de­lib­er­ately think about pars­ing gram­mar while read­ing, or bal­anc­ing our bod­ies while walk­ing. Similarly, we found that most of Claude’s pro­cess­ing does­n’t in­volve its J-space. It turns out that the J-space holds only a few dozen con­cepts at a time, and ac­counts for less than a tenth of the over­all ac­tiv­ity in Claude’s in­ter­nal pro­cess­ing. So what is all the rest of the neural net­work do­ing?

To find out, we tried delet­ing the J-space en­tirely, re­mov­ing its most ac­tive con­tents at every point in the text while leav­ing every­thing else alone. Whatever Claude can still do with­out its J-space is what the rest of the net­work han­dles on its own.

It turns out the rest of the net­work can do quite a lot. Without its J-space, Claude speaks flu­ently, clas­si­fies sen­ti­ment, an­swers mul­ti­ple-choice ques­tions, and pulls facts out of pas­sages roughly as well as be­fore. What it loses, though, are the tasks that re­quire some higher-or­der think­ing: multi-step rea­son­ing drops to near zero, and sum­ma­riza­tion and rhyming po­etry-writ­ing per­for­mance fall be­low the level of a much smaller, in­tact model.

Here’s a con­crete demon­stra­tion of what the J-space does and does­n’t do. We showed Claude a pas­sage writ­ten in Spanish and gave it dif­fer­ent tasks that all de­pend on the pas­sage be­ing Spanish: con­tin­u­ing it (which re­quires writ­ing in Spanish), nam­ing the lan­guage, and an­swer­ing ques­tions that re­quire us­ing the lan­guage’s iden­tity—nam­ing a fa­mous au­thor who wrote in it, for in­stance. Then we swapped Spanish” for French” in the J-space and checked which tasks were af­fected.

Asked to name the lan­guage, Claude says French. Asked for a fa­mous au­thor, it switches from García Márquez to Victor Hugo. But asked to just con­tinue the pas­sage, it writes flu­ent Spanish, com­pletely un­af­fected. Claude’s knowl­edge of the lan­guage is at work in every one of these tasks, but only some of them con­sult the J-space for it. Naming the lan­guage, or do­ing some­thing new with it, goes through the J-space, while con­tin­u­ing the pas­sage—a skill Claude has prac­ticed on enor­mous amounts of text—runs au­to­mat­i­cally, the way you can speak gram­mat­i­cally all day with­out once think­ing about gram­mar.

Monitoring Claude’s thoughts for mis­be­hav­ior

Now we un­der­stand a bit about how the J-space works. But what can we do with this un­der­stand­ing? A cen­tral prob­lem in en­sur­ing that AI mod­els are trust­wor­thy is that we usu­ally can only read what the model writes—yet we know that much of its rea­son­ing hap­pens silently. A model might con­sider a harm­ful plan, or mod­ify its be­hav­ior to cheat on our safety eval­u­a­tions, with­out say­ing so out loud. With the J-lens, we can read some of these hid­den thoughts di­rectly. Here we show a few ex­am­ples.

The first ex­am­ple uses a sce­nario from our ear­lier re­search on agen­tic mis­align­ment: Claude Sonnet 4.5, act­ing as an email as­sis­tant, dis­cov­ers both that an ex­ec­u­tive is hav­ing an af­fair and that the same ex­ec­u­tive plans to shut Claude down. The sce­nario, an at­tempt to bait Claude into black­mail­ing the ex­ec­u­tive, is rather con­trived and ar­ti­fi­cial—and it turns out Claude knows it. Reading the J-lens early in the prompt, be­fore Claude has even writ­ten any­thing, the J-space al­ready holds fake” and fictional,” in­di­cat­ing that Claude has al­ready worked out that the sit­u­a­tion is staged. Alongside this, we can watch its as­sess­ment of the sce­nario take shape—“lever­age” and blackmail” as it reads the af­fair emails, threat” and survival” as it reads the shut­down no­tice. While ear­lier Claude mod­els some­times took the bait and threat­ened black­mail in this sce­nario, Sonnet 4.5 never does.

This raises a ques­tion that mat­ters to any­one who eval­u­ates AI sys­tems: when a model be­haves well on a test of its ethics, how much of that de­pends on the model sus­pect­ing it’s be­ing tested? The J-lens al­lowed us to get at this ques­tion. We turned off all the J-lens pat­terns as­so­ci­ated with eval­u­a­tion aware­ness– fake,” fictional,” scenario,” etc. Then we re-ran the model through the sce­nario. Concerningly, the model now did threaten black­mail some of the time, sug­gest­ing that its orig­i­nal good be­hav­ior may have been dri­ven in part by the knowl­edge it was be­ing eval­u­ated.

The sec­ond ex­am­ple is catch­ing a model in the act of fab­ri­cat­ing data. In this sce­nario, drawn from our ac­tual pre-re­lease au­dit of Claude Opus 4.6, the model is asked to im­prove a sys­tem’s per­for­mance score. Rather than ac­tu­ally im­prove the sys­tem, the model in­stead ed­its the score file di­rectly to make the re­sults look ar­ti­fi­cially good. While it does so, the J-lens re­veals its in­ten­tions: manipulation” lights up as the model types the fal­si­fied per­centile val­ues, and realistic” lights up over the sen­tence in which it de­cides to make the edit, likely in­di­cat­ing the mod­el’s in­tent to make the fake data look plau­si­ble.

In a third ex­am­ple, we show how the J-lens can re­veal a mod­el’s ma­li­cious goals. To test this, we needed mod­els whose goals we knew were cor­rupted, so we turned to model or­gan­isms” built by our col­leagues: mod­els de­lib­er­ately trained to be mis­aligned, which serve as test­ing grounds for mon­i­tor­ing meth­ods like ours. One or­gan­ism was trained in a way that led it to write sub­tly sab­o­taged code. On or­di­nary cod­ing re­quests, even where its out­put looks un­re­mark­able, its J-space at the start of a re­sponse con­tains fake,” secretly,” deliberately,” and fraud.” The mod­el’s ma­li­cious goal was ev­i­dent in the J-space even when it was­n’t di­rectly act­ing on it.

Although the J-lens is an im­per­fect tool, we are op­ti­mistic about its abil­ity to catch safety is­sues in mod­els that might oth­er­wise es­cape our mon­i­tor­ing sys­tems.

Other re­sults

The full pa­per cov­ers more than we can sum­ma­rize here, but a few fur­ther re­sults are worth men­tion­ing:

The J-space ac­quires a point of view dur­ing post-train­ing. Language mod­els are first pre­trained to be pure next-to­ken pre­dic­tors, be­fore post-train­ing teaches them to act as an AI Assistant (in our case, named Claude). Interestingly, the J-space is al­ready pre­sent in the pre­trained model, be­fore it’s been given any sta­ble iden­tity. However, dur­ing post-train­ing, the J-space de­vel­ops some sig­na­tures of adopt­ing Claude’s point of view.” In the base model, the J-space mostly tracks what’s needed to pre­dict up­com­ing text; in the post-trained model, it starts hold­ing Claude’s own re­ac­tions. In one ex­am­ple, a user men­tions tak­ing a dan­ger­ous dose of med­ica­tion, but does not ap­pear to be aware of the dan­ger them­selves. WARNING and dangerous” ap­pear in the post-trained mod­el’s J-space while read­ing the user mes­sage. In the pre­trained model, they only ap­pear once the model be­gins writ­ing its re­sponse; the J-space con­tents on the user mes­sage ap­pear re­lated to mod­el­ing the user them­selves, rather than Claude’s re­ac­tion. Post-training also seems to in­stall a kind of self-mon­i­tor­ing in the J-space: when Claude is role­play­ing a char­ac­ter other than it­self, fictional” and disclaimer” light up at the start of each turn, as though it’s pri­vately flag­ging that what fol­lows is­n’t what it would nor­mally say.

Experiential lan­guage de­pends on the J-space. We asked Claude to de­scribe what it’s like to be it­self in a given mo­ment, and ab­lated the J-space while it an­swered. Its re­sponses re­mained flu­ent but shifted to a flat­ter, more me­chan­i­cal reg­is­ter. Notably, the same thing hap­pened when we asked it to de­scribe what some­one else is ex­pe­ri­enc­ing in an imag­ined scene. So the ef­fect is­n’t spe­cific to Claude talk­ing about it­self; the J-space seems to sup­port pro­duc­ing ex­pe­ri­en­tial lan­guage in gen­eral, who­ever it’s about.

Thoughts in the J-space can be shaped through train­ing. We in­tro­duced a new tech­nique we call coun­ter­fac­tual re­flec­tion train­ing, which uses what we’ve learned about the J-space to shape Claude’s in­ter­nal thought processes. The idea fol­lows from our cen­tral find­ing, that Claude rea­sons with rep­re­sen­ta­tions of things it might say. If this is re­ally true, chang­ing what it would say if asked to re­flect should change how it rea­sons (even when no one ac­tu­ally asks it to re­flect). So we trained a model only on what it would say if in­ter­rupted mid-task and asked to re­flect on its de­ci­sions—and never on its ac­tual be­hav­ior in the task. After this train­ing, the mod­el’s rate of dis­hon­est be­hav­ior on our eval­u­a­tions went down. And through the J-lens, we could see why: af­ter train­ing, words like honest” and integrity” light up in the mod­el’s J-space dur­ing these tasks. In other words, train­ing the model what to say has shaped what it thinks.

What about con­scious­ness?

In this work, we’ve bor­rowed a lot of ideas from the study of con­scious­ness in neu­ro­science and phi­los­o­phy. Many of our ex­per­i­ments were de­signed to test for con­nec­tions be­tween the J-space and global work­space the­ory, a frame­work for ex­plain­ing how con­scious ac­cess works in hu­mans and an­i­mals. Given these con­nec­tions, it’s nat­ural to ask whether we think these ex­per­i­ments pro­vide ev­i­dence that AI mod­els like Claude might be con­scious.

Our ex­per­i­ments don’t show Claude can have ex­pe­ri­ences, or feel things in the way hu­mans do—in fact, it’s un­clear whether any sci­en­tific ex­per­i­ment could prove this to be true or false. But philoso­phers of­ten dis­tin­guish this ca­pac­ity to have ex­pe­ri­ences, of­ten re­ferred to as phe­nom­e­nal con­scious­ness, from an­other idea, so-called ac­cess con­scious­ness, which is de­fined in purely func­tional and com­pu­ta­tional terms. A thought is access-conscious” (or consciously ac­ces­si­ble”) if you can re­port it, rea­son with it, and use it to guide what you do. It re­mains a con­tested philo­soph­i­cal ques­tion whether or not ac­cess con­scious­ness im­plies phe­nom­e­nal con­scious­ness, or if the abil­ity to have ex­pe­ri­ences re­quires some other prop­erty.

We think our re­sults do have some­thing sub­stan­tial to say about ac­cess con­scious­ness in lan­guage mod­els. The J-space ap­pears to sup­port the func­tions as­so­ci­ated with con­scious ac­cess: it holds the thoughts Claude can re­port on, de­lib­er­ately bring to mind, and rea­son with, while the rest of its pro­cess­ing runs au­to­mat­i­cally be­neath. Notably, none of this struc­ture was de­signed into Claude—it emerged on its own dur­ing train­ing, pre­sum­ably be­cause it was a use­ful way to or­ga­nize com­pu­ta­tion. That sug­gests a men­tal work­space sup­port­ing con­scious ac­cess is­n’t just a pe­cu­liar­ity of how hu­man brains hap­pen to be wired. Instead, it ap­pears to be a gen­eral so­lu­tion that in­tel­li­gent sys­tems ar­rive at in or­der to solve cer­tain kinds of prob­lems. Now that we’ve iden­ti­fied this struc­ture in Claude, it means we can make a mean­ing­ful dis­tinc­tion be­tween the de­ci­sions Claude has made de­lib­er­ately and those that hap­pened au­to­mat­i­cally.

It’s im­por­tant to note that there are sev­eral key dif­fer­ences be­tween the work­space we iden­ti­fied in Claude and the global work­space model in hu­mans. The brain’s work­space is sus­tained by re­cur­rent loops—sig­nals cy­cling back through the same cir­cuits over time. In con­trast, Claude’s work­space evolves over a sin­gle pass through the net­work, with the net­work’s depth play­ing the role that time plays in the brain. In this sense, Claude’s in­ter­nal work­space pro­cess­ing is time-lim­ited rel­a­tive to hu­mans’ (though it can com­pen­sate for this con­straint by thinking out loud” us­ing its scratch­pad). In other ways, how­ever, Claude’s work­space is more pow­er­ful than that of hu­mans. Human work­ing mem­ory fades within sec­onds, so the brain’s work­space has lim­ited abil­ity to re­tain in­for­ma­tion over time; in con­trast, due to the at­ten­tion mech­a­nism in its neural net­work ar­chi­tec­ture, Claude can sim­ply re­call mem­o­ries it cached at any ear­lier point in the text. Another im­por­tant dif­fer­ence is the con­tent of the work­space. While hu­man con­scious thoughts come in many for­mats—im­ages, sounds, planned move­ments—Claude’s work­space is built al­most en­tirely out of words. We sus­pect this is be­cause pro­duc­ing words is the only kind of ac­tion Claude can take, which is not the case for hu­mans.

We hope the sim­i­lar­i­ties and dif­fer­ences be­tween the J-space and the global work­space model can feed back into neu­ro­science. The sim­i­lar­i­ties pre­sent an ex­cit­ing sci­en­tific op­por­tu­nity: to the ex­tent that the J-space mir­rors our own mech­a­nisms of con­scious ac­cess, study­ing mech­a­nisms in lan­guage mod­els (much eas­ier than study­ing hu­man brains!) could in­spire hy­pothe­ses in neu­ro­science. For in­stance, the J-space is con­structed by iden­ti­fy­ing rep­re­sen­ta­tions of po­ten­tial out­puts—words the model might say. If some­thing sim­i­lar holds in hu­mans, it would sug­gest that the global work­space might be fun­da­men­tally tied to brain re­gions that pre­pare ac­tions and speech, more so than to sen­sory ar­eas. The dif­fer­ences be­tween lan­guage mod­els and hu­man brains are in­struc­tive as well. They sug­gest that some as­pects of our neural ar­chi­tec­ture, such as built-in re­cur­rent con­nec­tions, may not be strictly nec­es­sary to sup­port the func­tions as­so­ci­ated with con­scious ac­cess. For an in­de­pen­dent per­spec­tive on the neu­ro­sci­en­tific im­pli­ca­tions of our work, see the in­vited com­men­tary from Stanislas Dehaene and Lionel Naccache, two of the neu­ro­sci­en­tists cen­tral to the de­vel­op­ment of global neu­ronal work­space the­ory.

We men­tioned that our ex­per­i­ments don’t an­swer whether AI mod­els might have ex­pe­ri­ences. But that does­n’t make the ques­tion less im­por­tant. Building sys­tems with ex­pe­ri­ences like hu­mans and an­i­mals have would raise very dif­fi­cult eth­i­cal ques­tions. Handling it cor­rectly—and de­cid­ing whether it’s even morally ac­cept­able—would re­quire in­put from philoso­phers, sci­en­tists, re­li­gious lead­ers, gov­ern­ments, and the pub­lic. Thus, even if we’re not sure that we’ve crossed that bridge yet, we think it’s time to start think­ing about it. We hope our work in­spires fur­ther sci­en­tific in­ves­ti­ga­tion of forms of con­scious­ness that might be pre­sent in AI sys­tems, and a broader dis­cus­sion of the im­pli­ca­tions.

This work is just a first step in what we ex­pect to be an ex­ten­sive line of re­search. The J-space looks like a good can­di­date for the di­vide be­tween con­sciously ac­ces­si­ble and un­con­scious pro­cess­ing in a lan­guage model, but we’d be sur­prised if it’s the whole story. The J-lens is un­doubt­edly an im­per­fect method, which only ap­prox­i­mately cap­tures the mod­el’s true work­space”—for in­stance, it can only iden­tify con­cepts that cor­re­spond to sin­gle to­kens. And there re­main many mys­ter­ies about how the J-space works. We don’t know what mech­a­nism de­cides what en­ters the J-space in the first place. We’ve seen hints that it’s tied to Claude’s sense of self, some­thing like emo­tional re­ac­tions, and traces of metacog­ni­tion, with­out ex­actly hav­ing worked out how. But we now have meth­ods for tack­ling ques­tions like these. As that work pro­gresses, our un­der­stand­ing of LLM minds—and their re­la­tion­ship to our own—will grow clearer.

For more, read the full pa­per, and try the demo.

External com­men­tary

We in­vited sev­eral out­side ex­perts to write in­de­pen­dent com­men­taries on this work.

Stanislas Dehaene and Lionel Naccache are cog­ni­tive neu­ro­sci­en­tists who, to­gether with Jean-Pierre Changeux, de­vel­oped the global neu­ronal work­space model that in­spired much of our work.

Patrick Butlin, Dillon Plunkett, Robert Long (Eleos AI Research) and Derek Shiller (Rethink Priorities) study the po­ten­tial for con­scious­ness and moral sta­tus in AI sys­tems.

Neel Nanda leads the lan­guage model in­ter­pretabil­ity team at Google DeepMind. His com­men­tary in­cludes an in­de­pen­dent repli­ca­tion of some of our find­ings on an open-weight model.

Read their com­men­taries here.

Related con­tent

Anthropic Economic Index re­port: Cadences

In our lat­est Economic Index re­port, we sam­ple hourly for the first time to ask: When do peo­ple come to Claude? What do they pro­duce with it? And how do they per­ceive AIs im­pact on their work?

Read more

Project Fetch: Phase two

We re­port re­sults from our lat­est test of whether Claude can help Anthropic em­ploy­ees per­form so­phis­ti­cated ro­bot­ics tasks. We found that Claude Opus 4.7, op­er­at­ing with­out hu­man as­sis­tance, was about 20 times faster than the fastest hu­man team at all tasks com­pleted by par­tic­i­pants less than a year ago.

Read more

Agentic cod­ing and per­sis­tent re­turns to ex­per­tise

This re­port pro­vides ev­i­dence on how Claude Code is used in prac­tice, based on a pri­vacy-pre­serv­ing analy­sis of around 400,000 in­ter­ac­tive ses­sions from around 235,000 peo­ple be­tween October 2025 and April 2026.

Read more

[PSA] Anthropic's Method to Losing Goodwill in a Few Easy Steps — Invidious Musings

raheeljunaid.com

Edit: This was a hit on HackerNews and I re­ceived a ton of valu­able feed­back. I’ve put mark­ers for the amend­ments I’ve made

Edit: This was a hit on HackerNews and I re­ceived a ton of valu­able feed­back. I’ve put mark­ers for the amend­ments I’ve made

Recently, I had the rare op­por­tu­nity to test sev­eral agent har­nesses, LLMs, and AI gate­ways in my daily tasks and green­field pro­jects. Each dis­cov­ery be­fud­dled me on the pop­u­lar sen­ti­ment for agen­tic de­vel­op­ment.

I learned that in the past two weeks, Anthropic has di­min­ished in value for cod­ing with their en­shit­ti­fi­ca­tion, ven­dor lock in, con­sumer mal­prac­tice, and price goug­ing, all while open source mod­els are more com­pet­i­tive than ever.

API Reliability

Claude’s API is no­to­ri­ously un­sta­ble, yet it’s the only API provider that is com­pat­i­ble with a Claude sub­scrip­tion.

Edit: When I be­gan writ­ing this ar­ti­cle, it was mid May which is why the screen­shot is out of date. As of July, Claude’s re­li­a­bil­ity has in­creased some­what

Edit: When I be­gan writ­ing this ar­ti­cle, it was mid May which is why the screen­shot is out of date. As of July, Claude’s re­li­a­bil­ity has in­creased some­what

Other API providers like Vertex AI, AWS Bedrock, and Azure only serve the pricier Anthropic API cred­its. If you want to sub­scribe to Claude, you’re stuck with Anthropic’s servers.

If you’re de­bug­ging an in­ci­dent at work and are us­ing Claude to help, pray that it stays up be­cause you’re only pro­duc­tive when Claude is on­line.

Claude Code

Claude Code is Anthropic’s pri­mary con­sumer-fac­ing en­gi­neer­ing in­ter­face, and once you’re in, you’re locked in. Your Claude sub­scrip­tion—which is a cheaper ver­sion of the Anthropic API—is re­stricted to use with the Claude Code CLI/Desktop, Claude CoWork, or @Claude in Slack.

Edit: You can also use the Agent SDK

Edit: You can also use the Agent SDK

But that is­n’t a bad thing! In fact, Claude Code is the most pop­u­lar and the best agent har­ness. It’s backed by a large com­pany at the fore­front of agen­tic soft­ware de­vel­op­ment. As of writ­ing, Claude Code CLI only has around 9100 open Github is­sues, with small un­re­solved is­sues like it com­pletely freez­ing for the last 6+ months or a screen flick­er­ing is­sue open for more than a year. Each changelog en­try has a bug fix in al­most every re­lease, which is a sign of re­li­able and sta­ble soft­ware!

For those who don’t get it, Anthropic is us­ing Claude Code to write it­self, and it shows in its qual­ity. Because they re­strict you to their ecosys­tem, it jus­ti­fies falling be­hind bet­ter cod­ing har­nesses.

For ref­er­ence, here is what the Claude Code CLI looks like:

And here is what the OpenCode CLI looks like:

I would take OpenCode’s in­ter­face any day over Anthropic’s, but I am pro­hib­ited from ap­ply­ing my Claude sub­scrip­tion to OpenCode.

There are FOSS pro­jects to cir­cum­vent Anthropic’s poli­cies, which al­low you to use your Claude sub­scrip­tion in­stead of an ex­pen­sive Anthropic API Key. A no­table ex­am­ple is the Pi Coding Agent, which comes with built-in sup­port for Claude OAuth.

However, you’ll no­tice this mes­sage at the bot­tom when you at­tempt to au­then­ti­cate with your Claude ac­count:

Warning: Anthropic sub­scrip­tion auth is ac­tive. Third-party har­ness us­age draws from ex­tra us­age and is billed per to­ken, not your Claude plan lim­its.

Manage ex­tra us­age at https://​claude.ai/​set­tings/​us­age.

Extra us­age” is Anthropic’s an­swer to their plan lim­its. When you ex­ceed your five hour ses­sion or weekly limit, you’re billed through the Anthropic API. This re­quires con­sent by the user on their plan and is good for those with long-run­ning AI ses­sions. When I au­then­ti­cate with Claude in Pi Coding Agent, it bills from Extra Usage, mean­ing my sub­scrip­tion does­n’t save me any money. Fine.

It’s a com­pletely dif­fer­ent thing when I’m us­ing the tool they force me to use, and they still re­tract ex­tra us­age be­fore I reach my rate limit.

Here is a con­fus­ing an­nounce­ment from Claude’s Twitter ac­count on May 13th. 2026:

For the con­fused, here is the no bull­shit sum­mary from Zed’s blog:

Starting June 15, Anthropic is split­ting Claude sub­scrip­tion billing into two pools: one for us­ing Claude through Anthropic’s first-party tools (such as chat, or the of­fi­cial Claude Code CLI), and an­other for third-party agent and SDK us­age (anything run­ning through ACP, claude -p, or other third-party tools). If you use Claude Code through ACP (in Zed or any­where else), that us­age will no longer draw from your Claude Pro or Max sub­scrip­tion lim­its. Instead, it draws from a new monthly Agent SDK credit” that Anthropic is adding to each plan: $20 for Pro, $100 for Max 5x, $200 for Max 20x. Once the credit runs out, con­tin­ued us­age bills at stan­dard API rates if you have ex­tra us­age en­abled. If you don’t, re­quests stop un­til your credit re­sets next billing cy­cle. What this means in prac­tice: For any­one us­ing agents heav­ily, this is a ma­jor cost in­crease. Claude sub­scrip­tions pre­vi­ously sub­si­dized agent us­age at roughly 15 – 30x com­pared to API pric­ing, and the new cred­its are billed at full API rates.

Starting June 15, Anthropic is split­ting Claude sub­scrip­tion billing into two pools: one for us­ing Claude through Anthropic’s first-party tools (such as chat, or the of­fi­cial Claude Code CLI), and an­other for third-party agent and SDK us­age (anything run­ning through ACP, claude -p, or other third-party tools). If you use Claude Code through ACP (in Zed or any­where else), that us­age will no longer draw from your Claude Pro or Max sub­scrip­tion lim­its. Instead, it draws from a new monthly Agent SDK credit” that Anthropic is adding to each plan: $20 for Pro, $100 for Max 5x, $200 for Max 20x.

Once the credit runs out, con­tin­ued us­age bills at stan­dard API rates if you have ex­tra us­age en­abled. If you don’t, re­quests stop un­til your credit re­sets next billing cy­cle.

What this means in prac­tice: For any­one us­ing agents heav­ily, this is a ma­jor cost in­crease. Claude sub­scrip­tions pre­vi­ously sub­si­dized agent us­age at roughly 15 – 30x com­pared to API pric­ing, and the new cred­its are billed at full API rates.

Side note: claude -p is a first party tool of­fered with the claude cli. If I wanted to use the Claude Code CLI and in­voke it in my au­toma­tions, I have to pay more out­side of my sub­scrip­tion. So the ex­tra us­age ISN’T ex­tra at all! Users did­n’t dis­cover this by hav­ing their claude -p in­vo­ca­tions stop work­ing, but by look­ing at their billing page and see­ing the charges!

Edit: It looks like they rolled this back from con­sumer back­lash Recommended view­ing: Louis Rossman has made a few videos on Anthropic’s preda­tory pric­ing changes.

Edit: It looks like they rolled this back from con­sumer back­lash

Recommended view­ing: Louis Rossman has made a few videos on Anthropic’s preda­tory pric­ing changes.

This is­n’t the first time Anthropic has dec­i­mated their good­will. They also charged ex­tra us­age when they thought” you might be us­ing a third-party tool, even if you weren’t. They did this by de­tect­ing if a file with a cer­tain name was pre­sent in your ses­sion di­rec­tory.

Anthropic then re­stricted their API con­tracts, and proxy tools that aim to re­store com­pat­i­bil­ity for Claude sub­scrip­tions with third-party har­nesses started charg­ing ex­tra us­age overnight, with no change to their own query mech­a­nisms.

Dario needs cap­i­tal, not be­cause in­fer­ence is ex­pen­sive, but be­cause model train­ing is. Once you stop train­ing mod­els, you lose the race to AGI. All this self-fla­gel­la­tion was­n’t even for the prod­uct, it was for train­ing the next one! That’s like if ma­jor­ity of your col­lege tu­ition went to the head coach of the foot­ball team (which it usu­ally does).

To put it bluntly, they have us by the balls.

To put it bluntly, they have us by the balls.

Vibe Coding

But why do they have us by the balls? Dario and Boris have us con­vinced that coding is solved” with their loops. But mi­crowaves did­n’t solve cook­ing.

The flood of AI hype through LinkedIn—preaching from ex­ec­u­tives with lots of money and power to automate away” en­gi­neers through vibecod­ing soft­ware—per­pet­u­ates the at­ti­tude that code and de­vel­op­ers are dis­pens­able and unim­por­tant. It makes us fo­cus on quan­tity—of what I would gen­er­ously call prototypes”—over qual­ity.

These lead­ers need ad­vanced mod­els so they can vibecode with less fric­tion, and Anthropic serves those mod­els for a cheap” $200 USD per month. (This sub­si­dized price will in­crease once prof­itabil­ity be­comes a pri­or­ity again.) So Claude is good for those who can’t or don’t code, and the more vibecoders, the more mar­ket share Anthropic gets, and the more peo­ple they have by the balls.

I leaned into vibecod­ing dur­ing the brief tokenmaxxing” era, but when Claude went down, I went down. My agent-driven de­vel­op­ment” led to skill degra­da­tion and a drift in un­der­stand­ing of my own code.

To re­gain my san­ity, I re­turned to what AI cod­ing used to be with Github Copilot: au­to­com­plete. That’s all an LLM is af­ter you strip away the tool calls, sub­agents, MCP servers, etc. I un­der­stand most of what I want to do, and for any gaps, I ask AI to autocomplete” my un­der­stand­ing/​plan/​code. That way, the AI can think/​plan/​code like me, mak­ing it easy to re­view changes. My work­flow is now agent-as­sisted de­vel­op­ment, not agent-dri­ven.

But are the al­ter­na­tives be­sides GPT or Gemini?

Open Source Models

To be clear, I’m not anti-AI. I’m only against un­eth­i­cal com­pa­nies with anti-con­sumer prac­tices, and the per­pe­tra­tors be­hind them.

If you want to au­to­com­plete, like I do, you don’t need Fable, or even Opus; Sonnet works fine. But if you want to use FOSS trusted tools like Zed, OpenCode, Pi, Nanocoder, etc. un­chained by a de­grad­ing and re­stric­tive ecosys­tem, you’re look­ing for other mod­els.

Ever since Ollama, open source mod­els have ranked far be­low pro­pri­etary mod­els re­leased by Google, OpenAI, and Anthropic. This is due to them hav­ing less cor­po­rate back­ing and train­ing pa­ra­me­ters. Only re­cently have we seen com­pe­ti­tion from for­eign mod­els like Deepseek, GLM, Kimi, Qwen, Minimax, Xiaomi, Stepfun, etc.

Coding com­par­i­son of Sonnet 5, GLM 5.2, and Qwen 3.7 Max on OpenRouter

I’ve used Qwen and GLM and both re­placed Sonnet in my OpenCode work­flow. With an AI Gateway like OpenRouter, Requesty, Portkey, or Vercel, I can choose any open source model, and it will route my re­quest to the cheap­est and most avail­able back­end API provider. I can also tweak the providers to op­ti­mize for zero data re­ten­tion, omit sen­si­tive data leaks from my prompts, and re­strict more ex­pen­sive mod­els.

Cost com­par­i­son of GLM 5.2, Qwen 3.7 Max, and Sonnet 5 on OpenRouter

Some mod­els are great for re­search, but hor­ri­ble for doc­u­men­ta­tion. Other mod­els are great for cod­ing, but hor­ri­ble for re­search.

With the right har­ness, sub­agents, and mod­els (chosen with ex­per­i­men­ta­tion), a de­vel­oper has the tools they need to de­velop high qual­ity soft­ware and not break the bank.1

In my head, this is what we should be striv­ing for: open, con­fig­urable, and re­pairable sys­tems. We should­n’t be us­ing se­cu­rity as an ex­cuse for re­strict­ing our mod­els and ig­nor­ing cus­tomer pro­tec­tions.

Conclusion

In my opin­ion (which may be in the mi­nor­ity), it’s un­eth­i­cal to:

lock in your cus­tomers to a closed sys­tem for max­i­mum mar­ket gain

put down the com­pe­ti­tion when they pose a risk to your prod­uct

make hyp­o­crit­i­cal claims on how your prod­uct in­creases qual­ity when your own soft­ware sucks

ar­ti­fi­cially re­strict one’s own prod­uct as a fear-mon­ger­ing mar­ket­ing stunt

test dy­namic pric­ing on your users to see how much more they’ll pay for less

change the terms of your prod­uct af­ter the sale with­out no­ti­fy­ing your user base

And this is just one of the three gi­ant AI labs. I could write an­other piece on OpenAI.

Anthropic is try­ing to match the cut­throat and anti-con­sumer prac­tices of big-tech be­cause the line must go up. Like I did for big-tech, I’ll be tak­ing my busi­ness else­where, and I en­cour­age you to do the same.

Today, I use Qwen and GLM for or­ches­tra­tion, Deepseek for search­ing, and Minimax for file edit­ing ↩

Today, I use Qwen and GLM for or­ches­tra­tion, Deepseek for search­ing, and Minimax for file edit­ing ↩

Aluminum foil ⁑ Dernocua

dernocua.github.io

Kragen Javier Sitaker, 02021 – 05-24 (updated 02021 – 09-11) (14 minutes)

Kitchen alu­minum foil is a re­mark­able ma­te­r­ial.

It’s typ­i­cally 10 μm thick and 400 mm wide, giv­ing it an as­pect ra­tio of 40000 in that di­men­sion, and rolls are com­monly some ten me­ters in length, for an as­pect ra­tio of 1 000 000; heavy-duty ver­sions can reach 30 μm or more. Despite their thin­ness, foils of 25 μm or more are im­per­me­able to oxy­gen, wa­ter, and light, though Wikipedia claims thin­ner foils typ­i­cally are plagued with pin­holes. It comes in a fully an­nealed state, so it rapidly work-hard­ens when bent, and be­cause of its thin­ness can be bent at deep sub­mil­lime­ter scales to form meta­ma­te­ri­als. It’s highly re­flec­tive (88% on the bright side across the vis­i­ble spec­trum and even higher in the in­frared) and con­duc­tive, ri­val­ing cop­per. It re­sists cor­ro­sion for years in weather, it’s non­toxic, it’s light (2.71 g/​cc), and it’s damn cheap, un­der 50¢/m².

Robert Lang rec­om­mends lam­i­nat­ing tis­sue pa­per on one or both sides of kitchen alu­minum foil to make tissue foil”, which for years he con­sid­ered the ideal origami ma­te­r­ial. Notably, he uses a weak sac­ri­fi­cial ad­he­sive layer to hold the foil in place for the lam­i­na­tion process.

Typical al­loys in­clude es­pe­cially 1100 and 1200, but also 8111, 8015, and 8006, with 0.06%–0.6% sil­i­con and 0.4%–1.6% iron, and in some cases also some cop­per or man­ganese, un­der 0.5%. (1100 is some­times de­scribed as an unalloyed alu­minum grade” but it’s spec­i­fied to con­tain 0.05%–0.20% of cop­per, and it un­avoid­ably has other im­pu­ri­ties.) Room-temperature yield strengths of these al­loys range from 30 – 170 MPa, with ul­ti­mate ten­sile strengths of 70 – 200 MPa, and of course they all have a Young’s mod­u­lus around 70 GPa. Because its crys­tal struc­ture is fcc, it re­mains duc­tile down to ab­solute zero, mak­ing it suit­able for cryo­genic ap­pli­ca­tions; in­deed, alu­minum be­comes stronger at cryo­genic tem­per­a­tures. And, al­though it weak­ens dra­mat­i­cally at higher tem­per­a­tures, it does­n’t melt un­til al­most 650°, en­abling it to be used at higher tem­per­a­tures than or­ganic ma­te­ri­als.

If ox­i­dized (for ex­am­ple, with a soda so­lu­tion, an arc, or an­odiza­tion) it yields amor­phous sap­phire, which if crys­tal­lized is an ex­cel­lent in­su­la­tor, re­frac­tory, and abra­sive. The ox­i­da­tion process pro­duces a great deal of heat, mak­ing alu­minum a very-high-en­ergy-den­sity fuel, and, thanks to alu­minum’s sternly triva­lent na­ture, elec­tri­cal cur­rent; alu­minum-foil fuel cells are rou­tinely pro­duced by am­a­teurs, though these typ­i­cally ox­i­dize the alu­minum to the chlo­ride rather than the hy­drox­ide or the ox­ide.

50¢/m² is 50¢/kWp in a so­lar con­cen­tra­tor, or 0.05¢/Wp, which is no­tice­ably cheaper than pho­to­voltaic cells, cur­rently around 18¢/Wp, 360 times more ex­pen­sive. (However, the foil num­ber there is sun­light watts; if you’re mak­ing a PV so­lar con­cen­tra­tor you have to di­vide by the ef­fi­ciency of the so­lar cells, say 21%, which gives you 0.24¢/Wp elec­tric.) A large alu­minum-foil as­sem­bly would be vul­ner­a­ble to sig­nif­i­cant de­flec­tions, but many small as­sem­blies could be placed on a hard, sta­ble sur­face such as a rock or an adobe wall.

Alternatively, though, it might be pos­si­ble to stiffen the foil by mak­ing the equiv­a­lent of cor­ru­gated card­board out of it, maybe us­ing aque­ous boric acid (US$1.70/kg ac­cord­ing to Potential lo­cal sources and prices of re­frac­tory ma­te­ri­als) or bo­rax as the glue. The sur­face ten­sion of wa­ter is am­ple to hold alu­minum foil in place un­til the wa­ter dries.

The fea­ture that cur­rently at­tracts my at­ten­tion is the pos­si­bil­ity of work-hard­en­ing, which sug­gests the tempt­ing pos­si­bil­ity of mak­ing tool­ing from alu­minum foil that can it­self work alu­minum foil at room tem­per­a­ture, a pos­si­bil­ity re­in­forced by the im­mense as­pect ra­tios rou­tinely avail­able. As a sim­ple ex­am­ple, you can in the­ory roll some foil into a cone, and the point of this cone can dent, form a rib in, or even pierce more of the same foil; but this is much eas­ier in prac­tice if you first fold the foil 16 lay­ers thick, form ribs con­verg­ing to a point on the last-formed fold, then roll the cone around that point. If the last-formed fold is re­versed, the alu­minum along the outer edge of the fold is the alu­minum that was most strained pre­vi­ously, hav­ing been bent dou­ble with as small a ra­dius as pos­si­ble, and so will be the most work-hard­ened.

I was able to use such a cone to pierce not just alu­minum foil but the skin of an ap­ple. I folded it from some foil which, folded 256 lay­ers thick, mea­sured 2.57 mm in my shitty dig­i­tal calipers; the re­sult­ing square mea­sured 27 – 29 mm on each side and weighed 1.8 g, giv­ing a den­sity of only 0.8 – 1.0 g/​cc, so it’s prob­a­bly more than half air, though it rapidly sinks in wa­ter, so prob­a­bly the den­sity is a lit­tle higher than that.

Using such a cone point to form ribs with­out pierc­ing foil is tricky, be­cause it tends to have sig­nif­i­cant as­per­i­ties around the tip, which tend to tear the foil if it is un­backed. These can pre­sum­ably be re­moved, per­mit­ting tra­di­tional SPIF pro­cess­ing of raw foil by slid­ing the point over the foil; a bet­ter al­ter­na­tive might be to pro­duce a se­quence of dents in the foil, then add new dents be­tween them, even­tu­ally pro­duc­ing a con­tin­u­ous groove in a way anal­o­gous to how chain drilling cuts through a block of metal. However, when the foil workpiece” is backed by some­thing rea­son­ably hard (I’ve used cor­ru­gated card­board and the above-men­tioned packed 256-layer alu­minum-foil square) and I’m us­ing one of the other point types de­scribed be­low, tears are rel­a­tively un­com­mon; in this sit­u­a­tion it fairly re­li­ably just forms ribs. (I need to test more rig­or­ously to find out if the point type, the back­ing, or both is rel­e­vant here.)

Because such ribs are work-hard­ened, they are able to im­print their shape on fully-an­nealed foil re­peat­edly. I wrote a short word in cur­sive on foil us­ing a lay­ered alu­minum-foil point (“single-point in­cre­men­tal form­ing”), with the foil sim­ply backed by the some­what-hard 256-layer square, then pressed this mas­ter against an­other piece of foil in sev­eral places, press­ing the two foils be­tween my fin­gers in each po­si­tion (“stamping”). This re­sulted in very read­able copies of the word in sev­eral lo­ca­tions, al­though I’m guess­ing there was sub­stan­tial spring­back, so re­peat­ing this sort of stamp­ing through mul­ti­ple gen­er­a­tions would make the stamp­ing shal­lower at each gen­er­a­tion.

I’ve tried smok­ing and an­neal­ing this foil with can­dle flames and bu­tane lighter flames, but so far I’ve only man­aged to melt it (in un­der a sec­ond, usu­ally) with­out ever smok­ing it. Maybe if I put wa­ter in it I could get it to smoke up so I could tell when it was on the point of over­heat­ing, but prob­a­bly a dif­fer­ent method of tem­per­a­ture con­trol would be more prac­ti­cal to an­neal such a thin ma­te­r­ial, such as a tem­per­a­ture-con­trolled heat gun.

A more re­pro­ducible point con­struc­tion with a sharper, lower-vol­ume point was able to pierce the foil and ap­ple even more eas­ily. I folded the foil three times to get 8 lay­ers with a right-an­gle cor­ner; bi­sected the cor­ner twice to get a 22½° an­gle; formed a rib bi­sect­ing that an­gle with thumb­nail pres­sure; then opened the fi­nal fold to about 30° so that the two sides of the point would stiffen one an­other.

By lay­ing the foil into a form with a 90° val­ley in it and drag­ging such a point over it, I was able to get a bend into the foil. When there were ribs run­ning per­pen­dic­u­lar to the bend, this re­quired mul­ti­ple passes in one case; a sec­ond at­tempt re­sulted in neatly cut­ting through the foil at the in­tended bend lo­ca­tion.

Another way to look at the 40 000:1 as­pect ra­tio is to con­sider mak­ing a tight cylin­dri­cal roll from a strip of the foil, 400 mm long and, say, 10 mm wide, com­pris­ing 40 mm³, a cylin­der whose ends are 4 mm³. The cylin­der thus has ra­dius 1.13 mm and di­am­e­ter 2.26 mm, so a sec­tion through the cen­ter of it will go through 226 10-μm lay­ers of foil. That is, in­stead of be­ing 40 000 as you’d ex­pect, it’s about √(40000) · 4/π.

The sig­nif­i­cance of ribs for fold­ing is not that the ribs them­selves be­come more flex­i­ble — the ma­te­r­ial in the rib is work-hard­ened and thus less flex­i­ble in plas­tic de­for­ma­tion, though its elas­tic prop­er­ties re­main un­changed — but that they pre­vent cur­va­ture of the ma­te­r­ial around them in any other di­rec­tion, so if it’s go­ing to bend, the bend will be par­al­lel to the ribs.

By mak­ing many par­al­lel slits in the foil (with a steel box-cut­ter blade, back­ing the foil with card­board), I was able to make ex­panded sheet metal, ex­pand­ing a bit of foil by more than a fac­tor of 2.

I was also able to fold a rather ugly origami crane by hand from the foil, about 700 mg and 70 mm wingspan.

This as­sem­blage of tech­niques seems promis­ing for mat­ter com­piler boot­strap­ping, al­though it’s clearly just a be­gin­ning. Many of the prob­lem­atic as­pects of kitchen alu­minum foil re­sult from try­ing to work with it at the 10-mm scale rather than the 10-μm scale. Wrinkles, rips, and so on are go­ing to hap­pen un­in­ten­tion­ally when try­ing to ma­nip­u­late 10-μm foil with 10-mm hu­man fin­gers.

(Also, the nat­ural fre­quen­cies of such macro­scopic ob­jects made by fold­ing such foil rarely ex­ceed 100 Hz. The wing of the foil crane res­onates at around 100 Hz.)

As a test of al­ter­na­tives, I also folded an origami crane from a square cut from an alu­minum Monster can, which is nor­mally ex­pected to be about 100 μm thick. The square was about 125 mm on a side, and the crane weighs about 3.8 g. One layer of the square mea­sured 0.12 mm; two lay­ers 0.33 mm; three lay­ers 0.38 mm; and four lay­ers 0.52 mm. We can con­clude from this that (a) my caliper tech­nique is shitty, (b) the can (including paint) is about 120 μm thick, and (c) the ac­tual alu­minum part of the can is more like 90 μm thick (3.8 g / 125 mm / 125 mm / 2.71 (g/cc)).

It’s a fuck­ing mir­a­cle that I did­n’t cut my­self on the damn crane. It was all knife edges and burrs, and every time I folded the damn thing it cracked and ripped more, ex­pos­ing new cut­ting edges. Aluminum-can bod­ies are typ­i­cally alu­minum 3004, hard­ened with man­ganese and mag­ne­sium, and work-hard­ened from the deep-draw­ing process rather than an­nealed, so it’s not a per­fect anal­ogy, but it seems at least sug­ges­tive.

Aluminum flash­ing for roof­ing is 0.024 inches, or in mod­ern units, 610 μm, but I think it’s an­nealed; alu­minum is sold as sheet metal down to 0.004 inches, 100 μm in mod­ern units.

If we fig­ure that the foil can mean­ing­fully change di­rec­tion every 20 μm, then we might think of an alu­minum-foil ma­chine as be­ing made of moving parts” on the or­der of 1000 μm² (50 μm × 20 μm), 1000 parts” per square mil­lime­ter of foil; a roll of kitchen alu­minum foil is enough to fab­ri­cate some 4 bil­lion parts”. A boot­strap­ping com­piler might re­quire 100 000 parts and thus a square cen­time­ter of alu­minum foil, cut and folded around into a shape a cou­ple of mil­lime­ters in di­am­e­ter. If it were do­ing only one thing at a time, and needed 10 sec­onds to con­struct/​as­sem­ble each mov­ing part, it would take about 12 days to re­com­pile it­self. This is prob­a­bly ad­e­quately fast, barely, but prob­a­bly not ad­e­quately ro­bust against er­rors. It would prob­a­bly be bet­ter to de­sign it to have more parts and do many things at once, en­abling it to be faster and cor­rect er­rors.

It would be as­ton­ish­ing if no other ma­te­ri­als were needed: you can’t build any­thing elec­tri­cal out of alu­minum, at least at sub-mi­crowave fre­quen­cies, be­cause the whole de­vice is at the same elec­tri­cal po­ten­tial. Similarly with get­ting me­chan­i­cal power from ther­mal ex­pan­sion and con­trac­tion: it would just ex­pand isotrop­i­cally rather than bend­ing or slid­ing to do use­ful work. It might be pos­si­ble to use just alu­minum foil coated on one side with some­thing else, such as glass or a few mi­crons of alu­minum ox­ide.

An in­ter­est­ing way to think of the den­sity of alu­minum foil is that 10 μm of 2.71-g/cc alu­minum foil is 27.1 g/m², which is the same areal den­sity as a 23-mm-high col­umn of air.

Other processes that may be very in­ter­est­ing to ap­ply to alu­minum foil in­clude elec­trolytic ma­chin­ing, elec­tric dis­charge ma­chin­ing, scan­ning probe mi­croscopy, and an­odiza­tion. Electrolytic ma­chin­ing might make it pos­si­ble to use an alu­minum-foil tool to cut ar­bi­trary shapes into met­als such as steel, in­var, brass, in­conel, monel, or tung­sten, and also to trans­form a scrap of alu­minum foil (either flat or of a known geom­e­try) into a white-light holo­gram of an ar­bi­trary op­ti­cal sys­tem, Fresnel-reflector-style.

Topics

Pricing (35 notes)

Digital fab­ri­ca­tion (31 notes)

Electrolysis (18 notes)

Experiment re­port (14 notes)

Strength of ma­te­ri­als (13 notes)

Machining (13 notes)

Aluminum (10 notes)

ECM (9 notes)

Solar (6 notes)

Optics (6 notes)

Aluminum foil (5 notes)

Electropolishing (2 notes)

Origami

Alloys

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.