Noam Shazeer leaves Google for OpenAI

Noam Shazeer leaves Google for OpenAI

Good morning ๐Ÿ‘‹ The co-author of the transformer paper just announced he's joining OpenAI. Everything else you build is downstream of that paper.

In today's issue:

Get tomorrow's issue in your inbox.

One concise AI brief, sent after the signal clears the noise.


๐Ÿ”ญ THE ONE THING

๐Ÿง  Noam Shazeer leaves Google for OpenAI

Shazeer announced Tuesday on X that he's joining OpenAI as Lead for AI Architecture Research. He's one of the eight co-authors of "Attention Is All You Need," the 2017 paper that gave every current LLM its spine. He'd co-founded Character.AI after leaving Google the first time; Google paid approximately $2.7 billion to bring him back in 2024 as VP of Engineering and co-lead of Gemini. He lasted under two years. Sam Altman's reply: "noam is one of the people I have most wanted to work with since the very beginning of openai. only took 10 years. i think it will be worth the wait!"

What his day-to-day looks like isn't confirmed beyond the title. What is clear: Google's Gemini just lost a co-lead in the run-up to OpenAI's reported September IPO, and the person now overseeing OpenAI's model architecture is the one who helped write the blueprint everything is built from. The $2.7B retention package bought under two years.


๐Ÿ”ฌ RESEARCH HIGHLIGHTS


๐Ÿ› ๏ธ TOOLS & HOW-TO

Write an AGENTS.md your coding agent will actually use

The Probe-and-Refine paper's core finding: most AGENTS.md files are written top-down from how the author thinks about the codebase, not bottom-up from where agents actually get confused. Flip the process:

1. Run your agent on 5 representative tasks. Log every wrong file guess or subsystem confusion.

2. Add a one-line directory index for each area it got wrong: src/auth/ = session state only; src/users/ = profile data.

3. Document the test command and specify which failure types are expected noise vs. a genuine regression.

4. Add a "traps" section: "Fixing X in module A broke B three times. Always check both."

5. After every future failed run, ask what was missing from the file, not what was wrong with the agent.

Prompt: Review this AGENTS.md and identify: (1) subsystem boundaries an agent would likely confuse, (2) missing test guidance, (3) historical pitfalls not yet captured. Suggest 3 specific additions with exact wording.

5 trending right now


๐Ÿ”— QUICK LINKS


See you tomorrow.

Pradeep Perugu

Get inovAIte in your inbox.