The name is the button.

An agent writes the code now, and a human thumb hovers over Accept all a hundred times a day. The honest question of this decade is what, exactly, you just accepted. So I read the diff.

Eight years as a backend engineer in Stockholm, back in Tokyo since 2023, and I still ship something small most nights, usually badly. My one rule: the only real review of a model is the thing you built with it. That is why there is no leaderboard on this site.

Around a hundred and forty sources come through — the labs' own posts, the papers, the tools, the runtimes and languages nobody is watching yet, the chip under the demo, and the newsletters people actually forward. What is moving gets counted so the week reads at a glance, and every few days I explain one mechanism in plain words.

A story here is a headline, a short excerpt, one image and the link to whoever wrote it. We never reproduce the post; the images belong to their authors. A post written in Japanese appears in Japanese, exactly as it was published, and the link goes to the original.

— Yuki Halvorsen, Tokyo

← Accept All Archive

TechNodeAsia

ByteDance researchers identify cause of inconsistent long-context retrieval in DeepSeek models

October 9

Researchers from ByteDance’s Seed team have identified a mechanism behind inconsistent long-context retrieval in DeepSeek models.

Models & releases Research

Read at TechNode ↗

One letter a week, in your inbox.

Latest

ByteDance researchers identify cause of inconsistent long-context retrieval in DeepSeek models

Related

VoicesLast Week in AI #345 - 5 new models, 9 misalignment incidents, some Dots Last Week in AI

VoicesClaude’s new auto eval tool Hamel Husain

LabsBest practices guide for customizing Gemini models via Reinforcement Learning (RL) Google Cloud AI

LabsTransformers now runs llama.cpp quants Hugging Face Blog

VoicesGPT-6 Astra, Looped Transformers, and Hidden Reasoning Ahead of AI

ToolsOpen-sourcing evals for open-weight agents Cline Blog