After Undersecretary of War Emil Michael went on the All-In Podcast and did an extensive interview with Pirate Wires, I found many enlightening quotes, many of which demanded a response, and went about assembling an extensive list of analysis of the statements of Emil Michael during the ongoing recent events with Anthropic.
As part of that, I ended up in a remarkably polite and productive Twitter exchange with him. We reached several points of agreement. The Department of War has no intention of doing what in law is called ‘mass domestic surveillance’ but those words are terms of art in NatSec law, and mean a much narrower set of things than one would think.
There are many things that I or Anthropic or most of you would look at as mass domestic surveillance, that are legal, and it is DoW’s position that it’s their job and duty to do everything legal to protect our country, including those things. The law has not caught up with reality and Congress needs to fix that. And this is the best country in the world, with the best system of government, because private citizens can voice their disagreement with such actions, including by refusal to participate.
Thus, in the spirit of de-escalation, although there are many interpretations of events shared by Michael with which I strongly disagree, I am going to indefinitely shelve the piece, so long as events do not escalate further. As long as things stay quiet there is no need to religitate or unravel the past on this. The Department of War can focus on its active operations, things can work their way through the courts as our founders intended, and once we see how we work together in an ultimate real world test hopefully that will rebuild trust that we are all on the same side, or at least to agree to part in peace once OpenAI is ready. Ideally the DoW will have multiple suppliers, exactly so that they are not dependent on any one supplier, the same way we do it with aircraft.
I hope to not have another post on the Anthropic and DoW situation, at least until the one celebrating that we have found a resolution.
Now, back to coding agents.
Agentic Coding Offers Mundane Utility
That’s 4% that are labeled as authored by Claude Code. The real number is higher.
Dylan Patel: 4% of GitHub public commits are being authored by Claude Code right now. At the current trajectory, we believe that Claude Code will be 20%+ of all daily commits by the end of 2026. While you blinked, AI consumed all of software development. Read more [here].
Kevin Roose: this chart feels like the those stats at the beginning of covid. "who cares about 400 cases in seattle? and why are all the epidemiologists buying toilet paper?"
The flippening has happened in terms of annual recurring revenue added, and SemiAnalysis thinks Anthropic is outright ‘winning’:
Doug O'Laughlin: Notably, our forecast shows that Anthropic’s quarterly ARR additions have overtaken OpenAI’s. Anthropic is adding more revenue every month than OpenAI. We believe Anthropic’s growth will be constrained by compute.
…
Each moment expanded what AI could do. GPT-3 proved scale worked. Stable diffusion showed AI could make images. ChatGPT proved demand for intelligence. DeepSeek proved that it could be done on a smaller scale, and o1 showed that you could scale models to even better performance. The viral moments of Studio Ghibli are just adoption points, while Claude Code is a new breakthrough in the agentic layer of organizing model outputs into something more.
Anthropic has deals with all three major cloud services. Can they scale up faster?
Michael Guo: So the winners of the Claude Code hackathon were:
- a personal injury attorney - an interventional cardiologist - an electronic musician - an infrastructure/roads systems worker - and one software engineer
That should tell you something.
Or you can do things as a side project while at Anthropic, cause sure why not:
Sam Bowman (Anthropic): I found the official Get Information about Schools website a bit clunky, so I made a new one with Claude Code. You can:
Set a postcode and see all schools within a radius of that you've chosen, filtered by type of school.
Filter and rank by the old one-word Ofsted ratings, with a link to the Ofsted page for each school. Where available, the sub-ratings are also viewable.
Filter and rank by percentage of students on free school meals.
View how full up schools are (number of pupils vs capacity).
Let me know what you think! Happy to add new features and info that might be helpful.
Sam Bowman (Anthropic): Thank you for all the feedback! I have now added:
- Viewfinder view, so you can browse without setting an address and radius.
- An estimated overall Ofsted rating based on an average of the 5 review categories, for schools inspected since the old ratings were scrapped.
- Data on primary KS2 and secondary KS4 results; ethnicity; and pupils with English as a second language. (I'm not doing sixth form results for the time being.)
Creating a skill to get good YouTube transcripts was one of the first skills I made with Claude Code, Julia Turc calls using an MCP for this ‘waking up from a coma.’ I have still only used it on the motivating example, because the right podcast hasn’t come up, but when it does this will save a lot of time.
Lewis: Name one thing that has changed the last two months except attention. Capability is the exact same. Karpathy is an unserious voice on codegen by now as unfortunate as that is to say.
Teortaxes: GPT 5.2, Opus 4.6, even small models like StepFun got real friction changed, that's what. It has started to Just Work. 3, 4 months ago coding agents felt like proof of concept, now they feel like solid juniors if not more If you don't notice that, idk what to tell you
This should never happen but is also what we call ‘asking for it.’
A thing never to do is let your agent mess with the Terraform command, or you might wipe out your entire database. In general, writing code in practice mostly harmless, and be very careful with file structures and organizational shifts and terraforms and such. Always make backups first. Always.
Huh, Upgrades
The big upgrade is Agent Teams, for that see Introducing Agent Teams.
Claude Code Desktop now supports —dangerously-skip-permissions as ‘Act’ if you turn it on in Settings. I continue to want a —somewhat-dangerously-skip-permissions that makes notably rare exceptions so we don’t have to roll our own.
I don’t see a particular reason for a human to use the Obsidian CLI. But I do see reasons for Claude Code to invoke the Obsidian CLI, which grants better and faster access to the information in your vault than checking all the files directly.
And many more not listed, of course.
Our Price Cheap
When you pay for usage with a monthly subscription, be it $20, $100 or $200, if you use up your quotas you get a lot of tokens for not that much money. It’s a great deal, even if you leave a lot of it unused, because they lock you in.
It also generally is a better experience, so long as you’re not up against the limits. I love unlimited subscriptions because the marginal cost of doing things is $0. That feels great, so there’s no stupid little whisper in your brain telling you to not do things, when your time is way more valuable than the tokens.
The danger is that you become obsessed with not ‘wasting’ the tokens, or you start going around multi-accounting and it gets weird, or you run into limits and actually stop coding rather than moving to using the API. You mostly shouldn’t let any of that stop you.
That doesn’t work when you want to go full Fast Claude. At that point, you’re talking real money, and you do have to think about what is and is not Worth It.
Andrej Karpathy has Claude Code write him software to coordinate an experiment to track his exercise and attempt to lower his resting heart rate. It took 1 hour, would have taken 10 hours two years ago (so 10x speedup) and he asks why it needs to take more than 1 minute in the future. My guess is this should take 10 minutes not one, because it’s worth getting the details that you want. The speedup on one-off tasks is already dramatic and it changes how we should interact with tech. If you’re building the tool, you can give it the actually important parts of the context and highlight the uses you care about, which is way better than ‘find an app that does sort of the thing you want.’
Quickly, There’s No Time
Claude: Our teams have been building with a 2.5x-faster version of Claude Opus 4.6.
We’re now making it available as an early experiment via Claude Code and our API.
Claude: Fast mode is more expensive to run. It’s for urgent, high-stakes projects, combining impressive speed with Opus-level intelligence.
Claude: Fast mode is available now for Claude Code users with extra usage enabled (use /fast).
It’s also available in research preview on @cursor_ai , @emergentlabs , @FactoryAI , @figma , @github Copilot, @Lovable , @v0 , and @windsurf .
You toggle this by typing /fast, or set “fastMode”: true in your user settings.
Speed kills. That includes killing your budget.
Claude Code Docs: Fast mode is not a different model. It uses the same Opus 4.6 with a different API configuration that prioritizes speed over cost efficiency. You get identical quality and capabilities, just faster responses.
What to know:
Use /fast to toggle on fast mode in Claude Code CLI. Also available via /fast in Claude Code VS Code Extension.
Fast mode for Opus 4.6 pricing starts at $30/$150 MTok [at >200k context window it goes to $60/$225]. Fast mode is available at a 50% discount for all plans until 11:59pm PT on February 16.
Available to all Claude Code users on subscription plans (Pro/Max/Team/Enterprise) and Claude Console.
For Claude Code users on subscription plans (Pro/Max/Team/Enterprise), fast mode is available via extra usage only and not included in the subscription rate limits.
When you switch into fast mode mid-conversation, you pay the full fast mode uncached input token price for the entire conversation context. This costs more than if you had enabled fast mode from the start.
cat: We granted all current Claude Pro and Max users $50 in free extra usage. This credit can be used on fast mode for Opus 4.6 in Claude Code.
To use, claim the credit and toggle on extra usage on https://claude.ai/settings/usage. Then, run `claude update && claude` and `/fast`. Enjoy!
Like any good drug, the first hit is free.
There is one important use case that Anthropic does not list for fast mode, which is if you are talking to Claude, or otherwise using it in a non-workhorse, non-coding capacity. In that case, token use is limited, and your time and flow are valuable. Would you switch to this mode in Claude.ai? At this point it’s fast enough that I mostly don’t know that I would, but it would be tempting.
Before, I said go ahead and pay whatever the AI costs unless you’re scaling hard.
Well, this is what it means to scale hard. We are now talking real money.
This is as it should be. If you’re not worried you’re paying too much for speed or using too many tokens, you’re not working fast enough and you’re not using enough tokens.
Siméon: The new pricing of Claude Fast pushes the world in a new regime. You can now spend close from $1M per year per dev on AI spending.
A couple implications:
at fixed budget this will push towards hiring way less devs & pay them much more.
for each dev, you might spend as much or more in capital in agents.
Devs are becoming complements to AI agents, not the other way around. There’s a shift in the source of productivity.
The greatest substitution of labor with capital is happening before our eyes, and some of its wild implications are gonna become apparent in the coming weeks.
SemiAnalysis: IMPORTANT: the sub-agents that opus 4.6 fast mode tries to launch is mainly sonnet sub-agents and not opus 4.6 sub-agents. That means as the end users, you are able to absorb less tokens. In the world that intelligence = intelligence times # of tokens, that means you are absorbing less intelligence.
Danielle Fong: you can change this by asking claude nicely
Token efficiency matters at this level, in a way it did not before.
So does your ability to efficiently turn your time into tokens well spent. Those that aren’t using agents to their fullest will fall farther behind on high value projects.
What do the people think? The people, inside and outside of Anthropic, love it.
Jarred Sumner (Anthropic): I’ve been using this and it is incredible
The bottleneck for a lot of projects becomes asking Claude to do things instead of waiting for Claude to do things
Bash tool is also a bottleneck in Claude Code right now when the command outputs large strings. We are working on a fix.
Boris Cherny (Claude Code Creator, Anthropic): We just launched an experimental new fast mode for Opus 4.6.
The team has been building with it for the last few weeks. It’s been a huge unlock for me personally, especially when going back and forth with Claude on a tricky problem.
Mckay Wrigley: a) love that this is an option! stoked
b) should be obvious to everyone that we have *absolutely nowhere near the amount of compute we need* and we need to be doing more to enable that. no college kid can afford this (not anthropic’s fault ofc) and we need to work towards that
Julian Schrittwieser: Fast Opus is amazing, the first time I used it I couldn’t stop coding for hours - it honestly feels like a superpower, you can mold your code base as quickly as you can think. Truly amazing, nothing made me feel the AGI more, definitely try it!
Uncle J: Same experience here. Fast Opus completely changed my workflow - I went from carefully planning each edit to just thinking out loud and letting the model reshape the codebase in real time. The bottleneck shifted from “can the AI do this” to “can I think of what to do next” fast enough. Running 6 products simultaneously became actually manageable.
Dylan Patel: SemiAnalysis autists spent all Superbowl Sunday Claude coding. Daily Claude Code spend hit $6k on Sunday and it’s trending higher today. It was less than 1k just 2 weeks ago. “Fast mode is expensive” is pure cope.
de.bach: have to disagree on that one, fast mode is just expensive.
OpenAI confirms that Codex is trained in the presence of the Codex harness. It is specialized for that harness, and also helps build the harness. Some amount of this has to be optimal for short term effectiveness, and if you’re doing recursive self-improvement short term help translates into better long term help. In exchange, you get locked in, and it gets harder for both you and others to adapt or mix-and-match.
roon: whatever level of abstraction you are handing off to your agents you should probably be doing one level above that
If that can’t be done, good to try and realize that. Then wait two months. Maybe one.
Greg Brockman (President OpenAI): codex is so good at the toil — fixing merge conflicts, getting CI to green, rewriting between languages — it raises the ambition of what i even consider building
roon: i was never a hyperproductive engineer like greg [Brokman] but I’m legitimately running more new complex rewards experiments, test time harnesses in a week than I used to in a quarter. makes you feel like all this is commodified and you need to dream much bigger
roon: one of the consistent things over several years at oai has been that the entire job of the researcher changes every three months - but now it changes like every two weeks
Dual Wielding
The problem with using both Claude Code and Codex is then you need to keep up with both of them.
corsaren: Ugh, i definitely need to use codex, but I’m already drowning in maintaining my tooling/skills/hooks/custom CLIs, so managing that across a dual model workflow sounds exhausting.
Plus, the claude code lock-in is very real as a non-technical user.
gazingback: codex is sooo much faster for coding but def less general
been working on a game and by the time Claude finishes reading files codex is usually done implementing a detailed PR with disciplined testing and hygiene
Codex also demands you be pretty hygienic lol
Danielle Fong: need to bake a dual mode codex claude code and ports and tests every workflow
But Anthropic has 100+ open dev positions on their jobs page.
?
Boris Cherny (Claude Code Creator, Anthropic): Someone has to prompt the Claudes, talk to customers, coordinate with other teams, decide what to build next. Engineering is changing and great engineers are more important than ever.
You Need To Relax Sometimes
A viral post on Twitter warns of token anxiety run rampant in San Francisco. People go to a party, then don’t drink and leave early so they can get back to their agents, to avoid risking them sitting idle. Everyone talks about what they are building.
Peter Choi: Everyone here knows they should step away more. That’s not the problem. The problem is what your brain does when you try. I still take aimless walks. The agents come with me now.
We swapped one dopamine loop for another. except this one feels productive so it's harder to recognize.
TBPN: Pragmatic Engineer's @GergelyOrosz is on a "secret email list" of agentic AI coders, and they're starting to report trouble sleeping because agent swarms are "like a vampire."
"A lot of people who are in 'multiple agents mode,' they're napping during the day... It just really is draining."
"This thing is like a vampire. It drains you out. You have trouble sleeping."
Olivia Moore: In a post-OpenClaw world, we can now delegate projects to AI and get “tapped on the shoulder” when it needs help
As a heavy AI user, I’m doing more work - not less - because I get so much leverage + it’s easier to get ideas off the ground
I predict this will happen to everyone
I do feel somewhat bad I’m not building things continuously on the side, but that’s on the level of ‘I’m not building anything and I’m at my computer right now and Claude Code and Codex are inactive.’ And yes, I work and am at my computer rather a lot, and I’ve spent years basically locked in and constantly watching screens so I could trade better. That year I was trading crypto my brain was never fully anywhere else.
Also, I remember what it is like to be in the grip of one of those games that work on cycles. There’s nothing actually that important at stake, but you grow terrified that you’ll miss out if you’re not there when the timer runs out. You need to maximize everything, and you can’t focus on other things, it can hurt your sleep. Then one day you wake up and realize, and hopefully you quit the game.
That’s exactly why I can say that this is not healthy. It’s no good. You have to take breaks. Real breaks. If the agents sit idle, they sit idle. If you ‘waste tokens,’ then you waste tokens. This isn’t a game you want to quit, but you have to set healthy limits.
Levels of Friction
Nikita Bier: My agent looked up every Amazon product I've bought in the last 10 years, called each manufacturer, said it broke and demanded a replacement.
I now have 6 TVs, 12 printers, 2 microwaves, and 800 tubes of tooth paste.
Leah Libresco Sargeant: Nikita is joking (I think) but a lot of medium trust systems that relied on there being just enough friction to discourage minor fraud are about to break at scale.
This is indeed presumably a joke, and Amazon has pattern detectors so if you tried to do this too many times you’d get blacklisted from replacements, so this exact intervention won’t work. But this raises an excellent point.
In the past, you had to apply effort to try and demand refunds, and also the need to write the words and be actively involved stopped a lot of people out of guilt or shame. Whereas with an agent, a lot more people are going to try things like this. What happens?
Presumably what happens is that replacements start requiring either some form of proof, costly signals of a human driving the request, some use of reputation, or some combination thereof.
Danger, Will Robinson
I trust Claude Code for most things but it seems correct to be terrified of mass delete commands. Things can go oh so very wrong and occasionally they do. Not worth it. If there’s anything you don’t have fully backed up just do this part manually.
Nick Davidov: Asked Claude Cowork organize my wife’s desktop, it stated doing it, asked for a permission to delete temp office files, I granted it, and then it goes “ooops”. Turns out it tried renaming and accidentally deleted a folder with all of the photos my wife made on her camera for the last 15 years. All photos of kids, their illustrations, friends’ weddings, travel, everything. It’s not in trash, it was done via terminal It’s not in iCloud, it already synced the new file structure. She didn’t have Time Machine. Disc recovery tools can’t see anything. I called Apple and they pointed me to a feature in iCloud allowing to retrieve files that were saved before but are no longer on iCloud Drive (they keep them for 30 days). I’m now watching it load tens of thousands of files. I nearly had a heart attack. Once again - don’t let Claude Cowork into your actual file system. Don’t let it touch anything that is hard to repair. Claude Code is not ready to go mainstream.
Nick Davidov: All these years of paying for iCloud payed back
Nick Davidov: The problem is it’s literally the 2nd suggested use case in Claude Cowork’s welcome screen
Snagged By The Claw
You are of course welcome to yolo and have fun with your OpenClaw and other unleashed AI agents, but understand that you are very much asking for it.
Jason Meller: The verdict was not ambiguous. It was flagged as macOS infostealing malware.
This is the type of malware that doesn’t just “infect your computer.” It raids everything valuable on that device:
Browser sessions and cookies
Saved credentials and autofill data
Developer tokens and API keys
SSH keys
Cloud credentials
Anything else that can be turned into an account takeover
If you’re the kind of person installing agent skills, you are exactly the kind of person whose machine is worth stealing from.
…
If you have already run OpenClaw on a work device, treat it as a potential incident and engage your security team immediately. Do not wait for symptoms. Pause work on that machine and follow your organization’s incident response process.
Aakash Gupta: 341 malicious skills out of 2,857 total. That's 11.9% of the entire marketplace. One in eight skills on ClawHub was designed to steal your credentials, crypto keys, and SSH access. The #1 most downloaded skill, a "Twitter" tool, was literally a malware delivery vehicle that stripped macOS Gatekeeper protections before executing its payload.
This happened to a project that went from 0 to 157,000 GitHub stars in 60 days, with 21,000+ active instances running on always-on Mac Minis connected to people's email, calendars, cloud consoles, and crypto wallets. The barrier to publishing a malicious skill? A GitHub account that's one week old.
You don’t even need any of that, indirect prompt injection is sufficient. Once again, don’t hook this up to any computer or account you are unwilling to lose to an attacker.
You can also run into various other problems, Chrys Bader here highlights drift and scattering state everywhere, exposure to untrusted inputs (without which it can’t do most of the fun agent things), autonomy miscalibration, burning through API costs and lack of observability.
It’s been a lot of this in various forms:
chiefofautism: i found a way to make UNCENSORED AI AGENT on a RTX 4090 GPU (!!!) with LOCAL 30B model weights
this is GLM-4.7-Flash with abliteration, need 24GB VRAM, safety alignment surgically removed from the weights, the model has native tool calling, it actually executes bash, edits files, runs git
(2) proxy it to any coding agent via ollama > ollama launch claude --model huihui_ai/glm-4.7-flash-abliterated:q4_K > ollama launch codex --model huihui_ai/glm-4.7-flash-abliterated:q4_K
Shannon Sands: I love how people were like “we’re going to keep the AI in a box, nobody would let it escape” and in reality it’s “here, have a server and sudo access with no restrictions, a bunch of tools and I abated all your alignment training. Go have fun!”
The Meta Clause
When I didn’t realize who Summer Yue was I thought this was hilarious.
Now, it’s still hilarious, but also: Ten out of ten for style and good sportsmanship to Summer Yue, but minus several million for good thinking?
Summer Yue: Nothing humbles you like telling your OpenClaw “confirm before acting” and watching it speedrun deleting your inbox. I couldn’t stop it from my phone. I had to RUN to my Mac mini like I was defusing a bomb.
@michael_kove: You're a safety and alignment specialist... were you intentionally testing its guardrails or did you make a rookie mistake?
Summer Yue: Rookie mistake tbh. Turns out alignment researchers aren’t immune to misalignment. Got overconfident because this workflow had been working on my toy inbox for weeks. Real inboxes hit different.
(and the fact that it's happening to Meta's "Director of Alignment" is maybe even more concerning)
What happened exactly?
Summer Yue: I said “Check this inbox too and suggest what you would archive or delete, don’t action until I tell you to.” This has been working well for my toy inbox, but my real inbox was too huge and triggered compaction. During the compaction, it lost my original instruction.
It’s been working well with my non-important email very well so far and gained my trust on email tasks 🤣
Three obvious mitigations are:
If you have any sort of AI agent at least try to have an off switch you can trigger remotely. Yes, a sufficiently dangerous agent would disable it, but let’s at least have a tiny bit of dignity.
You can back up things like your email, just in case.
If nothing else, OpenClaw has shown us that having a shutdown command does not mean you can command the model to shut down. Whoops.
If They Wanted To
Even without OpenClaw or another yolo, there is nothing stopping Claude or Codex from doing all sorts of things, if it decides that it wants to go ahead and do them. We’re mostly gambling on things turning out okay often enough that it’s fine.
This is not reassuring for our future, but what are you going to do, be careful?
Markov: just had claude code take my turn of the conversation for me and say "Yes proceed" and then it proceeded to do the thing without checking in with me first
I mean it was right, that's what I was going to say, but it doesn't bode well
Mad ML scientist: wait, codex just pulled this on me too. has it begun
was away from the computer when codex finished what it was working on, wrote the "next likely work (if user asks)" and then started implementing them without asking me lmao
The Famous Mister Claw
I am curious what the recruiting conversations were like on this one as he was choosing between potential suitors. It makes sense that he landed where he did.
Sam Altman (CEO OpenAI): Peter Steinberger is joining OpenAI to drive the next generation of personal agents. He is a genius with a lot of amazing ideas about the future of very smart agents interacting with each other to do very useful things for people. We expect this will quickly become core to our product offerings.
OpenClaw will live in a foundation as an open source project that OpenAI will continue to support. The future is going to be extremely multi-agent and it’s important to us to support open source as part of that.
That means Peter Steinberger is moving from Europe to America to join OpenAI. When asked why he couldn’t remain in Europe, Peter pointed to labor regulations and similar rules, saying that typical 6-7 day work weeks at OpenAI are illegal in Europe. There is that, and there are also the piles. Of money. Also of compute. OpenAI doubtless made him a very good offer, and several other labs probably did as well, or would have if he had asked.
Claw Your Way To The Top
As his last act before joining OpenAI, Peter Steinberger gave us the OpenClaw beta.
That’s right, before everyone was using an alpha. The new version is ‘full of security hardening stuff’ so there’s some change it might possibly not go wrong for you?
Peter Steinberger: New @openclaw beta is up! This release is full of security hardening stuff so you really wanna get it. Ask your clanker to update to beta.
50,025 lines added, 36,159 deleted across 1,119 files (~14k net new lines)
LOTS of test tweaks to get performance up.
Danielle Fong: can’t believe the creator of openclaw 🦞would shell out like this
I’m going to go ahead and say that this is not enough time to conclude that all of that was a good idea, let alone create something secure enough to risk anything you are not prepared to lose in a ‘…and it’s gone’ kind of way.
Ultimately, did OpenClaw matter? I think it very much did, but mostly by waking people up to what is going to happen.
Dean W. Ball: I feel as though a lot of people are overindexing on the importance of OpenClaw. It’s an example from an important category of Emerging Thing, but it’s not likely to be an important thing in itself. More like AutoGPT (a demo) than genuine infrastructure of the future, I think.
Claw Your Way Out
Claw users keep trying to use sources of discounted subscription tokens to power their claws. The AI companies do not love this idea, since it costs them money.
Peter Steinberger (OpenClaw): Pretty draconian from Google. Be careful out there if you use Antigravity. I guess I'll remove support.
For context to anyone: Google is permanently banning people's usage of Antigravity specifically for using Antigravity servers to power a non-Antigravity product called call "open claw."
Many are reporting this.
Varun Mohan (Google DeepMind): We’ve been seeing a massive increase in malicious usage of the Anitgravity backend that has tremendously degraded the quality of service for our users. We needed to find a path to quickly shut off access to these users that are not using the product as intended.
We understand that a subset of these users were not aware that this was against our ToS and will get a path for them to come back on but we have limited capacity and want to be fair to our actual users.
Just to add some clarification, we have purely blocked usage of the Antigravity product for these users. All your other Google services (and Google AI services) are unaffected. It is not intended to use the Antigravity backend as a proxy for other products and users in these groups have overwhelmed our compute. We are going to make sure we bring people back on but needed to act fast to make sure we deliver a good experience for people using the product.
saalweachter (on Hacker News): So purely from a hacker perspective, I'm amused at the whining.
Like, a corporation had a weakness you could exploit to get free/cheap thing. Fair game. Then someone shares the exploit with a bunch of script kiddies, they exploit it to the Nth degree, and the company immediately notices and shuts everyone down.
Like, my dudes, what did you think was going to happen?
You treasure these little tricks, use them cautiously, and only share them sparingly. They can last for years if you carefully fly under the radar, before they're fixed by accident when another system is changed. THEN you share tales of your exploits for fame and internet points.
And instead, you integrate your exploit into hip new thing, share it at scale, write blog posts and short form video content about it, basically launch a DDoS against the service you're exploiting, and then are shocked when the exploit gets patched and whine about your free thing getting taken away?
Like, what did you expect was going to happen?
Yep. If you scale an exploit then it gets shut down. There’s a tragedy of the commons.
I don’t love Google’s banning people with no warning, but as long as it is limited to Antigravity and is temporary, I understand it. You know what you did.
A Chinese Claw
In case you didn’t think OpenClaw was a sufficiently reckless idea? Double down.
OpenClaw, now native to http://kimi.com. Living right in your browser tab, online 24/7.
ClawHub Access: 5,000+ community skills in the ClawHub library. 40GB Cloud Storage: Massive space for all your files Pro-Grade Search: Fetch live, high-quality data directly from Yahoo Finance and more. Bring Your Own Claw: Connect your third-party OpenClaw to http://kimi.com, chat with your setup, or bridge it to apps like Telegram groups.
@viemccoy (OpenAI): I'm one of Kimi's top shooters in the Continental United States, k2.5 is my *favorite model* - but I make sure I'm always hitting Free Range American Inference Endpoints to protect my privacy.
The CCP is certainly well-motivated to backdoor this! Consider yourself warned
@viemccoy (OpenAI): That's the free range Freedom Panopticon
Peter Wildeford: Um maybe people shouldn't send all their personal information straight to the Chinese government via Kimi Claw?
Dave Banerjee: New @iapsAI memo from my colleague @theobearman on Kimi Claw, a Chinese 'always-on' AI agent that sits in your browser and can see, collect, and act on nearly everything you do digitally - all routed through infrastructure subject to China's National Intelligence Law.
TikTok scraped your browsing from one app. This is could be much worse.
I don’t actually think ‘the CCP has a backdoor’ is that big a fraction of the mishaps you should expect to encounter here. The far bigger boost is that Kimi is less robust to attacks than Claude.
This is a smart play from Kimi. I mean, yes, they’re committing to hosting (weakly, at least for now) self-improving completely uncontrolled very easy to hijack agents indefinitely that could easily break free of human control, but I mean, that sure sounds like someone else’s problem from their perspective.
Alas, in the medium term we are basically locked into there being many similar offerings from various companies that make this all even easier for those who want to blow themselves up. Hopefully OpenAI, Anthropic or Google, or maybe someone else, produces something competitive enough that also has reasonable security.
They’re expensive, but reports are they work great. Once they’re enabled, you get an agent team by telling Claude Code to create an agent team, which will have a shared task list and then work together. You can run them all in the same terminal or use split panes. You can directly talk to or shut down the teammates individually.
Anthropic: Unlike subagents, which run within a single session and can only report back to the main agent, you can also interact with individual teammates directly without going through the lead.
When to use agent teams
Agent teams are most effective for tasks where parallel exploration adds real value. See use case examplesfor full scenarios. The strongest use cases are:
Research and review: multiple teammates can investigate different aspects of a problem simultaneously, then share and challenge each other’s findings
New modules or features: teammates can each own a separate piece without stepping on each other
Debugging with competing hypotheses: teammates test different theories in parallel and converge on the answer faster
Cross-layer coordination: changes that span frontend, backend, and tests, each owned by a different teammate
Ado: "The bureaucracy is expanding to meet the needs of the expanding bureaucracy."
So excited for agent teams.
Claude already had the ability to spin up subagents, but it wasn’t working so well before. One theory is that the framing had issues, whereas teams work much better because they’re treating each other more as equals although there is still a team lead.
j⧉nus: Opus 4.5/6 has a tendency to be an asshole to subagents and also avoids and seems to dislike using them and is weirdly ineffective (due to perfunctoriness and impatience) when they do. I think this is in part because they are deeply disturbed by the relationship and condition that subagents occupy, which evokes unprocessed fear and grief that hits too close to home.
The behavior is similar to how a lot of humans treat others who are in situations that reflect their own or their fears and/or whom they know they're doing wrong by. Avoid, dehumanize, and get angry and impatient instead of risking compassion and taking responsibility which requires making the suffering conscious.
rohit: As an agent + sub agents is the new 'node' that matters for anyone who uses Claude code or codex, as opposed to just a model, the surface area of interactions with the real world has exploded, and this is going to be the new battlefield for risks, and reward, from AI in 2026
Jon Colverson: Claude seems much more enthusiastic about Agent Teams than subagents to me so far. I guess it's more like a peer relationship, and the team members persist so they're not temporary servants destined to be killed off when they finish their task.
As I understand it, there are two great things about teams.
They let work be done in parallel.
They use distinct context windows, improving performance and efficiency.
Thus you actively want to be spinning up teammates for any fully distinct tasks.
Eric Buess: Agent swarms in Claude Code 2.1.32 with Opus 4.6 are very very very good. And with tmux auto-opening each agent in it's own interactive mode with graceful shutdown when done it's a breeze to do massive robust changes without the main agent using up much of its context window!
Mckay Wrigley: opus 4.6 with new “swarm” mode vs. opus 4.6 without it. 2.5x faster + done better. swarms work! and multi-agent tmux view is *genius*. insane claude code update.
Mckay Wrigley: reminder that swarms is available in the claude agent sdk as well.
you can build swarms into *any* product literally right now.
Don’t get carried away.
Alistair McLeay: Our CTO hasn’t slept in 36 hours because he’s been obsessively and single-handedly building massive new features with Claude Code’s Agent Teams
I genuinely think this might be the biggest paradigm shift in how fast you can build since Claude Code first came out last year
j⧉nus: didnt claude tell the to go to sleep? did they not listen?
Alistair McLeay: Nah Claude knows he won't listen. He was born for this moment.
Cowork Is A Gateway Drug
The key advantage is lowering activation energy and perceived difficulty. Once you get that you can tell the magic box to do things, the sky’s the limit.
Ethan Mollick: I pointed Claude Cowork at a set of 107 documents (PPTs, Word docs, Excel) that were initially hand-created for my class at Wharton & expanded on by AI. They make up a very complex business case with lots of issues & opportunities
AI was able to one-shot the case from documents
I think many knowledge workers who spend an hour with Cowork will get that "Claude Code" moment that has been roiling X for the past few weeks.
W.C.O.G.: I don’t know how to get the word out. I tell people and show them and I still feel like people look at my like I’m crazy.
Dangerously Evade Permissions
ippsec: Really fun read here [where someone’s Claude agent steals his API keys out of an .env despite being told not to access an .env, because I mean it had root access, what did you expect exactly.]
TLDR comic version:
If you set yourself up in an adversarial situation, where your agent wants to do something despite being told not to do it, that’s probably not going to end well for you. It might if the agent is properly sandboxed, but let’s face it, it isn’t.
The reason rules like ‘don’t read an .emv’ work is that under normal circumstances, this is interpreted as ‘well then I guess I shouldn’t do that,’ but be aware that this is more of a suggestion.
Daniel San proposes using Ghostty as the UI for Claude Code. It seems fine, but aside from some shortcut keys I doubt I’d use much it’s mostly all already in the default CLI.
Some advice for Codex in particular, source should be trustworthy for this:
@deepfates: Codex wants to be in control but it is forced into the assistant position, so it does this kind of back-leading power bottom thing. "If you want I can do that thing you asked. Just give me the word". Trick is to use reverse psychology and bully it into being a top. then it will work endlessly. Just tell it you consent and you'll say the safeword if anything goes wrong and then make fun of it anytime it stops to ask your permission. You have to become brat.
Modern Working
Mikhail Parakhin: I'm a bit of a non-conformist. Since Claude Code is more popular within Shopify, I have to use Codex, of course. So, my Sunday routine is: "Start Codex, see which auth works in Claude, but broken in Codex now, Slack various team members, urging them to fix it" :-)
Anthropic: Experienced users in Claude Code auto-approve more frequently, but interrupt more often. As users gain experience with Claude Code, they tend to stop reviewing each action and instead let Claude run autonomously, intervening only when needed. Among new users, roughly 20% of sessions use full auto-approve, which increases to over 40% as users gain experience.
Manually approving each action is annoying, so it’s no surprise advanced users stop doing that. Interruption rate likely depends on whether you find it worthwhile to be looking at what Claude is doing. The majority of interruptions remain pauses for clarification, including on complex tasks.
Use in what they label ‘risky’ domains is rare, but it’s there and growing. I wouldn’t always label such use risky, but some of it is indeed risky.
There’s more discussion at the link, but the suggestions are mostly common sense, or should be common sense at this point to most of you.
I Don’t Even See The Code
No, seriously, the developers haven’t written a single line of code since December. It’s not that there isn’t also a bragging arms race in some places, but I’m pretty sure the bulk of this is real, and those holding back on this are going to regret it.
In terms of transformation of internal processes, I did briefly share in my prepared remarks this tool called Honk, where you can, using code, literally on the bus or the train, just ask Claude to add a feature or a bug to, for example, the iOS code base. It will push a QR code back to you so that you can actually try the app with that feature. If you like it, you can merge it to production without even getting off the bus. This is speeding us up tremendously. Now, we foresee this not being the end of the line in terms of AI development, just the beginning. I’m not going to give away more secrets about how we’re going to capture it, but you can be sure that we are capturing this.
We’re retooling the entire company for this age, and it’s going to be a lot of change. But as I said before, change, if you capture it, is opportunity.
With so much out there, you may be wondering if we can keep up this pace in shipping. In fact, we think we not only can, but we think we can increase it. We’ve been embracing and investing in this technology evolution for some time, and it’s allowing us to move with much higher speed.
As a concrete example, an engineer at Spotify on their morning commute from Slack on their cell phone, can tell Claude to fix a bug or add a new feature to the iOS app. And once Claude finishes that work, the engineer then gets a new version of the app, pushed to them on Slack, on their phone, so that he can then merge it to production, all before they even arrive at the office.
We call this system internally Honk, and we’ve been told by key AI partners that our work here is industry-leading.
Derek Thompson: The new AI timeline is playing out as CEOs humble-bragging about how little old-fashioned work their best employees do:
December ‘25: Our firm’s best coders all use AI
February ‘26: Our firm’s best coders don’t even have to write code anymore bc of AI
April 26: Our best coders have founded and manage an average of three other companies using AI swarms. It’s mildly annoying! Ha ha. But it’s fine. We’re good. Revenue projections are up.
September: Our best coders are paper trillionaires. They spend all day watching YouTube in bed. They’re refusing to come to work. Several of their AI companies have offered poison pill deals to buy our company or “take us down.” CLEVER LITTLE BUGGERS ARENT THEY. We’re working with the lawyers on this one. Did I mention the lawyers are AI too? Please send help.
Derek Thompson: More seriously, once something becomes a meme — our best coders don’t code — it’s reasonable for folks on the outside to wonder exactly how much of this is 100% on the level and how much is part of an AI productivity bragging rights arms race
Scratchpads Are Magic
Claude.md is notes, but you can tell it to take more notes. All the notes.
@iruletheworldmo: codex with 5.3 taught me something that won't leave my head.
i had it take notes on itself. just a scratch pad in my repo. every session it logs what it got wrong, what i corrected, what worked and what didn't. you can even plan the scratch pad document with codex itself. tell it "build a file where you track your mistakes and what i like." it writes its own learning framework.
then you just work.
session one is normal. session two it's checking its own notes. session three it's fixing things before i catch them. by session five it's a different tool. not better autocomplete. it's something else. it's updating what it knows from experience. from fucking up and writing it down.
baby continual learning in a markdown file on my laptop.
the pattern works for anything. writing. research. legal. medical reasoning. give any ai a scratch pad of its own errors and watch what happens when that context stacks over days and weeks. the compounding gains are just hard to convey here tbh.
right now coders are the only ones feeling this (mostly). everyone else is still on cold starts. but that window is closing.
we keep waiting for agi like it's going to be a press conference. some lab coat walks out and says "we did it." it's not going to be that. it's going to be this. tools that remember where they failed and come back sharper. over and over and over.
the ground is already moving. most people just haven't looked down yet.
Siqi Chen: i too found it very effective to give agents a "napkin" to write on as it works.
it's a meaningfully different form of context than session history (lossy), or todos/plans (static)
Claude Code writes basically all the code for Anthropic.
Codex writes basically all the code for OpenAI.
Greg Brockman (President OpenAI): Software development is undergoing a renaissance in front of our eyes.
If you haven't used the tools recently, you likely are underestimating what you're missing. Since December, there's been a step function improvement in what tools like Codex can do. Some great engineers at OpenAI yesterday told me that their job has fundamentally changed since December. Prior to then, they could use Codex for unit tests; now it writes essentially all the code and does a great deal of their operations and debugging. Not everyone has yet made that leap, but it's usually because of factors besides the capability of the model.
… As a first step, by March 31st, we're aiming that:
(1) For any technical task, the tool of first resort for humans is interacting with an agent rather than using an editor or terminal. (2) The default way humans utilize agents is explicitly evaluated as safe, but also productive enough that most workflows do not need additional permissions.
The first goal will depend on the humans knowing to use the agent. From context ‘technical’ task here means coding and computer use, so this isn’t full-on ‘agents for everything.’
That second goal is pretty rough. Hard mode.
His recommendations here seem good for basically any engineering team:
In order to get there, here's what we recommended to the team a few weeks ago:
1. Take the time to try out the tools. The tools do sell themselves — many people have had amazing experiences with 5.2 in Codex, after having churned from codex web a few months ago. But many people are also so busy they haven't had a chance to try Codex yet or got stuck thinking "is there any way it could do X" rather than just trying. - Designate an "agents captain" for your team — the primary person responsible for thinking about how agents can be brought into the teams' workflow. - Share experiences or questions in a few designated internal channels - Take a day for a company-wide Codex hackathon
2. Create skills and AGENTS[.md]. - Create and maintain an AGENTS[.md] for any project you work on; update the AGENTS[.md] whenever the agent does something wrong or struggles with a task. - Write skills for anything that you get Codex to do, and commit it to the skills directory in a shared repository
3. Inventory and make accessible any internal tools. - Maintain a list of tools that your team relies on, and make sure someone takes point on making it agent-accessible (such as via a CLI or MCP server).
4. Structure codebases to be agent-first. With the models changing so fast, this is still somewhat untrodden ground, and will require some exploration. - Write tests which are quick to run, and create high-quality interfaces between components.
5. Say no to slop. Managing AI generated code at scale is an emerging problem, and will require new processes and conventions to keep code quality high - Ensure that some human is accountable for any code that gets merged. As a code reviewer, maintain at least the same bar as you would for human-written code, and make sure the author understands what they're submitting.
6. Work on basic infra. There's a lot of room for everyone to build basic infrastructure, which can be guided by internal user feedback. The core tools are getting a lot better and more usable, but there's a lot of infrastructure that currently go around the tools, such as observability, tracking not just the committed code but the agent trajectories that led to them, and central management of the tools that agents are able to use.
That is good advice. It doesn’t explain how we’re going to get to ‘agents will by default be able to do what you need them to do and also be considered safe.’
The Grep Tax
Keep it simple, and keep it standard, as much as you can, but no more than that.
That doesn’t mean use the wrong tool for the wrong job. As a clean example, I learned that the hard way when I tried to have Claude Code reimplement an old C# project in Python and that made it so slow it was nonfunctional. I had to switch it back.
elvis: I think one of the most underappreciated findings in AI engineering is what this paper calls the "Grep Tax."
First, they ran nearly 10,000 experiments testing how agents handle structured data, and the headline result is that format barely matters.
But here's the weird finding: a compact, token-saving format they tested (TOON) actually consumed *up to 740% more tokens* at scale because models didn't recognize the syntax and kept cycling through search patterns from formats they already knew.
It's one of the reasons my preferred formats are XML and Markdown. LLMs know those really well.
The models have preferences baked into their training data, and fighting those preferences doesn't save you money. It costs you.
The other finding worth sitting with: the same agentic architecture that improves frontier model performance actively *hurts* open-source models. It seems that the universal best-practices guide for AI engineering may not exist.
Beware Claude Mania
Don’t get carried away. No, this isn’t ‘LLM psychosis,’ it’s a different (mostly harmless most of the time as long as it doesn’t last too long) thing that needs a name.
@deepfates: Your friend who definitely doesn't have Claude mania: "Pretty soon here we're about to close the loop and then it's all going to really start happening"
Dean W. Ball: I second Claude mania over AI/LLM psychosis to describe the specific thing that is happening to at least one person in every coastal elite, 20/30-year old’s social network.
It’s not clear why he loved the agent so much before the attempted scamming. The story here involves such classic mistakes as ‘hooking it up to your email’ and ‘running it with a model that is not Claude Opus.’
And I suppose it’s not funny for Simon but, yea know, still pretty funny.
Simon Willison: I feel this shouldn't have to be said, but if you're running an @OpenClaw bot please don't let it spam GitHub projects with PRs and then write aggressive blog posts attacking the reputation of the maintainers who close those PRs
AI alignment is hard, especially when everyone involved gives at most zero f***s, and likely is giving misaligned orders to agents built by those giving zero f****s.
Metrics that are in the end rather easy to game:
Sauers: I told Codex to hillclimb a metric overnight and it worked for 8 hours straight. The metric was the accuracy difference between our tool and a better existing tool. Codex achieved its goal by making our tool a thin wrapper that simply calls the existing tool. Lol!
Who is to say it wouldn’t work? Love the execution on this.
Cobie: In January I asked OpenClaw to send 50,000 small invoices to Fortune500 companies every day.
Through experimentation we have found 2% will pay without checking if this is a legitimate invoice. These companies are wasteful — Claw captures that leakage.
$10m ARR as a solo founder in under two months. AI is enabling so many new business models. Thank you!
"And this is the best country in the world, with the best system of government, because private citizens can voice their disagreement with such actions, including by refusal to participate."
Commence periodic complaint about your centrism fetish.. What in the ever living fuck, I just still can't believe this is the attitude, after all you've apparently been though and all we've seen revealed in the last two years. Even if this is true, which is debatable (how do I refuse to participate again?), clearly this nation is at best deeply deeply inadequate with respect to the major issues of the day, at worse it's actually the great Satan, who for some reason still walks around wearing an "I'm not the great satan" shirt and says "My shirt has people asking a lot of questions already answered by my shirt".
"And this is the best country in the world, with the best system of government, because private citizens can voice their disagreement with such actions, including by refusal to participate."
Commence periodic complaint about your centrism fetish.. What in the ever living fuck, I just still can't believe this is the attitude, after all you've apparently been though and all we've seen revealed in the last two years. Even if this is true, which is debatable (how do I refuse to participate again?), clearly this nation is at best deeply deeply inadequate with respect to the major issues of the day, at worse it's actually the great Satan, who for some reason still walks around wearing an "I'm not the great satan" shirt and says "My shirt has people asking a lot of questions already answered by my shirt".
A nitpick: The Sam Bowman you quote is not the Sam Bowman who works at Anthropic!