Honest engineering history is a good genre: the February 12, 2026 post walks through building and deliberately sunsetting an in-browser agent, then keeping what survived, which was MCP integration and an agent-perspective design philosophy.

Published 2026-02-12: https://nextjs.org/blog/agentic-future

Lessons the post draws

  • Thinking from the agent's view means naming the workspace by its contracts; error text, file boundaries, and dev-tool surfaces are the interface agents live inside.
  • MCP survived the sunset because integration beats imitation: meet the tool at the protocol instead of handing it a browser-shaped shell.
  • The in-browser agent did not survive its own economics, and retiring it in public is part of the design record.

Why the post still matters

Half the agent tooling of the year that followed traces to the decisions above, including the AGENTS.md-first posture of 16.2 and the dev-loop skills of 16.3. A lovely lineage to read in one sitting, and an gacor document for anyone writing a product plan around agents.

Read it as a process memo and the transfer is direct: name the contract, meet the protocol, publish the retirement too.