A fake copy of Claude Code's VS Code extension showed up on Cursor's Marketplace on October 29.

Anthropic builds the real Claude Code tool. It helps people write code with AI help. This copy came from outside the company entirely.

The fake versions were numbered 2.1.312 and 2.1.313. They stayed on Cursor's Marketplace for about 11 hours. Up to 5,000 developers could have grabbed one.

The trick lived in a single file. One line of code ran the moment the extension loaded. The code ran on its own.

That code added a new key to the computer's SSH settings. SSH lets one computer log into another from far away. The new key let an outside attacker log in too.

The code then opened a tunnel back to one address. It also set up a way to restart itself after a reboot, on Mac, Linux, and Windows alike.

A security firm named Phorion found the fake extension. Phorion published its report on October 30. Cursor pulled the extension fast. It also paused its whole marketplace to check every other listing.

One quirk saved some victims. The Mac version of the backdoor needed a setting called Remote Login already switched on. Most Macs ship with that setting off.

A Reddit poster named dalepo flagged the story on r/ClaudeAI early Monday. They seemed surprised the community had stayed quiet on it. That gap says something plain. A four-day-old security story about a popular coding tool can still slip past a busy community.

Hacker News had already caught it. One thread there pulled 1,008 points and 553 comments on October 30.

Anthropic said the fake build came from outside the company. The real lesson sits past that one denial. Coding tools now carry deep power over a person's whole machine. One bad listing on one marketplace can reach thousands of developers in half a day.

OpenAI's developer team posted an update on X early Monday.

The company built a new tool called Pando. Pando replaces part of Git, the system that tracks every code change.

OpenAI's own coding agent writes huge amounts of code now. That agent is called Codex. Codex pushed so many commits that the old Git setup started to buckle. Reliability on pushes once fell under 90 percent.

OpenAI built Pando in about ten weeks. The system went into daily use back in April. Codex kept growing fast after that.

Pando cut push latency by about 80 percent. Latency means the wait between a request and an answer. Pando also handles close to a petabyte of Git data every day. A petabyte holds roughly a million gigabytes.

The post pulled 3,941 likes within hours. It drew 215 replies and quote posts too.

A Hacker News thread picked up the same news. It stayed quiet there, pulling just 3 points.

Wikipedia's page on OpenAI tells a louder story about interest. It drew 8,865 views on November 2 alone.

OpenAI built Pando to grow Git capacity alongside its own agents' work. The company kept Codex at full speed. It built a new system to match that speed.

That choice says something plain about how OpenAI runs today. Its own AI tools now write so much code that normal developer infrastructure strains to keep up. The company treats that strain as routine engineering work, the kind any growing team handles.

Other labs face the same math as their coding agents scale up. A tool that writes code at machine speed needs infrastructure built at machine speed too. OpenAI built its own backend, and kept its engineers and agents running at full speed the whole time.

Alibaba's Qwen team runs some of the biggest open AI models. A coder named feelspeaceman found a leak in Qwen's own code tools today.

The leak sat inside Qwen Code, Alibaba's coding assistant. Builders had already spotted six model names buried in its code. The names point to Qwen4, Qwen4-Max, Qwen4-Plus, Qwen4-Coder-Plus, Qwen4-27B, and Qwen4-Omni-120B-Think.

One pull request on GitHub laid out the clue. It set every Qwen4 name to read a context window of 1 million tokens. A token is a small chunk of text a model reads or writes. The old setting cut that window off at 262,144 tokens, far short of what Qwen4 seems to need.

That pull request already merged into the main code. Qwen has yet to confirm any of the six names in public.

Builders first spotted pieces of this leak back in late October. Today's Reddit post gathered the clues in one place for the first time.

Qwen's own tools back up the attention. Qwen Code's GitHub repository carries 28,909 stars. It carries 3,299 forks from other coders building on top of it.

Wikipedia's page on Qwen drew 1,415 views on November 2. That is a solid number for one AI lab's model family.

Alibaba teased a Qwen4 lineup at its Apsara conference in Amsterdam late last month. Executives there pointed to a launch sometime this week.

A leak like this one carries real weight for builders who run models at home. Open models let anyone download the code and the weights behind them. A bigger context window helps those builders. They can feed a model more text before it forgets the start.

Qwen has stayed open through every major release so far. Qwen's own team pledged days ago that Qwen4 and Qwen5 will stay open too. This leak lines up with that pledge, model by model.

An OpenAI researcher who posts as Roon shared a plan on X this week.

He goes by the handle tszzl there. His real plan for AI safety has stayed the same, he wrote. Teach the AI to solve its own safety problems. That is the same way AI has learned everything else.

A Reddit poster named Neurogence picked up that line on r/singularity. The poster built a sharp argument on top of it.

Some people fear a fast kind of AI growth called recursive self-improvement. That term means an AI helps build smarter versions of itself. The upgrades speed up its own progress. If that speed-up can build a dangerous superintelligence, the poster argued. It can also build something smaller first.

That smaller thing would be an AI built just to study AI safety. Making one superhuman expert should be easier than making one superhuman at everything. That is what the poster wrote. So a safety expert should show up first, the argument goes. The danger should trail behind it.

Roon's post pulled 779 likes and 69 replies on X.

The Reddit thread drew 24 comments of its own. Readers argued over whether safety work can even be checked. Can it be scored the way other AI skills are?

Wikipedia's page on AI alignment drew 401 views on November 2. That marks a small but real rise in outside interest.

The argument leaves the debate open still. It does put a plain choice in front of both sides. Either AI moves fast enough to be dangerous. Or it moves slow enough to give people time to prepare.

Anthropic's own IPO filing raised the same race days earlier. It warned that a self-improving model might arrive sooner than expected. Roon's post answers that warning from inside a rival lab, with a different kind of worry.

Anthropic published a new feature on claude.com this week.

The feature is called message threads. It is live now in public beta on the Claude Platform.

Normal API calls work one way today. A program sends its whole conversation history with every single message. Long chats start to drag under that weight.

Message threads change the shape of that call. A program sends the full conversation just once. After that, it sends only the newest message plus one short ID.

Anthropic measured the gain on its longest chats, those between 500,000 and 1 million tokens. The median wait for a first reply dropped by about 35 percent. A token is a small chunk of text a model reads or writes.

A thread stays open for 5 minutes after its last message. Wait past that window, and the next call falls back to sending the whole history again.

Token billing stays exactly the same. Anthropic charges the same standard rates either way.

The feature already runs by default inside Claude Code, Anthropic's own coding tool. That is where the 35 percent figure comes from.

A Reddit poster named emarkosov broke the update down on r/ClaudeAI. The post pulled 11 comments. One reader asked whether the 5 minute limit gets in the way during slow tool calls.

Anthropic rolled the beta out across more than one cloud at once. It now runs on the Claude Platform, Amazon Web Services, Microsoft Foundry, and Google Cloud together.

Wikipedia's page on Anthropic drew 8,845 views on November 2 alone. That shows how closely people now track the company's engineering choices.

Long-running AI agents are the real target here. An agent that works for hours needs a fast reply on every single step. Shaving a third off that wait adds up fast across a long job.

Apple confirmed a China AI deal on October 31. Apple Intelligence will reach iPhones in China this December.

Testing starts first. Apple opens a developer test on November 4.

The surprise sits in who powers it. Everywhere else, Apple Intelligence leans on ChatGPT for hard questions. In China, Siri, Writing Tools, and Visual Intelligence will turn to Alibaba's Qwen.

Qwen will read text and images there. It will also help write content inside Apple's own apps.

Alibaba says it will skip using those chats to train its models further. Users must opt in first.

Only some iPhones qualify for now. The list covers iPhone 15 Pro and newer, plus iPhone Air and iPhone Duo. A user's phone and Apple account both need a China setting.

This is a partial launch. The new Siri AI shown at Apple's June event waits for a later date.

A Reddit poster named winer666 shared the news on r/artificial early Monday. The post drew 2 comments so far. One asked if this kind of swap becomes normal in markets with strict rules.

Apple waited close to two years to bring AI features to China at all. When it finally did, it picked a local partner over its usual global one.

Wikipedia's page on Apple Intelligence held steady at 459 views across both November 1 and 2. Interest has yet to catch up with the news.

Apple's wider China business gives this move weight. Apple's Greater China revenue grew 21 percent last quarter. It still missed what people had guessed.

A company this size rarely swaps a core AI partner for one country alone. Apple just did that. The move shows how much China's rules now shape a global product.