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

GitHub BlogGitHub

How bug bounty sharpens one researcher’s security skills

10.22

As Cybersecurity Awareness Month continues, the GitHub Bug Bounty team is excited to spotlight another top-performing security researcher from the GitHub Security Bug Bounty Program: @r31n !

MCP, skills & tools

Read at GitHub Blog ↗

One letter a week, starting soon.

Latest

How bug bounty sharpens one researcher’s security skills

Related

ToolsIntroducing our Training API Modal

ToolsGive your Supabase app its own MCP server Supabase Blog

ResearchQiskit SDK v2.6 release summary IBM Research

LabsIntroducing North Automations: Intelligent workflow orchestration Cohere Blog

Toolsv2.1.307 Claude Code releases

VoicesClaude Mods: Flipping the Harness Inside Out Latent Space